From: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
To: Cody P Schafer <dev@codyps.com>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Multilib problem
Date: Mon, 03 Feb 2014 18:39:00 -0000 [thread overview]
Message-ID: <52EFE250.4030700@coloradoengineeringinc.com> (raw)
In-Reply-To: <52E2EAA0.3050605@codyps.com>
Cody, All:
Unfortunately, after your patch, the same problem persists. Have you
been able to look at this at all since?
Thanks,
Danny
On 01/24/2014 03:35 PM, Cody P Schafer wrote:
> On 01/24/2014 02:28 PM, Cody P Schafer wrote:
>>
>>
>> On 01/23/2014 02:37 PM, Danny Gale wrote:
>>> Hi all,
>>>
>>> I've successfully compiled my powerpc64-e6500-linux-gnu toolchain!
>>> Hooray! :)
>>>
>>> Now, the trouble is that U-Boot doesn't support 64-bit powerpc builds,
>>> so the toolchain needs to have multilib enabled. The compiler itself is
>>> built with no problem, but during the "Building for multilib
>>> subdir='32'" step, the build fails with this error:
>>
>> The problem with multilib on powerpc (and x86, and possibly others) is
>> that glibc (and probably other libcs) use the target to determine which
>> api to build for the arch. To explain: powerpc64-e6500-linux-gnu passed
>> to glibc's configure will always try to build a 64bit libc. One needs to
>> pass powerpc-e6500-linux-gnu and then override the place to find CC,LD,
>> and the like as well as the result directory. The only crossbuild tool I
>> know of that actually is able to do this is gentoo's "crossdev". I've
>> been working on some patches to try to get similar functionality in
>> crosstool-ng, but they're nowhere near ready
>> (https://bitbucket.org/jmesmon/crosstool-ng-pq/ is my patchqueue which
>> includes them).
>
> Direct link to the interesting (but untested) patch:
> https://bitbucket.org/jmesmon/crosstool-ng-pq/src/1fde229c1e3b036dcd8d58cd3cc40a889ad7486b/multilib-libc-fixup.patch?at=default
>
>
> And this is what crossdev uses to do it's heavy lifting w.r.t. multilib:
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/multilib.eclass?revision=1.105&view=markup
>
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-02-03 18:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 22:37 Danny Gale
2014-01-24 17:16 ` Harold Grovesteen
2014-01-24 22:28 ` Cody P Schafer
2014-01-24 22:35 ` Cody P Schafer
2014-01-24 23:00 ` Ray Donnelly
2014-02-03 18:39 ` Danny Gale [this message]
2014-02-03 22:17 ` Cody P Schafer
2014-02-04 2:49 ` Bryan Hundven
2014-02-04 0:39 ` Bryan Hundven
[not found] ` <52F03B5F.1000504@coloradoengineeringinc.com>
[not found] ` <CAJ+oik0PQd_0e6=RrdeTpg550pa3FJP0s=t8A5mD-Vten4jRNA@mail.gmail.com>
2014-02-04 1:08 ` Bryan Hundven
2014-02-04 1:11 ` Bryan Hundven
2014-02-04 1:12 ` Bryan Hundven
2014-02-04 17:45 ` Danny Gale
2014-02-04 18:29 ` Bryan Hundven
2014-02-04 18:39 ` Ray Donnelly
2014-02-04 22:18 ` Cody P Schafer
2014-02-12 6:01 ` Bryan Hundven
2014-02-12 7:52 ` Ray Donnelly
[not found] ` <52F13ECA.7060803@coloradoengineeringinc.com>
2014-02-07 7:42 ` Bryan Hundven
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=52EFE250.4030700@coloradoengineeringinc.com \
--to=daniel.gale@coloradoengineeringinc.com \
--cc=crossgcc@sourceware.org \
--cc=dev@codyps.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).