Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Autoconf still not building (M4 ) results
Date: Sat, 24 Oct 2009 08:21:01 +0200	[thread overview]
Message-ID: <87eiot1fea.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <5B7C7B17491E42A8A0888518184A7AD8@apexjs> (Sagaert Johan's message of "Fri\, 23 Oct 2009 18\:54\:56 +0200")

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

  reply	other threads:[~2009-10-24  6:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eiot1fea.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox