Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] building toolchain fails - more details
Date: Wed, 21 Oct 2009 20:31:28 +0200	[thread overview]
Message-ID: <87tyxsppj3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1531E53627F1F749B4FE809BF2A4EB67013CED64@WETMEX10.loepfe.com> (Noel Vellemans's message of "Wed\, 21 Oct 2009 16\:31\:19 +0200")

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

Hi,

 Noel> While looking to the the output/build directory it seems that it
 Noel> is -> autoconf-2.64-host.

Ok, that's a different issue than Johan's then - The snippet he posted
was about autoconf for the target.

 Noel> Looking into the config.log into this directory gives me.

 Noel> << autoconf-2.64-host - config.log snip >>

 Noel> configure:2356: checking for GNU M4 that supports accurate traces
 Noel> configure:2391: error: no acceptable m4 could be found in $PATH.
 Noel> GNU M4 1.4.6 or later is required; 1.4.13 is recommended

Strange as the host-autoconf package depends on host-m4. Don't you have
a build/m4-1.4.9-host directory? On my system I get:

configure:2356: checking for GNU M4 that supports accurate traces
configure:2398: result: /tmp/br/host/usr/bin/m4
configure:2401: checking whether /tmp/br/host/usr/bin/m4 accepts --gnu
configure:2411: result: no
configure:2422: WARNING: The version of M4 that was found does not support -g.
configure:2424: WARNING: Using it with POSIXLY_CORRECT set may cause problems.
configure:2428: checking how m4 supports trace files
configure:2438: result: --debugfile

 Noel> A) 'make at91sam9g20dfc_defconfig' (press enter a couple of times....) {

I don't see why it shouldn't work, but I've just started such a build
anyway.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-10-21 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7.1256126402.21246.buildroot@busybox.net>
2009-10-21 14:31 ` [Buildroot] building toolchain fails - more details Vellemans, Noel
2009-10-21 18:31   ` Peter Korsgaard [this message]
2009-10-21 20:54   ` 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=87tyxsppj3.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