From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: 64-bit gcc hack patch /
Date: Thu, 04 Aug 2011 08:24:41 -0700 [thread overview]
Message-ID: <4E3AB9B9.9010201@gmail.com> (raw)
In-Reply-To: <EEDE7930-C960-4D86-86EE-D8E1E0A28017@kernel.crashing.org>
On 08/04/2011 12:55 AM, Kumar Gala wrote:
> What is meta/recipes-devtools/gcc/gcc-4.6/64bithack.patch really accomplishing at this point?
>
> Its not clear to me what benefit or what is really impacted by the following change:
>
> MULTILIB_OPTIONS = m64/m32
> -MULTILIB_DIRNAMES = 64 32
> -MULTILIB_OSDIRNAMES = ../lib64 $(if $(wildcard $(shell echo $(SYSTEM_HEADER_DIR))/../../usr/lib32),../lib32,../lib)
> +MULTILIB_DIRNAMES = . 32
> +MULTILIB_OSDIRNAMES = . $(if $(wildcard $(shell echo $(SYSTEM_HEADER_DIR))/../../usr/lib32),../lib32,../lib)
>
> Trying to decide if the ppc equivalent of this patch is really needed or not.
I think this patch should not be needed.
>
> - k
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-08-04 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 7:55 64-bit gcc hack patch / Kumar Gala
2011-08-04 15:24 ` Khem Raj [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=4E3AB9B9.9010201@gmail.com \
--to=raj.khem@gmail.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