From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter Korsgaard <jacmet@uclibc.org>
Date: Sat, 24 Oct 2009 08:21:01 +0200
Subject: [Buildroot] Autoconf still not building (M4 ) results
In-Reply-To: <5B7C7B17491E42A8A0888518184A7AD8@apexjs> (Sagaert Johan's
	message of "Fri\, 23 Oct 2009 18\:54\:56 +0200")
References: <5B7C7B17491E42A8A0888518184A7AD8@apexjs>
Message-ID: <87eiot1fea.fsf@macbook.be.48ers.dk>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

>>>>> "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