Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Julian Pidancet <julian.pidancet@gmail.com>
Subject: Re: [PATCH v3] Introduce multiarch DISTRO_FEATURE
Date: Fri, 25 Nov 2011 23:40:04 +0000	[thread overview]
Message-ID: <1322264404.25382.4.camel@ted> (raw)
In-Reply-To: <CAEsOVNfoFW+3G-bSYiOy4p-Pa_bDShY_c3hutpA+THDO8hUrvg@mail.gmail.com>

On Fri, 2011-11-25 at 19:07 +0000, McClintock Matthew-B29882 wrote:
> On Fri, Nov 25, 2011 at 6:29 AM, Julian Pidancet
> <julian.pidancet@gmail.com> wrote:
> > This patch introduces a distro feature which enables gcc to produce
> > both 32bit and 64bit code, and enables binutils to operate on both
> > 32bit and 64bit binaries.
> >
> > v3: - Make get_gcc_multiarch_setting more elegant. Use a dictionnary
> > to store the config options and replace bb.data.getVar with d.getVar.
> >    - Remove i686 from the architecture list because it doesn't seem
> > to be a valid TARGET_ARCH any more in OE.
> >    - Configure gdb (gdb and gdb-cross) with --enable-64-bit-bfd if
> > multiarch DISTRO_FEATURE is present
> >
> > Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com>
> 
> I'm not sure if this is the correct spot to bring this up, but how
> should we go about building a 32-bit and 64-bit libgcc?

This is firmly in multilib territory as its not just libgcc but libc as
well and so it goes on.

One of the reasons I'm nervous of the patch you're replying to is that
people are now going to try and cross the two and we'll end up with a
mess :(.

Trying to build just libgcc from the gcc tree is a nightmare and when we
last tried it, caused no end of problems.

What specific problem are you trying to solve?

Cheers,

Richard






  reply	other threads:[~2011-11-25 23:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 12:29 [PATCH v3] Introduce multiarch DISTRO_FEATURE Julian Pidancet
2011-11-25 19:07 ` McClintock Matthew-B29882
2011-11-25 23:40   ` Richard Purdie [this message]
2011-11-28 21:32     ` McClintock Matthew-B29882
2011-11-28 22:14       ` Julian Pidancet
2011-11-28 22:22         ` Khem Raj
2011-11-28 22:24           ` McClintock Matthew-B29882
2011-11-28 22:56       ` Richard Purdie
2011-11-28 23:00         ` McClintock Matthew-B29882
2011-11-29 12:30           ` Richard Purdie
2011-11-29 16:10             ` McClintock Matthew-B29882
2011-11-29 21:48               ` McClintock Matthew-B29882
2011-11-30  1:05                 ` McClintock Matthew-B29882
2011-11-29 15:48 ` Saul Wold
2011-11-29 15:58   ` Julian Pidancet
2011-11-30 21:21     ` Saul Wold
2011-12-01  0:01       ` [PATCH] Fix " Julian Pidancet
2011-11-30 23:35         ` 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=1322264404.25382.4.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B29882@freescale.com \
    --cc=julian.pidancet@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