Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-core@lists.openembedded.org
Subject: meta-toolchain problem
Date: Thu, 15 Dec 2011 16:39:15 +0100	[thread overview]
Message-ID: <4EEA14A3.8070400@eukrea.com> (raw)

Hi,

while building for 3 different arm platform (armv5, armv6 & armv7), using 
oe-core + meta-oe + meta-angstrom I notice a problem when building 
meta-toolchain-qte or meta-toolchain :
in the armv7a-toolchain, I find 
./usr/local/angstrom-eglibc-x86_64-armv5te/sysroot/x86_64-angstromsdk-linux/usr/bin/ 
which contains native tools, while 
./usr/local/angstrom-eglibc-x86_64-armv7a/sysroots/x86_64-angstromsdk-linux/usr/bin/ 
is empty.
and I notice the same thing in armv6 meta-toolchain-qte.

It seems all the native packages installed in the 3 sdk are using path of the 
1st built sdk (armv5 in the present case) which seems wrong.

Do you have an idea of where to start looking for the reason of this problem ?

Thanks,
Eric





                 reply	other threads:[~2011-12-15 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4EEA14A3.8070400@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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