[Buildroot] Autoconf still not building (M4 )

[Buildroot] Autoconf still not building (M4 )

[Sagaert Johan]

Hi
 
i discovered 2 things : 
 
1) when changing the autoconf.mk to use version 2.63 instead of 2.64 then
everything builds .
 
 
2) when using the 2.64 version results in the error 
 
 
running configure with : --prefix=/home/johan/buildroot/output/host/usr
--sysconfdir=/home/johan/buildroot/output/host/etc
....
checking whether directories can have trailing spaces... yes
checking for expr... /usr/bin/expr
checking for GNU M4 that supports accurate traces... configure: error: no
acceptable m4 could be found in $PATH.
GNU M4 1.4.6 or later is required; 1.4.13 is recommended
....
 
BUT  
when creating and running a shell script containing 
 
#!/bin/sh
HOST_DIR=/home/johan/buildroot/output/host
echo running configure with : --prefix="$HOST_DIR/usr"
--sysconfdir="$HOST_DIR/etc"
./configure  --prefix="$HOST_DIR/usr" --sysconfdir="$HOST_DIR/etc"

produces :
 
running configure with : --prefix=/home/johan/buildroot/output/host/usr
--sysconfdir=/home/johan/buildroot/output/host/etc

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether /bin/sh -n is known to work... no
checking for characters that cannot appear in file names... none
checking whether directories can have trailing spaces... yes
checking for expr... /usr/bin/expr
checking for GNU M4 that supports accurate traces... /usr/bin/m4
checking whether /usr/bin/m4 accepts --gnu... yes
checking how m4 supports trace files... --debugfile
checking for perl... /usr/bin/perl
checking for emacs... no
...
 
Why is behaves this this differently ?
 
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091023/4face466/attachment.htm>

[Buildroot] Autoconf still not building (M4 )

[Peter Korsgaard]

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

Hi,
 
 Sagaert> Why is behaves this this differently ?

Strange. Try comparing the config.log files of the two runs and have a
look at the line numbers in configure that config.log refers to.

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 )

[Lionel Landwerlin]

Le vendredi 23 octobre 2009 ? 15:20 +0200, Peter Korsgaard a ?crit :
> >>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
> 
> Hi,
>  
>  Sagaert> Why is behaves this this differently ?
> 
> Strange. Try comparing the config.log files of the two runs and have a
> look at the line numbers in configure that config.log refers to.
> 

Same problem for me.
No problem with version 2.63.

Any idea ?

-- 
Lionel Landwerlin <llandwerlin@gmail.com>

[Buildroot] Autoconf still not building (M4 )

[Peter Korsgaard]

>>>>> "Lionel" == Lionel Landwerlin <llandwerlin@gmail.com> writes:

 >> Strange. Try comparing the config.log files of the two runs and have a
 >> look at the line numbers in configure that config.log refers to.
 >> 

 Lionel> Same problem for me.
 Lionel> No problem with version 2.63.

 Lionel> Any idea ?

Yes, please do as I requested above.

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Sagaert Johan]

Hi  


The logfile with ok suffix is the one run manually.

The PATH is diffferent when running through buildroot make compared with
manual run of ./configure with the same options.

I still have no explanation why this 'bug' does not show up on my debian
machine.

Johan

-----Oorspronkelijk bericht-----
Van: Peter Korsgaard [mailto:jacmet at gmail.com] Namens Peter Korsgaard
Verzonden: vrijdag 23 oktober 2009 15:20
Aan: Sagaert Johan
CC: buildroot at busybox.net
Onderwerp: Re: [Buildroot] Autoconf still not building (M4 )

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

Hi,
 
 Sagaert> Why is behaves this this differently ?

Strange. Try comparing the config.log files of the two runs and have a look
at the line numbers in configure that config.log refers to.

--
Bye, Peter Korsgaard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log_bad
Type: application/octet-stream
Size: 5779 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091023/9a3054ef/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log_ok
Type: application/octet-stream
Size: 8281 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091023/9a3054ef/attachment-0003.obj>

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

 Sagaert> Hi  
 Sagaert> The logfile with ok suffix is the one run manually.

 Sagaert> The PATH is diffferent when running through buildroot make compared with
 Sagaert> manual run of ./configure with the same options.

Exactly, that's the whole point. We build our own m4 version in
output/host/usr/bin. Maybe a fix is to upgrade our m4 version, but I
would prefer to understand the problem first.

 Sagaert> I still have no explanation why this 'bug' does not show up on my debian
 Sagaert> machine.

Presumably because Ubuntu is odd/different/newer than other dists?

The config.log output is not very verbose, so you'll need to do the
configure tests by hand to see what fails - E.G.:

output/usr/vin/m4 -F conftest.m4f </dev/null should not output anything
and produce a conftest.m4f file.

echo 'changequote(<,>)indir(<ifdef>,mac,bug)patsubst(a,\(b\)\|\(a\),\1)dnl' |\
 output/host/usr/bin/m4 --trace=mac

should not output anything.

Could you test that?

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Sagaert Johan]

Hi

I already upgraded the m4 package to use 1.4.13 and that does not help ...
Will have to do more checks, it seems several guys have this problem.

Johan  

-----Oorspronkelijk bericht-----
Van: Peter Korsgaard [mailto:jacmet at gmail.com] Namens Peter Korsgaard
Verzonden: zaterdag 24 oktober 2009 8:21
Aan: Sagaert Johan
CC: 'Peter Korsgaard'; buildroot at busybox.net
Onderwerp: Re: [Buildroot] Autoconf still not building (M4 ) results

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

 Sagaert> Hi
 Sagaert> The logfile with ok suffix is the one run manually.

 Sagaert> The PATH is diffferent when running through buildroot make
compared with  Sagaert> manual run of ./configure with the same options.

Exactly, that's the whole point. We build our own m4 version in
output/host/usr/bin. Maybe a fix is to upgrade our m4 version, but I would
prefer to understand the problem first.

 Sagaert> I still have no explanation why this 'bug' does not show up on my
debian  Sagaert> machine.

Presumably because Ubuntu is odd/different/newer than other dists?

The config.log output is not very verbose, so you'll need to do the
configure tests by hand to see what fails - E.G.:

output/usr/vin/m4 -F conftest.m4f </dev/null should not output anything and
produce a conftest.m4f file.

echo 'changequote(<,>)indir(<ifdef>,mac,bug)patsubst(a,\(b\)\|\(a\),\1)dnl'
|\
 output/host/usr/bin/m4 --trace=mac

should not output anything.

Could you test that?

--
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

 Sagaert> Hi

 Sagaert> I already upgraded the m4 package to use 1.4.13 and that does not help ...
 Sagaert> Will have to do more checks, it seems several guys have this problem.

Ok, could you please do the 2 small tests I requested?

-- 
Bye, Peter Korsgaard