LFS 5.7 - Glibc configure doesn't have proper CC var as defined in 5.2
by davecan from LinuxQuestions.org on (#4VTG2)
So in my quest to learn Linux by going through LFS on a VM, I've progressed now past my previous issues (partition failure and gcc failure) and have encountered this hopefully minor issue.
In section 5.2 there is a comment regarding section 5.7 (Glibc): (emphasis mine)
> After the run of configure, check the contents of the config.make file in the glibc-build directory for all important details. Note the use of CC="i686-lfs-gnu-gcc" to control which binary tools are used and the use of the -nostdinc and -isystem flags to control the compiler's include search path. These items highlight an important aspect of the Glibc package-it is very self-sufficient in terms of its build machinery and generally does not rely on toolchain defaults.
Now that I'm at section 5.7 I take a look at my /mnt/lfs/sources/glibc-2.30/build/config.make file, here is the relevant excerpt:
Code:# Build tools.
CC = gcc
CXX = g++
BUILD_CC = gccMy config.make file has a different CC setting than what the book says it should have in 5.2. Since this bit in 5.2 is stressed ("take no risks" etc) I'm wondering if there is something glossed over in the instructions. I ran the ../configure script exactly as shown in 5.7, from the /mnt/lfs/sources/glibc-2.30/build directory as directed.
Checking ../configure --help there is a statement that CC is an environment variable. But I don't recall a step where CC was set as an env var.
Do I need to do the following to move forward:
Thanks.
In section 5.2 there is a comment regarding section 5.7 (Glibc): (emphasis mine)
> After the run of configure, check the contents of the config.make file in the glibc-build directory for all important details. Note the use of CC="i686-lfs-gnu-gcc" to control which binary tools are used and the use of the -nostdinc and -isystem flags to control the compiler's include search path. These items highlight an important aspect of the Glibc package-it is very self-sufficient in terms of its build machinery and generally does not rely on toolchain defaults.
Now that I'm at section 5.7 I take a look at my /mnt/lfs/sources/glibc-2.30/build/config.make file, here is the relevant excerpt:
Code:# Build tools.
CC = gcc
CXX = g++
BUILD_CC = gccMy config.make file has a different CC setting than what the book says it should have in 5.2. Since this bit in 5.2 is stressed ("take no risks" etc) I'm wondering if there is something glossed over in the instructions. I ran the ../configure script exactly as shown in 5.7, from the /mnt/lfs/sources/glibc-2.30/build directory as directed.
Checking ../configure --help there is a statement that CC is an environment variable. But I don't recall a step where CC was set as an env var.
Do I need to do the following to move forward:
- set CC=i686-lfs-linux-gnu-gcc
- rm -rf $LFS/sources/glibc-2.30
- unpack glibc and restart 5.7
Thanks.