From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error building with external toolchain
Date: Mon, 3 Feb 2014 19:37:01 +0100 [thread overview]
Message-ID: <20140203193701.5775f5d5@skate> (raw)
In-Reply-To: <52EFD674.7060800@coloradoengineeringinc.com>
Dear Danny Gale,
On Mon, 03 Feb 2014 10:48:36 -0700, Danny Gale wrote:
> > Aren't you running with "make -j<something>" by any chance?
> I'm running make with a single thread (-j1) to pinpoint this error.
>
> The external toolchain was built on an x86_64 host by Crosstool-NG
> 1.19.0 for a powerpc64-e6500 target. I've attached the config file for
> ct-ng.
Ok. Can you put up online a tarball of this toolchain?
We don't have powerpc64 support in Buildroot, so maybe some minor
changes in the external toolchain logic are needed.
> I was able to go through the buildroot source and follow it through: the
> .stamp_staging_installed target calls $($(PKG)_INSTALL_STAGING_CMDS),
> with PKG=TOOLCHAIN_EXTERNAL. TOOLCHAIN_EXTERNAL_INSTALL_STAGING_COMMANDS
> in ./toolchain/toolchain-external/toolchain-external.mk calls
> TOOLCHAIN_EXTERNAL_INSTALL_CORE in that same file. The message "Copying
> external toolchain libraries to target..." is there, though I don't
> understand why it fails at that point.
Correct. All the external toolchain logic is in
toolchain/toolchain-external/toolchain-external.mk.
> It seems I was mistaken -- the 32-bit version of the toolchain doesn't
> seem to import either. A different 32-bit toolchain (for the powerpc 440
> core) does import, however. So there seems to be something wrong with my
> toolchain configuration. I suspect RPC support to be the culprit.
> >>
> >> What will be required to get buildroot working with the 64-bit toolchain?
> > When you're talking about 32 bits or 64 bits, are you talking about the
> > bitness for the host architecture, or the target architecture?
> The target. The host is an x86_64. The target is a 64-bit powerpc (e6500
> core)
Again, if you can sure the toolchain tarball, I could do some testing.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-03 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 17:05 [Buildroot] Error building with external toolchain Danny Gale
2014-02-01 8:42 ` Thomas Petazzoni
2014-02-03 17:48 ` Danny Gale
2014-02-03 18:37 ` Thomas Petazzoni [this message]
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=20140203193701.5775f5d5@skate \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.