From: Ray Donnelly <mingw.android@gmail.com>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: multilib-list
Date: Wed, 26 Feb 2014 18:33:00 -0000 [thread overview]
Message-ID: <CAOYw7duX-_vbiszjD7xvcWxdZiuOpvoECorbz+Q+RK6Atpd5YQ@mail.gmail.com> (raw)
In-Reply-To: <530E2237.50603@linaro.org>
Hi Trevor,
AFAIK --with-multilib-list is only supported on intel and sh and in
GCC 4.9 it's also supported for arm.
If you're interested in multilib support, a few of us have been
contributing to the following patch queue:
https://bitbucket.org/bhundven/crosstool-ng-multilib
On Wed, Feb 26, 2014 at 5:19 PM, Trevor Woerner
<trevor.woerner@linaro.org> wrote:
> Hi everyone,
>
> The help text for crosstool-NG's MULTILIB configuration option states:
>
> "The list of variants is dependent on the architecture, and is
> hard-coded in gcc, so it is not possible to say what variants to
> support, only whether hard-coded variants should be supported or not."
>
> Isn't this the purpose of gcc's --with-multilib-list option? Doesn't
> this allow the user to select which multilib variants to build?
>
> Best regards,
> Trevor
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-02-26 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 17:19 multilib-list Trevor Woerner
2014-02-26 18:33 ` Ray Donnelly [this message]
2014-02-26 19:52 ` multilib-list Trevor Woerner
2014-02-26 20:05 ` multilib-list Ray Donnelly
2014-02-26 23:39 ` multilib-list Trevor Woerner
2014-02-27 0:37 ` multilib-list Ray Donnelly
2014-02-27 6:37 ` multilib-list Cody P Schafer
2014-02-27 8:16 ` multilib-list Trevor Woerner
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=CAOYw7duX-_vbiszjD7xvcWxdZiuOpvoECorbz+Q+RK6Atpd5YQ@mail.gmail.com \
--to=mingw.android@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=trevor.woerner@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).