Hi all,

i tried to build a new LFS system. Unfortunatly, the build breaks at gcc pass-2 in chapter 5. I tried several times now, the build always breaks with the same message
"<broken filename>: No such file or directory"
but it happens not always on the same source of gcc and the broken filename is always different. Pass 1 of gcc runs thru smoothly.
This failure does not occur on a x86_64 system.

Have you ever seen such kind of error? To me it looks like the linker is somehow failing.

...
libtool: link: /home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/./gcc/xgcc -shared-libgcc -B/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/./gcc -nos tdinc++ -L/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu /libstdc++-v3/src -L/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc -linux-gnu/libstdc++-v3/src/.libs -L/home/lfs/build/i686/autolfs/sources/gcc-7.1 .0/build/i686-pc-linux-gnu/libstdc++-v3/libsupc++/.libs -B/tools/i686-pc-linux-g nu/bin/ -B/tools/i686-pc-linux-gnu/lib/ -isystem /tools/i686-pc-linux-gnu/includ e -isystem /tools/i686-pc-linux-gnu/sys-include -fPIC -DPIC -D_GLIBCXX_SHARE D -shared -nostdlib /tools/lib/crti.o /home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/./gcc/crtbeginS.o .libs/compatibility.o .libs/compatibility-debug_list.o .libs/compatibility-debug_list-2.o .libs/compatibility-c++0x.o .libs/compatibility-atomic-c++0x.o .libs/compatibility-thread-c++0x.o .libs/compatibility-chrono.o .libs/compatibility-condvar.o -Wl,--whole-archive ../libsupc++/.libs/libsupc++convenience.a ../src/c++98/.libs/libc++98convenience.a ../src/c++11/.libs/libc++11convenience.a -Wl,--no-whole-archive -L/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3/libsupc++/.libs -L/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3/src -L/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3/src/.libs -lm -L/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/./gcc -L/tools/i686-pc-linux-gnu/bin -L/tools/i686-pc-linux-gnu/lib -L/tools/lib -lc -lgcc_s /home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/./gcc/crtendS.o /tools/lib/crtn.o -Wl,-O1 -Wl,-z -Wl,relro -Wl,--gc-sections -Wl,--version-script=libstdc++-symbols.ver -Wl,-soname -Wl,libstdc++.so.6 -o .libs/libstdc++.so.6.0.23 libtool: link: (cd ".libs" && rm -f "libstdc++.so.6" && ln -s "libstdc++.so.6.0.23" "libstdc++.so.6") libtool: link: (cd ".libs" && rm -f "libstdc++.so" && ln -s "libstdc++.so.6.0.23" "libstdc++.so") libtool: link: (cd .libs/libstdc++.lax/libsupc++convenience.a && /tools/i686-pc-linux-gnu/bin/ar x "/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3/src/../libsupc++/.libs/libsupc++convenience.a")
^E/ard_error.o/  1495021063  1003  1000  100644  4928      `
Ê9^E: No such file or directory
make[5]: *** [Makefile:609: libstdc++.la] Error 1
make[5]: Leaving directory '/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3/src'
make[4]: *** [Makefile:641: all-recursive] Error 1
make[4]: Leaving directory '/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3/src'
make[3]: *** [Makefile:510: all-recursive] Error 1
make[3]: Leaving directory '/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3'
make[2]: *** [Makefile:417: all] Error 2
make[2]: Leaving directory '/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build/i686-pc-linux-gnu/libstdc++-v3'
make[1]: *** [Makefile:11618: all-target-libstdc++-v3] Error 2
make[1]: Leaving directory '/home/lfs/build/i686/autolfs/sources/gcc-7.1.0/build'
make: *** [Makefile:903: all] Error 2

--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to