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: Mon, 28 Nov 2011 22:56:08 +0000 [thread overview]
Message-ID: <1322520968.30225.23.camel@ted> (raw)
In-Reply-To: <CAEsOVNcAR_N2LszE41fTaA=FGXMgtOdnCTLvdMxyYC5+GkTkKg@mail.gmail.com>
On Mon, 2011-11-28 at 21:32 +0000, McClintock Matthew-B29882 wrote:
> On Fri, Nov 25, 2011 at 5:40 PM, Richard Purdie
> > What specific problem are you trying to solve?
>
> The specific issue I'm having is for our 64-bit part that still uses a
> 32-bit u-boot. Not sure the best approach really is...
Hmm, does it really need libgcc?
> I've tried utilizing multilib by adding the following to my u-boot
> recipe, but it's just hacky...
>
> DEPENDS_e5500-64b_append = " lib32-gcc"
> CC_e5500-64b = "powerpc-poky-linux-gcc -m32"
>
> I'd rather NOT recompile gcc/eglibc/etc just for this 32-bit build of
> u-boot where we don't need libc. I'd rather just have a functional
> 32bit/64bit compiler for our 64-bit target.
The trouble is that you need glibc-intermediate to build gcc-cross
(which builds a functional libgcc). You therefore can't short circuit
this as much as you think :/.
> Looking forward farther, I would like to have one toolchain
> ("meta-toolchain") that can produce target code for multiple targets
> also.
This is easier since we would just add lib32-gcc and lib-gcc to the
sysroot. It then becomes a case of just ensuring gcc is configured
correctly.
Cheers,
Richard
next prev parent reply other threads:[~2011-11-28 23:02 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
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 [this message]
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=1322520968.30225.23.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