From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: STAGING_LIBDIR_NATIVE needed in bitbake.conf
Date: Tue, 07 Aug 2007 09:52:10 +0100 [thread overview]
Message-ID: <1186476730.5653.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200708070822.03530.openembedded@hrw.one.pl>
On Tue, 2007-08-07 at 08:22 +0200, Marcin Juszkiewicz wrote:
> STAGING_LIBDIR_NATIVE sounds ok for me
I'd certainly prefer STAGING_LIBDIR_NATIVE rather than paths with the
"/../" in them :). I'm wondering if we need it though?
> > Anyone have any heartburn with this approach to resolving this problem?
>
> It should be done in classes/native.bbclass not in ncurses-native. The
> problem is wider as there are few distributions which have host versions
> of stuff other then OE use as native. As a result building of native
> stuff which depend on native libraries can fail - when you will set
> LD_LIBRARY_PATH in native.bbclass then it should work.
Just to be clear, this is a problem with ncurses-native? If so,
STAGING_LIBDIR_NATIVE == STAGING_LIBDIR due to native.bbclass anyway so
we don't need the _NATIVE version?
We'd only need a _NATIVE version if our cross compiled packages needed
to reference something there explicitly (like they do some of the
binaries). DoO we need to do that (and if so, which package and why)?
Setting LD_LIBRARY_PATH for native.bbclass sounds like a worthwhile
experiment...
Cheers,
Richard
next prev parent reply other threads:[~2007-08-07 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 17:58 STAGING_LIBDIR_NATIVE needed in bitbake.conf Mike (mwester)
2007-08-06 18:42 ` Khem Raj
2007-08-07 6:22 ` Marcin Juszkiewicz
2007-08-07 8:52 ` Richard Purdie [this message]
2007-08-07 9:14 ` Mike (mwester)
2007-08-07 12:27 ` Richard Purdie
2007-08-07 20:28 ` Mike (mwester)
2007-08-07 22:02 ` Dr. Michael Lauer
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=1186476730.5653.6.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.