Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [Multilib] a problem of SHLIBSDIR
Date: Wed, 29 Jun 2011 10:49:26 +0100	[thread overview]
Message-ID: <1309340966.20015.337.camel@rex> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F27050B57BE@shsmsx502.ccr.corp.intel.com>

On Wed, 2011-06-29 at 17:10 +0800, Lu, Lianhao wrote:
> Hi,
> 
> SHLIBSDIR is a central place where to store the pkg information about
> the shared libraries which the package would provide. In the
> do_package task,  the function package_do_shlibs() will use this kind
> of information to automatically add RDEPENDS for the package being
> built. In the multilib situation, the SHLIBSDIR should be set to a
> different place form the normal version, otherwise a 32bit application
> might RDEPENDS on lib64-eglibc instead of the 32bit eglibc. 
> 
> The following patch tries to solve this problem. Any comment?
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/ml&id=1970842424c414db50058ff99c6627e3ca034a04 

I think I'd been assuming that SHLIBSDIR included the TARGET_VENDOR
string as part of the triplet but it obviously doesn't and we need this.

Good catch. I think the patch is a good one to add!

Cheers,

Richard




      reply	other threads:[~2011-06-29  9:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 12:14 Multilib Development Update Richard Purdie
2011-06-21 12:28 ` Koen Kooi
2011-06-21 13:31   ` Richard Purdie
2011-06-21 13:02 ` Frans Meulenbroeks
2011-06-21 13:30   ` Richard Purdie
2011-06-21 13:33     ` Eric Bénard
2011-06-21 16:43       ` Khem Raj
2011-06-21 17:00       ` Richard Purdie
2011-06-21 14:35   ` Mark Hatle
2011-06-21 14:32 ` Khem Raj
2011-06-21 14:51   ` Mark Hatle
2011-06-29  9:10 ` [Multilib] a problem of SHLIBSDIR Lu, Lianhao
2011-06-29  9:49   ` 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=1309340966.20015.337.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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