Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, so I'm trying to build the gcc source in the chroot environment(according to section 6.14. I ran the 'make -k check' command, and a few errors were given. I then ran the 'make install' command, and it aborted w/ errors. Here is the output of my test summary file
Quote:
*********************************************
*Section 6.14 Gcc-3.4.1
*Some errors were given during make -k check
*After make install
*********************************************
cat <<'EOF' |
LAST_UPDATED: Obtained from CVS: -rgcc_3_4_1_release
Native configuration is i686-pc-linux-gnu
=== g++ tests ===
Running target unix
WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable
WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable
XPASS: g++.old-deja/g++.other/init5.C execution test
WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable
=== g++ Summary ===
# of expected passes 9640
# of unexpected successes 1
# of expected failures 67
# of unsupported tests 32
/sources/gcc-build/gcc/testsuite/../g++ version 3.4.1
=== gcc tests ===
Running target unix
FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os
XPASS: gcc.dg/cpp/cmdlne-dI-M.c scan-file (^|\\\\n)cmdlne-dI-M.*:[^\\\\n]*cmdlne-dI-M.c
XPASS: gcc.dg/cpp/cmdlne-dM-M.c scan-file (^|\\\\n)cmdlne-dM-M[^\\\\n]*:[^\\\\n]*cmdlne-dM-M.c
FAIL: gcc.dg/cleanup-10.c execution test
FAIL: gcc.dg/cleanup-11.c execution test
FAIL: gcc.dg/cleanup-5.c execution test
FAIL: gcc.dg/cleanup-8.c execution test
FAIL: gcc.dg/cleanup-9.c execution test
=== gcc Summary ===
# of expected passes 24622
# of unexpected failures 6
# of unexpected successes 2
# of expected failures 68
# of untested testcases 7
# of unsupported tests 191
/sources/gcc-build/gcc/xgcc version 3.4.1
=== libstdc++-v3 check-abi Summary ===
# of added symbols: 298
# of missing symbols: 284
# of incompatible symbols: 284
=== libstdc++ tests ===
Running target unix
XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
=== libstdc++ Summary ===
# of expected passes 2696
# of unexpected successes 1
# of expected failures 5
no, I don't think so, but I went back and ran the ../gcc-3.4.1/configure command, and it looks like everything it's looking for it can't find, perhaps a toolchain problem? is there a way to fix that? I'll have to get the output for you.
ok, here are the errors from the 'make check' command
Quote:
WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable
WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable
XPASS: g++.old-deja/g++.other/init5.C execution test
WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable
XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
make[3]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make[2]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make[1]: *** [check-recursive] Error 1
make[1]: Target `check' not remade because of errors.
make[1]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make: *** [check-target-libstdc++-v3] Error 2
make[1]: Entering directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty'
make[2]: Entering directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty/testsuite'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty/testsuite'
make[1]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty'
make: Target `check' not remade because of errors.
and here are the error's from 'make install
Quote:
make[4]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make[2]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make[1]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make[1]: Entering directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty'
make[2]: Entering directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty/testsuite'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty/testsuite'
make[1]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libiberty'
Well-l-l... better take a look at the config.log or whatever first. Messages like "could not create executable" usually mean something else, and you need to look for a detailed logfile to find out why.
I saw a bunch of these and what was really the matter was that glibc was hosed. Trying the simple "cc command test" mentioned earlier in the instructions revealed that the command didn't work. I had indeed done something wrong.
As anxious as you may be to "proceed," you really do need to do a little bit of deeper-looking before you proceed from this point, given these messages...
I tried the cc dummy.c test, mentioned earlier in the book. It listed the correct listing. So I assume that's not the error. I'll look into it some more. Any ideas as to what's wrong?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.