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.
make[1]: Target 'check-host' not remade because of errors.
make[1]: Leaving directory '/sources/gcc-8.2.0/build'
make: *** [Makefile:2235: do-check] Error 2
make: Target 'check' not remade because of errors.
Should I continue?
When you have build errors, don't just show the last few lines because they are totally uninformative. You need to scroll back and find the actual errors. If you can't do that because they are too far up, repeat the build operation with a log file so that you will have something to examine.
Also you haven't told us whether these are Chapter 5 or Chapter 6 errors, or what stage of the build they come from. It looks like the "make check" stage but how can we tell if you don't tell us? And with gcc, there is a further wrinkle because this is actually a composite build like binutils. We need to know which part of it caused the errors. More information please. And no, you shouldn't continue. gcc is one of the most important packages in the whole of LFS. It has to be built properly.
Here is the latest build: this in in chapter 6 building the base system.
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../../../libitm/testsuite/config/default.exp as tool-and-target-specific interface file.
Running ../../../../libitm/testsuite/libitm.c/c.exp ...
Running ../../../../libitm/testsuite/libitm.c++/c++.exp ...
=== libitm Summary ===
# of expected passes 42
# of expected failures 3
# of unsupported tests 1
make[4]: Leaving directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm/testsuite'
make[3]: Leaving directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm/testsuite'
make[3]: Entering directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm'
true DO=all multi-do # make
make[3]: Leaving directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm'
make[2]: Leaving directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm'
make[2]: Entering directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libatomic'
Making check in testsuite
make[3]: Entering directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libatomic/testsuite'
make check-DEJAGNU
make[4]: Entering directory '/sources/gcc-8.2.0/build/x86_64-pc-linux-gnu/libatomic/testsuite'
Making a new site.exp file...
srcdir='../../../../libatomic/testsuite'; export srcdir; \
EXPECT=expect; export EXPECT; \
runtest=runtest; \
if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
exit_status=0; l='libatomic'; for tool in $l; do \
if $runtest --tool $tool --srcdir $srcdir ; \
then :; else exit_status=1; fi; \
done; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi; \
exit $exit_status
WARNING: Couldn't find the global config file.
Using ../../../../libatomic/testsuite/lib/libatomic.exp as tool init file.
Test run by nobody on Wed Jul 31 17:34:21 2019
Native configuration is x86_64-pc-linux-gnu
=== libatomic tests ===
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../../../libatomic/testsuite/config/default.exp as tool-and-target-specific interface file.
Running ../../../../libatomic/testsuite/libatomic.c/c.exp ...
Fine. It's the check stage in chapter 6. Always provide this kind of information in future.
Now, if you read Chap 6.31 of the book again, it will tell you how to print out a summary of the results. There's a program called test_summary that will do it for you. There will be a few errors, so don't panic! I believe there are six expected ones in libgcc++ alone.
Then follow the link to the official build and check your errors against those shown. If there are no additional ones (or only one or two of them), you are good to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.