From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Prebuilt toolchains
Date: Wed, 11 Nov 2009 10:00:51 -0700 [thread overview]
Message-ID: <4AFAEDC3.80404@mlbassoc.com> (raw)
I'd like to use my own toolchains when building OpenEmbedded.
I've tried to follow the information at:
http://docs.openembedded.org/usermanual/usermanual.html#commonuse_prebuilt_toolchain
It's a bit terse and confusing, so I'm just trying to see
what I need (I think the section tries to discuss too many
concepts at once)
Anyway, I added these lines to my local.conf:
TARGET_SYS = "${TARGET_ARCH}-${TARGET_OS}"
ASSUME_PROVIDED += " virtual/${TARGET_PREFIX}gcc "
ASSUME_PROVIDED += " virtual/libc "
This led to a number of other inferences which I don't understand.
NOTE: selecting glibc to satisfy virtual/libintl due to PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy runtime libsegfault due to PREFERRED_PROVIDER_virtual/libc = glibc
NOTE: selecting linux-libc-headers to satisfy runtime linux-libc-headers-dev due to PREFERRED_PROVIDER_linux-libc-headers = linux-libc-headers
NOTE: selecting glibc to satisfy runtime glibc due to PREFERRED_PROVIDER_virtual/libc = glibc
NOTE: selecting gcc-cross-intermediate to satisfy virtual/powerpc-linux-gcc-intermediate due to PREFERRED_PROVIDERS
NOTE: selecting linux-libc-headers to satisfy linux-libc-headers due to PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy virtual/libiconv due to PREFERRED_PROVIDERS
NOTE: selecting gcc-cross to satisfy runtime libgcc due to PREFERRED_PROVIDER_virtual/powerpc-linux-gcc = gcc-cross
NOTE: selecting binutils-cross to satisfy virtual/powerpc-linux-binutils due to PREFERRED_PROVIDERS
NOTE: selecting glibc-initial to satisfy virtual/powerpc-linux-libc-initial due to PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy virtual/powerpc-linux-libc-for-gcc due to PREFERRED_PROVIDERS
NOTE: selecting gcc-cross-initial to satisfy virtual/powerpc-linux-gcc-initial due to PREFERRED_PROVIDERS
At which point, OE goes off on its merry way to build the
internal toolchains.
What am I missing?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2009-11-11 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 17:00 Gary Thomas [this message]
2009-11-11 20:39 ` Prebuilt toolchains Chris Conroy
2009-11-11 21:07 ` Gary Thomas
2009-11-11 21:29 ` Chris Conroy
2009-11-13 14:06 ` Gary Thomas
2009-11-13 15:57 ` Chris Conroy
2009-11-13 17:25 ` Gary Thomas
2009-11-13 18:41 ` Chris Conroy
2009-11-13 23:00 ` Gary Thomas
2009-11-16 22:40 ` Gary Thomas
2009-11-17 3:12 ` Mike Turquette
2009-11-17 7:34 ` Koen Kooi
2009-11-18 13:40 ` Gary Thomas
2009-11-18 15:29 ` Gary Thomas
2009-11-18 23:24 ` Gary Thomas
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=4AFAEDC3.80404@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@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 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.