From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org
Cc: Trevor Woerner <twoerner@gmail.com>
Subject: Re: Built arm-none-eabi with multilib for x86_64-unkown-linux-gnu with crosstool-ng-1.14.0
Date: Thu, 02 Feb 2012 12:57:00 -0000 [thread overview]
Message-ID: <201202021357.37302.yann.morin.1998@free.fr> (raw)
In-Reply-To: <CAHUNapS-Lya==p+9urRyBxYW0G1_v8jZ75-PQ5BPfNJfKMwxOA@mail.gmail.com>
Trevor, All,
On Thursday 02 February 2012 13:40:28 Trevor Woerner wrote:
> I built the arm-cortex_a8-linux-gnueabi sample and enabled multilib:
[--SNIP--]
> When I ask the compiler to list the multilibs I get:
>
> $ ./arm-cortex_a8-linux-gnueabi-gcc -print-multi-lib
> .;
>
> I only have a little experience with multilib-enabled tools, but I
> assume something is missing?
I was not able to build a multi-lib ARM Linux EABI toolchain so far.
Looking at the code in gcc, it seems that all multi-lib definitions
are nuked-out for arm*-*-linux-*gnueabi tupples.
OTOH, the multi-lib _code_ in crosstool-NG works, as I was able to build a
Sparc multi-lib toolchain (but it required a few unrelated Leon patches to
gcc, so it is not available as a sample). Also, Per has submitted a working
bare-metal multi-lib ARM EABI sample yesterday, which means that the
multi-lib support (in crosstooll-NG) if operational.
Basically, it looks like the culprit here is, at least partially, in the gcc
code. It can also be the case that we incorrectly drive the gcc ./configure
and/or make, of course.
This is why I announced it a 'initial support for multi-lib'. The code path
is known to (rather more than less) work. Yes, I could have been more explicit
by stating that there were yet some issues and restrictions.
This means there are still some changes to do to make it ubiquitous, and that
will have to be done is the release cycle(s) to come.
Although I will be working on this on my side, it's not a top-priority for me.
So: patches and .config welcome! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-02-02 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 14:11 Per Arnold Blaasmo
2012-02-01 20:47 ` Yann E. MORIN
2012-02-02 11:15 ` Per Arnold Blaasmo
2012-02-02 12:40 ` Trevor Woerner
2012-02-02 12:57 ` Yann E. MORIN [this message]
2012-02-02 13:01 ` Yann E. MORIN
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=201202021357.37302.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=crossgcc@sourceware.org \
--cc=twoerner@gmail.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).