From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] cross.bbclass: Fix many QA RPATH errors for distros preferring libtool-2.2
Date: Mon, 21 Feb 2011 18:44:41 -0700 [thread overview]
Message-ID: <4D631509.30602@mentor.com> (raw)
In-Reply-To: <20110220012310.GC3451@sakrah.homelinux.org>
On 02/19/2011 06:23 PM, Khem Raj wrote:
> On (19/02/11 13:11), Eric Benard wrote:
>> Hi Andreas,
>>
>>> index 1a6d906..50c0f63 100644
>>> --- a/classes/cross.bbclass
>>> +++ b/classes/cross.bbclass
>>> @@ -75,6 +75,6 @@ sysroot_stage_all() {
>>>
>>> #
>>> # Cross .la files have more path issues we have to correct only for libtool< 2.4
>>> -SYSROOTEXTRALIBDIRSED_OLD = " -e \"/^libdir=/s,.*,libdir=${STAGING_DIR_TARGET}${target_libdir},g\" -e \"/^dependency_libs=/s,\([[:space:]']\)-L${STAGING_LIBDIR_NATIVE},,g\""
>>> +SYSROOTEXTRALIBDIRSED_OLD = " -e \"/^libdir=/s,.*,libdir=${target_libdir},g\" -e \"/^dependency_libs=/s,\([[:space:]']\)-L${STAGING_LIBDIR_NATIVE},,g\""
>>>
>>> SYSROOTEXTRALIBDIRSED = "${@["${SYSROOTEXTRALIBDIRSED_OLD}",""][("${LIBTOOL_HAS_SYSROOT}" == "yes")]}"
>>
>> I was just finishing to test a similar fix and this seems to be the
>> right direction. Now testing your fix which is cleaner.
>
> Also try meta-toolchain targets
I'm kicking off a subset of my normal matrix with this change applied
and hope to report back results in the morning (-0700).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-22 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 11:53 [PATCH] cross.bbclass: Fix many QA RPATH errors for distros preferring libtool-2.2 Andreas Mueller
2011-02-19 12:11 ` Eric Benard
2011-02-20 1:23 ` Khem Raj
2011-02-22 1:44 ` Tom Rini [this message]
2011-02-22 14:59 ` Tom Rini
2011-02-22 22:47 ` Andreas Mueller
2011-02-22 8:19 ` Eric Benard
2011-02-22 14:56 ` Tom Rini
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=4D631509.30602@mentor.com \
--to=tom_rini@mentor.com \
--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