Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Autoconf still not building (M4 )
@ 2009-10-23 13:15 Sagaert Johan
  2009-10-23 13:20 ` Peter Korsgaard
  0 siblings, 1 reply; 23+ messages in thread
From: Sagaert Johan @ 2009-10-23 13:15 UTC (permalink / raw)
  To: buildroot

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>

^ permalink raw reply	[flat|nested] 23+ messages in thread
[parent not found: <D675D91F830D4777BC8E1C8B2AF4CD7C@apexjs>]
* [Buildroot]  Autoconf still not building (M4 ) results
@ 2009-10-26  6:37 Vellemans, Noel
  2009-10-26 10:35 ` Will Newton
  0 siblings, 1 reply; 23+ messages in thread
From: Vellemans, Noel @ 2009-10-26  6:37 UTC (permalink / raw)
  To: buildroot

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>

^ permalink raw reply	[flat|nested] 23+ messages in thread

end of thread, other threads:[~2009-10-26 18:19 UTC | newest]

Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-23 13:15 [Buildroot] Autoconf still not building (M4 ) Sagaert Johan
2009-10-23 13:20 ` Peter Korsgaard
2009-10-23 13:27   ` Lionel Landwerlin
2009-10-23 13:53     ` Peter Korsgaard
2009-10-23 16:54   ` [Buildroot] Autoconf still not building (M4 ) results Sagaert Johan
2009-10-24  6:21     ` Peter Korsgaard
2009-10-24  9:18       ` Sagaert Johan
2009-10-24  9:38         ` Peter Korsgaard
     [not found] <D675D91F830D4777BC8E1C8B2AF4CD7C@apexjs>
2009-10-24 18:14 ` Peter Korsgaard
2009-10-24 19:07   ` Lionel Landwerlin
2009-10-24 19:11     ` Peter Korsgaard
2009-10-24 22:06   ` Sagaert Johan
2009-10-25 16:47     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-10-26  6:37 Vellemans, Noel
2009-10-26 10:35 ` Will Newton
2009-10-26 10:57   ` Vellemans, Noel
2009-10-26 11:48     ` Will Newton
2009-10-26 11:58       ` Vellemans, Noel
2009-10-26 12:11         ` Will Newton
2009-10-26 12:20           ` Vellemans, Noel
2009-10-26 12:44             ` Peter Korsgaard
2009-10-26 15:55               ` Lionel Landwerlin
2009-10-26 18:19                 ` Peter Korsgaard

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox