Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <llandwerlin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autoconf still not building (M4 ) results
Date: Sat, 24 Oct 2009 21:07:08 +0200	[thread overview]
Message-ID: <1256411229.28475.78.camel@coalu.atr> (raw)
In-Reply-To: <87y6n0zmjp.fsf@macbook.be.48ers.dk>

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

  reply	other threads:[~2009-10-24 19:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D675D91F830D4777BC8E1C8B2AF4CD7C@apexjs>
2009-10-24 18:14 ` [Buildroot] Autoconf still not building (M4 ) results Peter Korsgaard
2009-10-24 19:07   ` Lionel Landwerlin [this message]
2009-10-24 19:11     ` Peter Korsgaard
2009-10-24 22:06   ` Sagaert Johan
2009-10-25 16:47     ` Peter Korsgaard
2009-10-26  9:43       ` [Buildroot] Autoconf still not building (M4 ) results getting weird Sagaert Johan
2009-10-26  6:37 [Buildroot] Autoconf still not building (M4 ) results 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
  -- strict thread matches above, loose matches on Subject: below --
2009-10-23 13:20 [Buildroot] Autoconf still not building (M4 ) 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

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=1256411229.28475.78.camel@coalu.atr \
    --to=llandwerlin@gmail.com \
    --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