From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc-common.inc: Consider multilib when renaming libgcc for debian'ness
Date: Tue, 25 Sep 2012 10:42:34 +0100 [thread overview]
Message-ID: <1348566154.8662.38.camel@ted> (raw)
In-Reply-To: <1348525482-31986-1-git-send-email-raj.khem@gmail.com>
On Mon, 2012-09-24 at 15:24 -0700, Khem Raj wrote:
> When doing multilib builds rpm does not find libgcc1 for lib32
> multilib because its not honoring the debian renaming scheme for
> libgcc-multilib. Lets add MLPREFIX to fix it.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-devtools/gcc/gcc-common.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-09-25 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 22:24 [PATCH] gcc-common.inc: Consider multilib when renaming libgcc for debian'ness Khem Raj
2012-09-25 9:42 ` Richard Purdie [this message]
2012-09-25 18:07 ` McClintock Matthew-B29882
2012-09-26 10:55 ` Richard Purdie
2012-09-28 18:31 ` McClintock Matthew-B29882
2012-09-25 18:12 ` Mark Hatle
2012-09-25 21:53 ` Richard Purdie
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=1348566154.8662.38.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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