gcc and autoconf

Matthias Benkmann matthias at winterdrache.de
Tue Nov 6 15:38:29 PST 2001

On 6 Nov 2001, at 16:19, Kale Duncan wrote:

> I was merrily making my way through the LFS book when I was rudely stopped
> in my tracks. While compiling the dynamic gcc-2.95.3 I got the following
> messages:
> make[1]: Leaving directory `/usr/src/tmp/gcc-build/texinfo'
> Bootstrapping the compiler
> make[1]: Entering directory `/usr/src/tmp/gcc-build/gcc'
> cd ../../gcc-2.95.3/gcc; autoconf
> /bin/sh: autoconf: command not found
> make[1]: *** [../../gcc-2.95.3/gcc/configure] Error 127
> make[1]: Leaving directory `/usr/src/tmp/gcc-build/gcc'
> make: *** [bootstrap] Error 2
> I noticed that autoconf is not installed until a ways down the list. This
> is my first time trying LFS so I am a bit nervous about deviating from the
> prescribed order. I assume I did something wrong. 

autoconf is definitely not needed for compiling gcc in chroot. Did you 
delete the gcc-build directory after the chapter 5 build and recreate it 
again for chapter 6. It is not advisable to re-use the old tree. 


Ambition is a poor excuse for not having enough sense to be lazy.

Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message

More information about the lfs-support mailing list