From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] gcc: remove the 64bithack patch
Date: Wed, 09 Jan 2013 13:45:28 +0000 [thread overview]
Message-ID: <1357739128.13022.81.camel@ted> (raw)
In-Reply-To: <441976458177570ed317fb6a8687c8eab8667cf8.1357721541.git.constantinx.musca@intel.com>
On Wed, 2013-01-09 at 11:00 +0200, Constantin Musca wrote:
> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
> ---
> meta/recipes-devtools/gcc/gcc-4.7.inc | 1 -
> meta/recipes-devtools/gcc/gcc-4.7/64bithack.patch | 63 -----------------------
> 2 files changed, 64 deletions(-)
> delete mode 100644 meta/recipes-devtools/gcc/gcc-4.7/64bithack.patch
Does removing this break multilib builds? For example, with different
libdir layouts?
Note that gcc has a shared source tree so patches cannot by applied in
say the cross case when we need this yet not in the target case when we
probably don't want it. We need to make a patch which works in all
cases.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-09 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 9:00 [PATCH 0/3] On-target multilib gcc enhancement Constantin Musca
2013-01-09 9:00 ` [PATCH 1/3] gcc: add missing dependency (zlib) Constantin Musca
2013-01-09 9:00 ` [PATCH 2/3] gcc: remove the 64bithack patch Constantin Musca
2013-01-09 13:45 ` Richard Purdie [this message]
2013-01-09 14:30 ` Constantin Musca
2013-01-09 9:00 ` [PATCH 3/3] gcc: enable multilib for target gcc Constantin Musca
2013-01-11 15:20 ` Richard Purdie
2013-01-11 15:26 ` 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=1357739128.13022.81.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=constantinx.musca@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.