On Wed, May 24, 2006 at 11:49:57PM +0100, Ken Moffat wrote: > > So, I'm starting to suspect that on multilib we might be missing > something for the 32-bit gcc that we build for the temporary system, > or else something for the 32-bit cross-glibc. > > I suppose my next step will be to rebuild 32-bit glibc at the end of > the completed system (i.e. using the final gcc). >
Which made no significant difference (c++-types-check.out now shows Error 1 instead of Error 2, but the other errors are identical). And this run was with all locales already installed. I conclude that *maybe* there is indeed something broken in 32-bit glibc on multilib. But I'm out of ideas. > Or perhaps we should just forget about running tests and trying to > prove the goodness of our builds ? > Obviously, sometimes test failures highlight errors in the build, so they are usually worth investigation, but at the moment I have to conclude that nobody on this list understands enough about the byzantine edifice called glibc to work out what is going wrong. Ken -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-dev mailing list [email protected] http://ninja.linux-phreak.biz/mailman/listinfo/clfs-dev
