Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH BUG #1236 0/3] Unify ldd/ldconfig for all multilib eglibcs
Date: Thu, 11 Aug 2011 15:38:22 -0700	[thread overview]
Message-ID: <4E4459DE.1000007@linux.intel.com> (raw)
In-Reply-To: <cover.1312195779.git.lianhao.lu@intel.com>

On 08/01/2011 04:01 AM, Lianhao Lu wrote:
> This series of patch allow all the eglibc(s) in the current multilib
> configuration have the same ldd/ldconfig settings.
>
> We put the dynamic loaders'(ld.so) names in the dictionary of "ld_info_all"
> defined in the file eglibc-ld.inc. This dictionary is indexed by the
> TUNENAME. To support a new ABI, new entry should be added into this
> dictionary along with the new ABI's TUNENAME.
>
> The information in ld_info_all can be used for both ldd script and ldconfig
> binary.
>
> The following changes since commit f94b781695cd8fa387daff16ecbf3987a0883018:
>    Bruce Ashfield (1):
>          poky.conf: explicitly referenced preferred linux-yocto version
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib llu/bug1236
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=llu/bug1236
>
> Lianhao Lu (3):
>    utils.bbclass/multilib.conf: Added misc supporting functions.
>    eglibc: Modify ldd script according to multilib config.
>    eglibc: Setting KNOWN_INTERPRETER_NAMES for ldconfig.
>
>   meta/classes/utils.bbclass                         |   31 ++++++++++++
>   meta/conf/bitbake.conf                             |    1 +
>   meta/conf/multilib.conf                            |    6 ++-
>   .../eglibc/eglibc-2.13/multilib_readlib.patch      |   20 ++++++++
>   meta/recipes-core/eglibc/eglibc-ld.inc             |   49 ++++++++++++++++++++
>   meta/recipes-core/eglibc/eglibc.inc                |    1 +
>   meta/recipes-core/eglibc/eglibc_2.13.bb            |   12 ++++-
>   7 files changed, 118 insertions(+), 2 deletions(-)
>   create mode 100644 meta/recipes-core/eglibc/eglibc-2.13/multilib_readlib.patch
>   create mode 100644 meta/recipes-core/eglibc/eglibc-ld.inc
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Can you please rebase and test this and resend.

Thanks
	Sau!



      parent reply	other threads:[~2011-08-11 22:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 11:01 [PATCH BUG #1236 0/3] Unify ldd/ldconfig for all multilib eglibcs Lianhao Lu
2011-08-01 11:02 ` [PATCH BUG #1236 1/3] utils.bbclass/multilib.conf: Added misc supporting functions Lianhao Lu
2011-08-01 11:02 ` [PATCH BUG #1236 2/3] eglibc: Modify ldd script according to multilib config Lianhao Lu
2011-08-01 17:52   ` Saul Wold
2011-08-01 11:02 ` [PATCH BUG #1236 3/3] eglibc: Setting KNOWN_INTERPRETER_NAMES for ldconfig Lianhao Lu
2011-08-01 11:09 ` [PATCH BUG #1236 0/3] Unify ldd/ldconfig for all multilib eglibcs Koen Kooi
2011-08-11 22:38 ` Saul Wold [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=4E4459DE.1000007@linux.intel.com \
    --to=sgw@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