Hi all,
So I am gong through linux from scratch and have hit this problem compiling binutils-2.27.

I was advised that the problem will be found around the line containing 'checking for C compiler...' in the created config.log file. Here are the relevant excerpts:

The 'checking for compiler...' line occurs twice in my config.log. First time I assume is fine:

Second time the 'checking for compiler...' occurs is where I guess the problem is:

I believe this test might help clarify the situation:

I was told I should have an a.out executable.

which should output 0 "

Here is what happened at this point:

Thanks again!

That's the problem.

It's a generic symlink to the compiler. On my box (gcc-4.x), cc is a symlink to gcc in /usr/bin. I have cc1 in /usr/libexec/x86_64-slackware-linux/4.8.3/cc1, and it's an executable.

Binutils is your first compile, so I presume you're on chapter 5. Is that correct? It's trying to use the tools on your original install at this stage, and is not finding cc1 on the base system. Your setup is probably wrong. Go figure. That's the fun (& LEARNING CURVE) of LFS

1 members found this post helpful.

Hi, thanks for the reply - yes I'm on chapter 5. I thought I had followed the instructions to the letter but perhaps not.

When I search for cc1 find returns just this:

/usr/lib/gcc/i686-linux-gnu/6/cc1

I check the $PATH variable using this command:

su - 'user' -c env | grep PATH

and /usr/lib/... isn't in any $PATH.


Here is the output of versioncheck.sh. I was sure that I had everything lined up with regard to this:

bash, version 4.4.0(1)-release
/bin/sh -> /bin/bash
Binutils: (GNU Binutils) 2.26.20160125
bison (GNU Bison) 3.0.4
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2, Version 1.0.6, 6-Sept-2010.
Coreutils: 8.25
diff (GNU diffutils) 3.5
find (GNU findutils) 4.7.0-git
GNU Awk 4.1.3, API: 1.1 (GNU MPFR 3.1.4-p2, GNU MP 6.1.1)
/usr/bin/awk -> /usr/bin/gawk
gcc (Debian 6.1.1-11) 6.1.1 20160802
g++ (Debian 6.1.1-11) 6.1.1 20160802
(Debian GLIBC 2.23-5) 2.23
grep (GNU grep) 2.5.1
gzip 1.6
Linux version 4.6.0-kali1-686-pae (devel@kali.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1kali1 (2016-07-21)
m4 (GNU M4) 1.4.17
GNU Make 4.1
GNU patch 2.7.5
Perl version='5.22.2';
sed (GNU sed) 4.2.2
tar (GNU tar) 1.29
texi2any (GNU texinfo) 6.3
xz (XZ Utils) 5.1.0alpha
g++ compilation OK

I am guessing I need to make a symlink in somewhere like /usr/bin to link to here: /usr/lib/gcc/i686-linux-gnu/6/cc1

Does that sound reasonable?

Cheers

yes, the symlink is the way to go and /usr/bin is the place to put it.

Very sorry please ignore this post.

Immediately after posting something else occurred to me and it is better that I follow that idea through before posting again, and I don't see a delete post option... Thanks

Just remember that it's not unknown for a mistake to slip into the LFS book, especially development books.