From: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error building with external toolchain
Date: Fri, 31 Jan 2014 10:05:59 -0700 [thread overview]
Message-ID: <52EBD7F7.8010504@coloradoengineeringinc.com> (raw)
Hi all,
I'm having some trouble getting buildroot to import my external
toolchain properly. The output is:
>>> toolchain undefined Extracting
>>> toolchain undefined Patching
>>> toolchain-external undefined Extracting
>>> toolchain-external undefined Patching
>>> toolchain-external undefined Configuring
>>> toolchain-external undefined Building
>>> toolchain-external undefined Installing to staging directory
>>> toolchain-external undefined Copying external toolchain libraries
to target...
make[1]: ***
[/home/dgale/Documents/system_build/bld/start.buildroot-2013.11/output/build/toolchain-external-undefined/.stamp_staging_installed]
Error 255
make[1]: Leaving directory
`/home/dgale/Documents/system_build/bld/start.buildroot-2013.11'
make: *** [.buildroot] Error 2
I have been unable to get make to output any useful error messages here,
even using the -d flag.
This error shows release 2013.11, but there are similar problems with
the latest git snapshot.
What is the problem here? Has anybody run into this before? I should
mention that the toolchain being imported is 64-bit. This is NOT an
issue using an equivalent toolchain at 32-bits. The 64-bit toolchain,
however, doesn't support multilib.
What will be required to get buildroot working with the 64-bit toolchain?
Thanks,
Danny
next reply other threads:[~2014-01-31 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 17:05 Danny Gale [this message]
2014-02-01 8:42 ` [Buildroot] Error building with external toolchain Thomas Petazzoni
2014-02-03 17:48 ` Danny Gale
2014-02-03 18:37 ` Thomas Petazzoni
2014-02-03 19:50 ` Danny Gale
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=52EBD7F7.8010504@coloradoengineeringinc.com \
--to=daniel.gale@coloradoengineeringinc.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