From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Luo Zhenhua-B19537 <B19537@freescale.com>
Cc: Guo Chunrong-B40290 <B40290@freescale.com>,
Liu Ting-B28495 <B28495@freescale.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: rpm: fix probably redundant RPATH issue
Date: Fri, 22 Mar 2013 16:50:11 +0000 [thread overview]
Message-ID: <1363971011.3097.19.camel@ted> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A0148460D@039-SN2MPN1-022.039d.mgd.msft.net>
On Thu, 2013-03-21 at 12:29 +0000, Luo Zhenhua-B19537 wrote:
> The issue can be reproduced with FSL toolchain which has not been published yet.
>
> I am not sure if the issue can be reproduced with Yocto default toolchain.
I'm going to guess that you have "lib/../lib" entries in some of your
external toolchain .la files. The question is therefore whether we can
better deal with this. I think other recipes will have this problem and
we need to fix libtool to better handle it.
Cheers,
Richard
prev parent reply other threads:[~2013-03-22 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 7:00 rpm: fix probably redundant RPATH issue Zhenhua Luo
2013-03-21 9:32 ` Richard Purdie
2013-03-21 12:29 ` Luo Zhenhua-B19537
2013-03-22 16:50 ` Richard Purdie [this message]
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=1363971011.3097.19.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B19537@freescale.com \
--cc=B28495@freescale.com \
--cc=B40290@freescale.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