From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH 04/11] gcc 4.2.4: add gcc-multilib64dir.patch
Date: Thu, 16 Apr 2009 15:10:15 -0700 [thread overview]
Message-ID: <20090416221015.GP17629@smtp.west.cox.net> (raw)
In-Reply-To: <1239798960-3586-4-git-send-email-khimov@altell.ru>
On Wed, Apr 15, 2009 at 04:35:53PM +0400, Roman I Khimov wrote:
> ---
> recipes/gcc/files/gcc-multilib64dir.patch | 43 +++++++++++++++++++++++++++++
> recipes/gcc/gcc-4.2.4.inc | 1 +
> 2 files changed, 44 insertions(+), 0 deletions(-)
> create mode 100644 recipes/gcc/files/gcc-multilib64dir.patch
Does this apply as-is to 4.1 and 4.3 too? If not, lets name it
gcc-4.2.x-multilib64dir.patch.
--
Tom Rini
next prev parent reply other threads:[~2009-04-16 22:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 12:33 [RFC] AMD64 and multilib support Roman I Khimov
2009-04-15 12:35 ` [PATCH 01/11] Add x86_64-generic machine Roman I Khimov
2009-04-15 12:35 ` [PATCH 02/11] binutils: add binutils-x86_64_i386_biarch.patch Roman I Khimov
2009-04-15 12:35 ` [PATCH 03/11] linux-libc-headers 2.6.23: fix amd64 headers Roman I Khimov
2009-04-15 12:35 ` [PATCH 04/11] gcc 4.2.4: add gcc-multilib64dir.patch Roman I Khimov
2009-04-15 12:35 ` [PATCH 05/11] gcc-cross-initial: add multilib overrides Roman I Khimov
2009-04-15 12:35 ` [PATCH 06/11] gcc-cross-intermediate: " Roman I Khimov
2009-04-15 12:35 ` [PATCH 07/11] gcc-cross: " Roman I Khimov
2009-04-15 12:35 ` [PATCH 08/11] glibc: move get_glibc_fpu_setting to glibc.inc Roman I Khimov
2009-04-15 12:35 ` [PATCH 09/11] glibc: add initial-multilib Roman I Khimov
2009-04-15 12:35 ` [PATCH 10/11] glibc: add multilib glibc Roman I Khimov
2009-04-15 12:36 ` [PATCH 11/11] package.bbclass: add multilib libdir to search path Roman I Khimov
2009-04-15 19:28 ` [PATCH 08/11] glibc: move get_glibc_fpu_setting to glibc.inc Khem Raj
2009-04-15 19:37 ` Roman I Khimov
2009-04-15 19:23 ` [PATCH 04/11] gcc 4.2.4: add gcc-multilib64dir.patch Khem Raj
2009-04-15 19:31 ` Roman I Khimov
2009-04-16 22:10 ` Tom Rini [this message]
2009-04-17 4:35 ` Roman I Khimov
2009-04-17 17:59 ` Tom Rini
2009-04-15 19:09 ` [PATCH 03/11] linux-libc-headers 2.6.23: fix amd64 headers Khem Raj
2009-04-15 19:25 ` Roman I Khimov
2009-04-16 7:12 ` Khem Raj
2009-04-18 19:54 ` Roman I Khimov
2009-04-15 19:25 ` [PATCH 02/11] binutils: add binutils-x86_64_i386_biarch.patch Khem Raj
2009-04-16 5:28 ` Roman I Khimov
2009-04-16 7:14 ` Khem Raj
2009-04-16 8:47 ` Roman I Khimov
2009-04-17 22:37 ` [PATCH 02/11] binutils: add?binutils-x86_64_i386_biarch.patch Khem Raj
2009-04-18 15:44 ` Roman I Khimov
2009-04-21 20:22 ` Roman I Khimov
2009-04-23 4:42 ` [PATCH 02/11] binutils:?add?binutils-x86_64_i386_biarch.patch Khem Raj
2009-04-23 9:37 ` Roman I Khimov
2009-04-27 10:28 ` Roman I Khimov
2009-04-28 20:02 ` [PATCH 02/11]?binutils:?add?binutils-x86_64_i386_biarch.patch Khem Raj
2009-04-15 13:01 ` [RFC] AMD64 and multilib support Stanislav Brabec
2009-04-15 13:32 ` Stanislav Brabec
2009-04-15 13:52 ` Roman I Khimov
2009-04-15 14:23 ` Stanislav Brabec
2009-04-15 14:55 ` Roman I Khimov
2009-04-15 16:03 ` Stanislav Brabec
2009-04-16 22:11 ` Tom Rini
2009-04-17 5:05 ` Roman I Khimov
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=20090416221015.GP17629@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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