[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

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

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

 Sagaert> Peter

 Sagaert> ./output/host/usr/bin/m4 -F conftest.m4f </dev/null

 Sagaert> Produces a file (see attachement ) and does not complain on the console.

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

 Sagaert> Does not output anything on the console

OK, that all looks normal. This is getting strange - To summarize:

- Fails on Ubuntu (what version?), but not on Debian
- M4 check fails on autoconf2.64, works on 2.63 - But the M4 check is
  almost completely the same for the two versions
- The two tests done by the configure script succeeds when run by hand

Does it also fail if you prepend output/host/bin:output/host/usr/bin to
the path before running configure by hand (E.G. a setup very close to
how it's done in buildroot)?

It's hard for me to debug it here as I cannot reproduce it. It would be
very helpful if you could add a few debug echo lines to ./configure
around line 2356, so we can see what's going on.

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Lionel Landwerlin]

Le samedi 24 octobre 2009 ? 20:14 +0200, Peter Korsgaard a ?crit :
> >>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
> 
>  Sagaert> Peter
> 
>  Sagaert> ./output/host/usr/bin/m4 -F conftest.m4f </dev/null
> 
>  Sagaert> Produces a file (see attachement ) and does not complain on the console.
> 
>  Sagaert> This 
>  Sagaert> echo 'changequote(<,>)indir(<ifdef>,mac,bug)patsubst(a,\(b\)\|\(a\),\1)dnl'
>  Sagaert> |\
>  Sagaert>  output/host/usr/bin/m4 --trace=mac
> 
>  Sagaert> Does not output anything on the console
> 
> OK, that all looks normal. This is getting strange - To summarize:
> 
> - Fails on Ubuntu (what version?), but not on Debian
Which version of Debian ?
I'm using Debian unstable and I got the problem.

> - M4 check fails on autoconf2.64, works on 2.63 - But the M4 check is
>   almost completely the same for the two versions
> - The two tests done by the configure script succeeds when run by hand
> 
> Does it also fail if you prepend output/host/bin:output/host/usr/bin to
> the path before running configure by hand (E.G. a setup very close to
> how it's done in buildroot)?
> 
> It's hard for me to debug it here as I cannot reproduce it. It would be
> very helpful if you could add a few debug echo lines to ./configure
> around line 2356, so we can see what's going on.
> 

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

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

Hi,

 >> - Fails on Ubuntu (what version?), but not on Debian
 Lionel> Which version of Debian ?
 Lionel> I'm using Debian unstable and I got the problem.

Interesting. I personally build on testing and stable boxes, and as we
haven't gotten any bugreports before now, it must be something that has
recently changed.

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Sagaert Johan]

 
Hi 

There seems to be a problem somewhere in the configure script of autoconf
2.64

I found a way to solve it by setting the M4 variable in the makefile (line
42) so the configure script does not have to parse and find the m4 path.



Something seems to go wrong in the tests done around line 2378 in the
configure script (compare with configure script of v2.63 )

Snip
   { test -f "$ac_path_M4" && $as_test_x "$ac_path_M4"; } || continue
      # Root out GNU M4 1.4.5, as well as non-GNU m4 that ignore -t, -F.
      ac_snippet=change'quote(<,>)in''dir(<if''def>,mac,bug)'
      ac_snippet=${ac_snippet}pat'subst(a,\(b\)\|\(a\),\1)d'nl
      echo "ac_snippet2=$ac_snippet"
      test -z "`$ac_path_M4 -F conftest.m4f </dev/null 2>&1`" \
      && test -z "`echo $ac_snippet | $ac_path_M4 --trace=mac 2>&1`" \
snip


Meanwhile it might be a good idea to update the m4 package in buildroot to
1.4.13 instead of the current 1.4.9


-----Oorspronkelijk bericht-----
Van: Peter Korsgaard [mailto:jacmet at gmail.com] Namens Peter Korsgaard
Verzonden: zaterdag 24 oktober 2009 20:15
Aan: Sagaert Johan; buildroot at uclibc.org
Onderwerp: Re: [Buildroot] Autoconf still not building (M4 ) results

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

 Sagaert> Peter

 Sagaert> ./output/host/usr/bin/m4 -F conftest.m4f </dev/null

 Sagaert> Produces a file (see attachement ) and does not complain on the
console.

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

 Sagaert> Does not output anything on the console

OK, that all looks normal. This is getting strange - To summarize:

- Fails on Ubuntu (what version?), but not on Debian
- M4 check fails on autoconf2.64, works on 2.63 - But the M4 check is
  almost completely the same for the two versions
- The two tests done by the configure script succeeds when run by hand

Does it also fail if you prepend output/host/bin:output/host/usr/bin to the
path before running configure by hand (E.G. a setup very close to how it's
done in buildroot)?

It's hard for me to debug it here as I cannot reproduce it. It would be very
helpful if you could add a few debug echo lines to ./configure around line
2356, so we can see what's going on.

--
Bye, Peter Korsgaard
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: autoconf.mk
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091025/454e5528/attachment.diff>

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

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

 Sagaert> Hi 

 Sagaert> There seems to be a problem somewhere in the configure script
 Sagaert> of autoconf 2.64

Exactly.

 Sagaert> I found a way to solve it by setting the M4 variable in the
 Sagaert> makefile (line 42) so the configure script does not have to
 Sagaert> parse and find the m4 path.

Ok, that's atleast a workaround, but I would like to understand what the
problem is exactly.

 Sagaert> Something seems to go wrong in the tests done around line 2378 in the
 Sagaert> configure script (compare with configure script of v2.63 )

 Sagaert> Snip
 Sagaert>    { test -f "$ac_path_M4" && $as_test_x "$ac_path_M4"; } || continue
 Sagaert>       # Root out GNU M4 1.4.5, as well as non-GNU m4 that ignore -t, -F.
 Sagaert>       ac_snippet=change'quote(<,>)in''dir(<if''def>,mac,bug)'
 Sagaert>       ac_snippet=${ac_snippet}pat'subst(a,\(b\)\|\(a\),\1)d'nl
 Sagaert>       echo "ac_snippet2=$ac_snippet"
 Sagaert>       test -z "`$ac_path_M4 -F conftest.m4f </dev/null 2>&1`" \
 Sagaert>       && test -z "`echo $ac_snippet | $ac_path_M4 --trace=mac 2>&1`" \
 Sagaert> snip

Indeed. Could you try sticking in a few debug echo lines, to figure out
what's going on?

 Sagaert> Meanwhile it might be a good idea to update the m4 package in buildroot to
 Sagaert> 1.4.13 instead of the current 1.4.9

Indeed. But you wrote something earlier about that not having any effect
on the above problem, right?

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Vellemans, Noel]

Repost .. mail did not reach mailing-list.

Noel,
________________________________

From: Noel Vellemans  
 Sent: 26Oct09 00:16
To: Peter Korsgaard
Cc: Sagaert Johan; buildroot at uclibc.org; llandwerlin at gmail.com;
Vellemans, Noel
Subject: Re: [Buildroot] Autoconf still not building (M4 ) results


Hi all,

Been DIGGING into the configure script ...And I have found SOMETHING
that possibly is the problem.

(have put a lot of echo's into the code to find-out something wierd)

I think the problem is that the LINE 
'echo
'changequote(<,>)indir(<ifdef>,mac,bug)patsubst(a,\(b\)\|\(a\),\1)dnl' |
/buildhome/20091024/buildroot/output/host/usr/bin/m4 --trace=mac' is not
empty/zero but a strange character printed as a small funny-thing a "00
01" (graphic thing) , due to this the 'test -z' fails .

A second test I did was remove the '&& test -z "`echo $ac_snippet |
$ac_path_M4 --trace=mac 2>&1`"line in the script and then everything
runs normal (no errors).


<snip .. echo stuff >

  test -z "$as_dir" && as_dir=.
    for ac_prog in m4 gm4 gnum4; do
    for ac_exec_ext in '' $ac_executable_extensions; do
      ac_path_M4="$as_dir/$ac_prog$ac_exec_ext"

#      echo "\n(0) $ac_path_M4,  $as_dir,  $ac_prog,   $ac_exec_ext,
$as_test_x"
 
      { test -f "$ac_path_M4" && $as_test_x "$ac_path_M4"; } || continue
      # Root out GNU M4 1.4.5, as well as non-GNU m4 that ignore -t, -F.
      ac_snippet=change'quote(<,>)in''dir(<if''def>,mac,bug)'
      ac_snippet=${ac_snippet}pat'subst(a,\(b\)\|\(a\),\1)d'nl
      
      echo "\n(1) $ac_path_M4"
      echo "$ac_snippet | $ac_path_M4 --trace=mac"
#      $ac_path_M4 -F conftest.m4f
#      cat conftest.m4f
#      rm -f conftest.m4f
      echo "$ac_snippet | $ac_path_M4 --trace=mac."
      echo
'changequote(<,>)indir(<ifdef>,mac,bug)patsubst(a,\(b\)\|\(a\),\1)dnl' |
/buildhome/20091024/buildroot/output/host/usr/bin/m4 --trace=mac
## THE ABOVE line prints a strange CHARACTER bug here ???????

      test -z "`$ac_path_M4 -F conftest.m4f </dev/null 2>&1`" \
      && test -z "`echo $ac_snippet | $ac_path_M4 --trace=mac 2>&1`" \
      && test -f <snip .. echo stuff >
conftest.m4f \
      && ac_cv_path_M4=$ac_path_M4 ac_path_M4_found=:
      rm -f conftest.m4f
      $ac_path_M4_found && break 3
    done
<snip .. echo stuff >


Greetz...... Noel


PS: upgrading to a newer version (> 1.4.9) has the same problem (double
checked it)



On Sun, Oct 25, 2009 at 5:47 PM, Peter Korsgaard <jacmet@uclibc.org>
wrote:


	>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be>
writes:
	
	
	 Sagaert> Hi
	
	 Sagaert> There seems to be a problem somewhere in the configure
script
	 Sagaert> of autoconf 2.64
	
	Exactly.
	
	 Sagaert> I found a way to solve it by setting the M4 variable
in the
	 Sagaert> makefile (line 42) so the configure script does not
have to
	 Sagaert> parse and find the m4 path.
	
	Ok, that's atleast a workaround, but I would like to understand
what the
	problem is exactly.
	
	 Sagaert> Something seems to go wrong in the tests done around
line 2378 in the
	 Sagaert> configure script (compare with configure script of
v2.63 )
	
	 Sagaert> Snip
	 Sagaert>    { test -f "$ac_path_M4" && $as_test_x
"$ac_path_M4"; } || continue
	 Sagaert>       # Root out GNU M4 1.4.5, as well as non-GNU m4
that ignore -t, -F.
	 Sagaert>
ac_snippet=change'quote(<,>)in''dir(<if''def>,mac,bug)'
	 Sagaert>
ac_snippet=${ac_snippet}pat'subst(a,\(b\)\|\(a\),\1)d'nl
	 Sagaert>       echo "ac_snippet2=$ac_snippet"
	 Sagaert>       test -z "`$ac_path_M4 -F conftest.m4f </dev/null
2>&1`" \
	 Sagaert>       && test -z "`echo $ac_snippet | $ac_path_M4
--trace=mac 2>&1`" \
	 Sagaert> snip
	
	Indeed. Could you try sticking in a few debug echo lines, to
figure out
	what's going on?
	
	 Sagaert> Meanwhile it might be a good idea to update the m4
package in buildroot to
	 Sagaert> 1.4.13 instead of the current 1.4.9
	
	Indeed. But you wrote something earlier about that not having
any effect
	on the above problem, right?
	
	--
	Bye, Peter Korsgaard
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091026/f2c6a74d/attachment.htm>

[Buildroot] Autoconf still not building (M4 ) results

[Will Newton]

On Mon, Oct 26, 2009 at 7:37 AM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> Repost .. mail did not reach mailing-list.
> Noel,

Hi Noel,

What locale are you running with? i.e., what is the output of "locale"
on your development machine?

[Buildroot] Autoconf still not building (M4 ) results

[Vellemans, Noel]

Hello ...

<Will >Hi Noel,

<Will >What locale are you running with? i.e., what is the output of
"locale"
<Will >on your development machine?


Plse find the output of locale ...
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=



Regards Noel.


-----Original Message-----
From: Will Newton [mailto:will.newton at gmail.com] 
Sent: 26Oct09 11:35
To: Vellemans, Noel
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Autoconf still not building (M4 ) results

On Mon, Oct 26, 2009 at 7:37 AM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> Repost .. mail did not reach mailing-list.
> Noel,

Hi Noel,

What locale are you running with? i.e., what is the output of "locale"
on your development machine?

[Buildroot] Autoconf still not building (M4 ) results

[Will Newton]

On Mon, Oct 26, 2009 at 11:57 AM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> Hello ...
>
> <Will >Hi Noel,
>
> <Will >What locale are you running with? i.e., what is the output of
> "locale"
> <Will >on your development machine?
>
>
> Plse find the output of locale ...
> $ locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=

Hmm, well that's one theory that down. What distribution are you
running? What is your /bin/sh (/bin/sh --version)?

[Buildroot] Autoconf still not building (M4 ) results

[Vellemans, Noel]

< Will > Hmm, well that's one theory that down. What distribution are
you running? What is your /bin/sh (/bin/sh --version)?



/$ /bin/sh --version
/bin/sh: Illegal option --

I already was looking this way .. but :-( no version .. 
It is a Ubuntu 9.04 system (with the latest patches) .. 
[ at this time it is reported to happen on Ubuntu and non-stable debian.
]


$ uname -a
Linux bmslin0003-2 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:49:34
UTC 2009 i686 GNU/Linux

$ 


Need more info ? Don't hesitate .. 

Regards noel.
 

-----Original Message-----
From: Will Newton [mailto:will.newton at gmail.com] 
Sent: 26Oct09 12:49
To: Vellemans, Noel
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Autoconf still not building (M4 ) results

On Mon, Oct 26, 2009 at 11:57 AM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> Hello ...
>
> <Will >Hi Noel,
>
> <Will >What locale are you running with? i.e., what is the output of 
> "locale"
> <Will >on your development machine?
>
>
> Plse find the output of locale ...
> $ locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=

Hmm, well that's one theory that down. What distribution are you
running? What is your /bin/sh (/bin/sh --version)?

[Buildroot] Autoconf still not building (M4 ) results

[Will Newton]

On Mon, Oct 26, 2009 at 12:58 PM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> < Will > Hmm, well that's one theory that down. What distribution are
> you running? What is your /bin/sh (/bin/sh --version)?
>
>
>
> /$ /bin/sh --version
> /bin/sh: Illegal option --
>
> I already was looking this way .. but :-( no version ..
> It is a Ubuntu 9.04 system (with the latest patches) ..
> [ at this time it is reported to happen on Ubuntu and non-stable debian.
> ]
>
>
> $ uname -a
> Linux bmslin0003-2 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:49:34
> UTC 2009 i686 GNU/Linux
>
> $
>
>
> Need more info ? Don't hesitate ..

Could you try changing the top line of the configure from /bin/sh to /bin/bash?

[Buildroot] Autoconf still not building (M4 ) results

[Vellemans, Noel]

Hi Will,

I can confirm .

/bin/sh -> fails !! (just re-tested it to be sure it still fails, and it
does fail)

/bin/bash -> is SUCCESS !!


Regards Noel.


 

-----Original Message-----
From: Will Newton [mailto:will.newton at gmail.com] 
Sent: 26Oct09 13:12
To: Vellemans, Noel
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Autoconf still not building (M4 ) results

On Mon, Oct 26, 2009 at 12:58 PM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> < Will > Hmm, well that's one theory that down. What distribution are 
> you running? What is your /bin/sh (/bin/sh --version)?
>
>
>
> /$ /bin/sh --version
> /bin/sh: Illegal option --
>
> I already was looking this way .. but :-( no version ..
> It is a Ubuntu 9.04 system (with the latest patches) ..
> [ at this time it is reported to happen on Ubuntu and non-stable
debian.
> ]
>
>
> $ uname -a
> Linux bmslin0003-2 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:49:34

> UTC 2009 i686 GNU/Linux
>
> $
>
>
> Need more info ? Don't hesitate ..

Could you try changing the top line of the configure from /bin/sh to
/bin/bash?

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

>>>>> "Noel" == Vellemans, Noel <Noel.Vellemans@visionBMS.com> writes:

 Noel> Hi Will,
 Noel> I can confirm .

 Noel> /bin/sh -> fails !! (just re-tested it to be sure it still fails, and it
 Noel> does fail)

 Noel> /bin/bash -> is SUCCESS !!

Ok, so the configure script of autoconf 2.64 fails with shell =
dash. Thanks for the debugging.

-- 
Bye, Peter Korsgaard

[Buildroot] Autoconf still not building (M4 ) results

[Lionel Landwerlin]

Le lundi 26 octobre 2009 ? 13:44 +0100, Peter Korsgaard a ?crit :
> >>>>> "Noel" == Vellemans, Noel <Noel.Vellemans@visionBMS.com> writes:
> 
>  Noel> Hi Will,
>  Noel> I can confirm .
> 
>  Noel> /bin/sh -> fails !! (just re-tested it to be sure it still fails, and it
>  Noel> does fail)
> 
>  Noel> /bin/bash -> is SUCCESS !!
> 
> Ok, so the configure script of autoconf 2.64 fails with shell =
> dash. Thanks for the debugging.
> 

Just for confirmation, Debian unstable is running dash as default shell.

Thanks again for debugging.

-- 
Lionel Landwerlin <llandwerlin@gmail.com>

[Buildroot] Autoconf still not building (M4 ) results

[Peter Korsgaard]

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

Hi,

 Lionel> Just for confirmation, Debian unstable is running dash as
 Lionel> default shell.

 Lionel> Thanks again for debugging.

Ok, so the easiest fix is probably to to s^!/bin/sh^!/bin/bash^ on the
first line of the configure script - And then report the issue upstream.

What I don't get is that Johan wrote that the configure script didn't
break when run outside buildroot - How could that be?

-- 
Bye, Peter Korsgaard