From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] ncurses-native: install to libdir, not base_libdir
Date: Mon, 16 Jan 2012 11:09:53 -0800 [thread overview]
Message-ID: <4F147601.3070902@linux.intel.com> (raw)
In-Reply-To: <4F146249.6080905@linux.intel.com>
On 16/01/12 09:45, Saul Wold wrote:
> On 01/16/2012 07:32 AM, Chris Larson wrote:
>> On Thu, Jan 12, 2012 at 7:25 AM, Enrico Scholz
>> <enrico.scholz@sigma-chemnitz.de> wrote:
>>> Christopher Larson<kergoth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> writes:
>>>
>>>> --- a/meta/recipes-core/ncurses/ncurses.inc
>>>> +++ b/meta/recipes-core/ncurses/ncurses.inc
>>>> ...
>>>> +# natives don't generally look in base_libdir
>>>> +base_libdir_virtclass-native = "${libdir}"
>>>
>>> I do not think that this should be done per recipe (afais, at least
>>> libusb is affected by the same issue).
>>>
>>> Adding '-L<baselibdir>' and the '-Wl,-rpath-link' + '-Wl,-rpath' options
>>> to BUILD_LDFLAGS would be a more general solution.
>>
>> Alternatively, could simplify the layout of the native sysroot and
>> adjust things in the native class. It could make a certain amount of
>> sense, as it makes more sense for our structure for native to match
>> the host than it does the target.
>
> So, Chris, are you going to implement this and do we drop the ncurses
> patch for now?
We need to merge something to resolve this issue sooner rather than
later, I had to apply this change in order to build on a system without
ncurses installed.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-16 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 19:51 [PATCH] ncurses-native: install to libdir, not base_libdir Christopher Larson
2012-01-12 9:37 ` Martin Jansa
2012-01-12 14:25 ` Enrico Scholz
2012-01-16 15:32 ` Chris Larson
2012-01-16 17:45 ` Saul Wold
2012-01-16 19:09 ` Joshua Lock [this message]
2012-01-16 21:27 ` Chris Larson
2012-01-17 19:32 ` Saul Wold
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=4F147601.3070902@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@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