All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: STAGING_LIBDIR_NATIVE needed in bitbake.conf
Date: Tue, 7 Aug 2007 08:22:01 +0200	[thread overview]
Message-ID: <200708070822.03530.openembedded@hrw.one.pl> (raw)
In-Reply-To: <03d301c7d853$58ec39f0$6e01a8c0@twilight>

Dnia poniedziałek, 6 sierpnia 2007, Mike (mwester) napisał:
> In order to fix an ncurses build bug
> (http://bugs.openembedded.org/show_bug.cgi?id=2554), we need to set
> LD_LIBRARY_PATH in the ncurses bb file.
>
> I've tested, and the following resolves the problem with ncurses not
> installing:
>
>     export LD_LIBRARY_PATH = "${STAGING_BINDIR_NATIVE}/../lib"
>
> That's not too elegant, so I'd like to create "STAGING_LIBDIR_NATIVE"
> in the bitbake.conf file instead, which will clean up the recipe and
> make more obvious what it is that we're doing.

STAGING_LIBDIR_NATIVE sounds ok for me

> 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.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

              whats mean ubuntu?
              it's african word for "can't configure debian"





  parent reply	other threads:[~2007-08-07  6:24 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 [this message]
2007-08-07  8:52   ` Richard Purdie
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=200708070822.03530.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --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.