On Tue, Jan 28, 2014 at 05:30:16PM +0100, Frans de Boer wrote: > The next messages are produced every single time I encounter this chapter: > > Running /sources/binutils-2.24/ld/testsuite/ld-elf/binutils.exp ... > Running /sources/binutils-2.24/ld/testsuite/ld-elf/comm-data.exp ... > Running /sources/binutils-2.24/ld/testsuite/ld-elf/compress.exp ... > Running /sources/binutils-2.24/ld/testsuite/ld-elf/dwarf.exp ... > Running /sources/binutils-2.24/ld/testsuite/ld-elf/eh-group.exp ... > Running /sources/binutils-2.24/ld/testsuite/ld-elf/elf.exp ... > FAIL: static preinit array > FAIL: static init array > FAIL: static fini array > FAIL: static init array mixed > Running /sources/binutils-2.24/ld/testsuite/ld-elf/exclude.exp ... [...] > Running /sources/binutils-2.24/ld/testsuite/ld-ifunc/ifunc.exp ... > FAIL: Could not link a static executable [...] > ----------------- > > There are five failures and I can't find the cause of it. > I rebuilded everything from scratch - more then once, but still > encounter these messages. I tried this on i686 and x86_64 machines. > > Anybody an idea what might be the cause and if it is a show stopper. > > Regards, Frans.
I see that all the time, at least on x86_64 (I don't remember if I saw it when I built and tested i686 in August). So, definitely NOT a show stopper. In my own builds, I do everything I can to avoid static libraries. I have a _few_ from the toolchain, particularly libc.a, but not all of them, and not static libs from other packages. Pedantically, I do still have the libs, but I rename them to libwhatever.a.static so that I can make them available if I need to. The last time I looked at my own failures in static linking during these tests, I failed to diagnose the problem : I have a variable to preserve all static libs if I'm doing a "build like the book" run, and I thought that would solve the problem, but it didn't. By the time I looked at the results, I was way past binutils and didn't have the build and source directories any more. I was not sufficiently interested to prioritise debugging what I assumed was a problem with my own scripts. If you have not advanced beyond the tests, and still have all the build directory, I guess you could look at the test results and see if anything jumps out. If not, I suppose I can do a fresh build sometime in the next week or two. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
