From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] building toolchain fails
Date: Wed, 21 Oct 2009 13:26:03 +0200 [thread overview]
Message-ID: <87r5sxq984.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <598EFF531CAB4EC0A53CDCCD0CF8AC77@apexjs> (Sagaert Johan's message of "Wed\, 21 Oct 2009 12\:29\:52 +0200")
>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
Sagaert> Hi
Sagaert> i used the 2009.08 on 2 systems without problems and i decided to give the
Sagaert> latest version a try:
Sagaert> I failed in building on both machines :
Sagaert> on my debian i ended up with :
Your subject seems to imply that you have a problem building toolchains,
but in both cases it's a problem building a package for the host?
Sagaert> ....
Sagaert> configure: error: C compiler cannot create executables
Sagaert> make: *** [/home/johan/buildroot/output/build/ncurses-5.6/.configured] Error 77
Strange. Ncurses builds here (also on Debian). What configure check
fails? (have a look at config.log in build/ncurses-5.6)
Sagaert> gcc is on the path,
Sagaert> under buildroot/output/build/staging_dir/usr/bin there is a softlink of
Sagaert> arm-linux-gcc pointing to executable ccache ???
You have presumably enabled ccache support then.
Sagaert> on my ubuntu 8.10 machine i ended with an error : error: no acceptable m4 could
Sagaert> be found in $PATH.
Sagaert> i have 1.4.11 on my system so that should be ok
Sagaert> I have seen Noel Vellemans also reporting this issue, but no solution yet..
Sagaert> Any clues ?
Sagaert> for now i patched my 2009.08 version to use 2.6.31.4 and bbox 1.15.2
Sagaert> [7m>>> autoconf 2.64 Configuring [27m
This is autoconfig for the target - A pretty uncommon thing to build.
Sagaert> checking for GNU M4 that supports accurate traces...
Sagaert> configure: WARNING: unrecognized options: --disable-gtk-doc
Sagaert> configure: error: no acceptable m4 could be found in $PATH.
Sagaert> GNU M4 1.4.6 or later is required; 1.4.13 is recommended
Sagaert> make: *** [/home/johan/buildroot/output/build/autoconf-2.64/.stamp_configured]
It seems like autoconf needs a dependency on m4. Could you try adding m4
to package/autoconf/autoconf.mk: AUTOCONF_DEPENDENCIES and try again?
If that fails, check config.log to see what/why it fails.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-10-21 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 10:29 [Buildroot] building toolchain fails Sagaert Johan
2009-10-21 11:26 ` Peter Korsgaard [this message]
[not found] <48B29D7D7EE043AF836DB1647ED0F5C6@apexjs>
2009-10-21 12: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=87r5sxq984.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