From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC BUG #1236 2/2] eglibc: Modify ldd script according to multilib config.
Date: Fri, 29 Jul 2011 16:38:19 +0100 [thread overview]
Message-ID: <1311953900.30326.495.camel@phil-desktop> (raw)
In-Reply-To: <8d920461c0a2d050b30d99d5a5ce464af6209f40.1311950827.git.lianhao.lu@intel.com>
On Fri, 2011-07-29 at 22:57 +0800, Lianhao Lu wrote:
> + "x86": ["ld-linux.so.2", "FLAG_ELF_LIBC5"],
That looks a bit weird to me. Are you sure that's right?
p.
next prev parent reply other threads:[~2011-07-29 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 14:57 [RFC BUG #1236 0/2] Modify ldd script for multilib Lianhao Lu
2011-07-29 14:57 ` [RFC BUG #1236 1/2] utils.bbclass/multilib.conf: Added misc supporting functions Lianhao Lu
2011-07-29 14:57 ` [RFC BUG #1236 2/2] eglibc: Modify ldd script according to multilib config Lianhao Lu
2011-07-29 15:38 ` Phil Blundell [this message]
2011-07-30 1:00 ` Lu, Lianhao
2011-07-30 20:04 ` Khem Raj
2011-08-01 2:33 ` Lu, Lianhao
2011-08-01 6:11 ` Khem Raj
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=1311953900.30326.495.camel@phil-desktop \
--to=philb@gnu.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