From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openembedded with a prebuilt external toolchain
Date: Wed, 02 Mar 2011 11:02:05 -0500 [thread overview]
Message-ID: <20110302160205.GC10330@denix.org> (raw)
In-Reply-To: <4D598D30.3080506@drewtech.com>
On Mon, Feb 14, 2011 at 03:14:40PM -0500, Joey Oravec wrote:
> On 2/10/2011 6:35 PM, Tom Rini wrote:
>>> Both the -csl.bb and -generic.bb copy a bunch of stuff to STAGING_DIR in
>>> do_stage(). Of course in the long-run I need for the recipe to copy C
>>> libraries, but for now I should be able to leave the body blank. At
>>> least it'll use my compiler and run to completion. Right?
>>
>> Well, as you saw, it fails in some cases. This is because, yeah, we're
>> telling the toolchain stuff lives ...here now, and it doesn't.
>
> Thanks for the additional help on chat! This followup is to share my
> results with the mailing list.
>
> Regarding my "bitbake nano" failure, that was a symptom of a sysroot issue.
> An external cross compiler has some default sysroot where it looks for
> libraries. By default it looks like OE passes nothing to change this. As a
> result do_configure() didn't look for libraries in staging dir, decided
> that ncurses didn't exist, and the build failed. One solution is to add:
>
> TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
That is the default now in conf/bitbake.conf:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?h=org.openembedded.dev&id=ebd905685a339814c36bf658a8e58bf8f457f14e
> to your build/conf/local.conf and make sure your compiler's default sysroot
> (libc, etc) gets copied into the staging dir. That way you can call *-gcc
> from somewhere in your path but it'll look for everything under OE's
> staging directory.
--
Denys
prev parent reply other threads:[~2011-03-02 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 20:24 openembedded with a prebuilt external toolchain Joey Oravec
2011-02-10 20:58 ` Tom Rini
2011-02-10 23:22 ` Joey Oravec
2011-02-10 23:35 ` Tom Rini
2011-02-14 20:14 ` Joey Oravec
2011-03-02 16:02 ` Denys Dmytriyenko [this message]
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=20110302160205.GC10330@denix.org \
--to=denis@denix.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox