All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:27:52 +0100	[thread overview]
Message-ID: <1186489672.5653.28.camel@localhost.localdomain> (raw)
In-Reply-To: <0cf301c7d8d3$4d422cb0$6e01a8c0@twilight>

On Tue, 2007-08-07 at 04:14 -0500, Mike (mwester) wrote:
> > On Tue, 2007-08-07 at 08:22 +0200, Marcin Juszkiewicz wrote:
> > 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?
> 
> No, this is a problem with ncurses, not ncurses-native. 

Ok, fair enough, I wondered but wasn't sure. its clear now :)

> > 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)?
> 
> I think they do -- how else do the dynamically-linked executables in staging
> find their shared libraries?

I'm convinced, it make sense. Feel free to add STAGING_LIBDIR_NATIVE and
then use it in the ncurses bb file (maybe mention in a comment there is
a util used in do_install which needs to find libraries from
ncurses-native).

In fact this raises the question of whether that should be set globally?

Cheers,

Richard




  reply	other threads:[~2007-08-07 12:30 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
2007-08-07  9:14     ` Mike (mwester)
2007-08-07 12:27       ` Richard Purdie [this message]
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=1186489672.5653.28.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.