Bash 3.2 make failes

Bliepo · 06-10-2009, 01:28 PM

When I try to compile BASH, I get this error (included the previous command for clarity):

Code:

lfs@x:/mnt/lfs/sources/bash-3.2$ make
cd . && autoconf
/bin/sh: autoconf: not found
make: *** [configure] Error 127

I used the configure options as described in the LFS book, so that cannot be the problem.

My best guess is that one of the host requirements hasn't been met. Therefore I have included the output of the bash version check script.

Code:

bash, version 3.2.48(1)-release
/bin/sh -> /bin/dash
Binutils: (GNU Binutils) 2.18
bison (GNU Bison) 2.3
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2,  Version 1.0.5, 10-Dec-2007.
Coreutils:  6.12
diff (GNU diffutils) 2.8.1
find (GNU findutils) 4.4.0
GNU Awk 3.1.6
/usr/bin/awk -> /usr/bin/gawk
gcc (GCC) 4.3.2
GNU C Library stable release version 2.9,
GNU grep 2.5.3
gzip 1.3.12
Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
m4 (GNU M4) 1.4.11
GNU Make 3.81
patch 2.5.9
Perl version='5.10.0';
GNU sed version 4.1.5
tar (GNU tar) 1.20
makeinfo (GNU texinfo) 4.11
Compilation OK

The host system is Ubuntu 9.04 (32 bits).

weibullguy · 06-10-2009, 02:37 PM

Have you read section 1.5 of the book? What version of the book are you using? What section is the failure occuring? Do you have autoconf installed on you host machine?

druuna · 06-10-2009, 02:58 PM

Hi,

I see one thing that's not up to specs, but that's probably not the cause of the problem: /bin/sh -> /bin/dash. I haven't used dash yet so I don't know the impact. The LFS document does specifically mention the link to bash.

Another thing I noticed: lfs@x:/mnt/lfs/sources/bash-3.2$
That doesn't look correct, it should look like this: lfs:/mnt/lfs/sources/bash-3.2$

Maybe other environment settings are also wrong......

Did you forget a step in chapter 4.3 and/or 4.4?

Bliepo · 06-11-2009, 06:21 AM

I have discovered the source of the problem. I didn't have autoconf installed.

It worked fine after I installed autoconf.

Gesp · 08-19-2009, 02:26 PM

You find a solution so my input will only be for the record.

This problem just happen to me today on a machine (sparc64 debian lenny) wich usually had no problem to compile bash-3.2 but fail that time with the same error as you.
Just erasing bash source and restarting compilation fix the issue for me.

You should be able to compile bash-3.2 without autoconf installed.
But sometime, probably a timing issue, compilation try to use autconf and fail when it is not installed.

This is the diff of bad and good logs.
--- bash-3.2-sparc-toolchain.bad.log 2009-08-19 19:56:24.000000000 +0200
+++ bash-3.2-sparc-toolchain.good.log 2009-08-19 19:56:26.000000000 +0200
@@ -538,6 +538,4 @@
config.status: executing default commands
cd /root/ipcop/svn/ipcop/trunk/build_sparc/ipcop/usr/src/bash-3.2 && make
make[1]: Entering directory `/root/ipcop/svn/ipcop/trunk/build_sparc/ipcop/usr/src/bash-3.2'
-cd . && autoconf
-/bin/bash: autoconf: command not found
-make[1]: *** [configure] Error 127
+bison -y -d ./parse.y

You could see that in the good case autoconf is even not called, bison is directly executed.

Gesp · 08-19-2009, 04:56 PM

the race is due to patching configure and configure.in in that order.
If you are unlucky configure.in is not in the same second as configure and autoconf will be called.

this will trigger the bug and try to run autoconf each time.
touch configure && sleep 1 && touch configure.in && make clean

reverse configure and configure.in order and autoconf will not be called