[SOLVED] Just finished the last GCC compilation, please tell me if the following output is acceptable

skorm513 · 04-12-2016, 07:36 PM

So I'm at Chapter 6.17 (GCC) using version 7.9-systemd, using an x86_64 architecture.

After compiling, and running `make -k check`, I get this strange (but apparently non-fatal) error immediately after:

Code:

make[2]: autogen: Command not found
Makefile:176: recipe for target 'check' failed
make[2]: *** [check] Error 127
make[2]: Leaving directory '/sources/gcc-5.3.0/build/fixincludes'
Makefile:3560: recipe for target 'check-fixincludes' failed
make[1]: *** [check-fixincludes] Error 2

The test output however matches that of the logs located for my version in the LFS website, so I think that it's still fine?

Also, searching for the header files the compiler is using gives me a slightly different output instead of the expected /usr/lib/gcc/i686-pc-linux-gnu directory:

Code:

grep -B4 '^ /usr/include' dummy.log

gives me

Code:

                                          
#include <...> search starts here:
 /usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/include-fixed
 /usr/include

Is this okay?

hpmachining · 04-13-2016, 08:03 AM

If your output matches the build logs it should be fine. Here is what the book says...

Quote:

Unless the test results are vastly different from those at the above URL, it is safe to continue.

The different output is also normal.

Quote:

Depending on your machine architecture, the above may differ slightly, the difference usually being the name of the directory after /usr/lib/gcc.

So you should be fine.

hazel · 04-13-2016, 08:37 AM

Check always reports an overall failure if anything fails that the upstream developers don't consider to be an expected failure. That includes a few failures that are expected on LFS. That's why you use the -k option. If the failures are in the specimen log, you can ignore them.