Custom Query (532 matches)

We still have a number of "To be written" descriptions for some of the programs in udev.

If you 'su' to user clfs (or whomever) to build the temporary system, bash is defective. This mostly passes unnoticed, but when you run the glibc testsuite you will see

scripts/check-c++-types.sh: line 38: syntax error near unexpected token `('
scripts/check-c++-types.sh: line 38: `  $cxx -S -xc++ -o - -D_GNU_SOURCE <(cat <<EOF'
make[1]: *** [/building/glibc-build/c++-types-check.out] Error 2

We seem to have now traced this to a failed test in bash's configure:

checking whether /dev/fd is available... absent

This test returns 'standard' if the builder is logged in, or is root, but 'absent' if the user has used 'su' to become the user who will build the clfs system.

At some point we changed to 'make libbz2.a' instead of 'make' for the 32-bit libraries because it creates all we need. The text still says "Recompile the package using a non-shared library and test it." which has confused at least one builder, because the tests are not run. The Makefile says

all: libbz2.a bzip2 bzip2recover test

The test target depends on the static bzip2.

Although I like running tests, I'm ambivalent about the bzip2 tests, because as it is shipped they only test the static code. It seems to be there are three choices:

1. Change the text to omit "and test it".

2. revert to make CC=... CXX=... without a target, so that all the targets are compiled and executed (this wastes marginal time compiling bzip2recover).

3. If people want to test, add a mention of "make CC=... CXX=... test"