LinuxQuestions.org - Adjusting tool chain question LFS 7.2 AMD-64

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - Adjusting tool chain question LFS 7.2 AMD-64 (https://www.linuxquestions.org/questions/linux-from-scratch-13/adjusting-tool-chain-question-lfs-7-2-amd-64-a-4175441538/)

Adjusting tool chain question LFS 7.2 AMD-64

I just adjusted my tool chain & all of the test outputs were ok except possibly 1

This ic the command

Code:

grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'

Here's the output
SEARCH_DIR("/tools/x86_64-unknown-linux-gnu/lib64")
SEARCH_DIR("/tools/x86_64-unknown-linux-gnu/lib")
SEARCH_DIR("/usr/lib")
SEARCH_DIR("/lib");
It'the "unknown" that I question

Another thing I noticed is in gcc-pass-2 chapter 5.9 there's an entry that is for setting flags for x86 machine

Quote:

For x86 machines, a bootstrap build of GCC uses the -fomit-frame-pointer compiler flag. Non-bootstrap builds omit this flag by default, and the goal should be to produce a compiler that is exactly the same as if it were bootstrapped. Apply the following sed command to force the build to use the flag:

Code:

cp -v gcc/Makefile.in{,.tmp}

sed 's/^T_CFLAGS =$/& -fomit-frame-pointer/' gcc/Makefile.in.tmp \

  > gcc/Makefile.in

Should I have removed it? I am now at Gcc Chapater 6.17 should I just omit from this build of gcc or start over?

I wouldn't have thought the "unknown" part is important though in my tools folder its "/tools/x86_64-lfs-linux-gnu/lib" as long as the tools are being found and compiled correctly the "unknown" or in my case "lfs-linux-gnu" bit is just an identifier, I seem to recall a bit at the beginning of the CLFS about the naming of the tools.

The test for Gcc in Chapater 6.17 errored out so I started from scratch.

I've found answer to

Quote:

/tools/x86_64-unknown-linux-gnu/lib64

Quote:

tooldir=/usr
Normally, the tooldir (the directory where the executables will ultimately be located) is set to $(exec_prefix)/$(target_alias). For example, x86_64 machines would expand that to /usr/x86_64-unknown-linux-gnu. Because this is a custom system, this target-specific directory in /usr is not required. $(exec_prefix)/$(target_alias) would be used if the system was used to cross-compile (for example, compiling a package on an Intel machine that generates code that can be executed on PowerPC machines).