Description of Problem:
The most recent version(s) of the glibc SRPMS does a "make check" (self test of
the generated libraries) in the course of building the binary RPMs. When errors
occure in the self-test, the build continues anyway, generating binary RPMs that
are now known to contain errors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpm -bb --target i586-redhat-linux /usr/src/redhat/SPECS/glibc.spec
This might take a while
Testing GB18030 *** FAILED ***
make: Target `tests' not remade because of errors.
make: Leaving directory `/usr/src/redhat/BUILD/glibc-2.2.5/iconvdata'
make: *** [iconvdata/tests] Error 2
make -s -C locale tests
make: Entering directory `/usr/src/redhat/BUILD/glibc-2.2.5/locale'
make: Leaving directory `/usr/src/redhat/BUILD/glibc-2.2.5/locale'
make -s -C localedata tests
Self-test failure should stop the build process, or at least provide some
indication that those shiny-new binary RPM are known to contain failing code.
Once the build of the binary RPM is completed there is no way to know that
errors have been encountered in the course of the self test(s). The only way
you would know there are problem is if you were watching the screen when the
That's because some glibc (and especially gcc) tests are known to fail,
the rpm -ba -v output is checked against output from older glibc/gcc versions
to search for regressions.