public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: Ray Donnelly <mingw.android@gmail.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: multilib-list
Date: Wed, 26 Feb 2014 19:52:00 -0000	[thread overview]
Message-ID: <530E45F5.1040404@linaro.org> (raw)
In-Reply-To: <CAOYw7duX-_vbiszjD7xvcWxdZiuOpvoECorbz+Q+RK6Atpd5YQ@mail.gmail.com>

Hello Ray,

On 02/26/14 13:33, Ray Donnelly wrote:
>  AFAIK --with-multilib-list is only supported on intel and sh and in
> GCC 4.9 it's also supported for arm.

Specifically I have been working with the gcc-arm-embedded code from
https://launchpad.net/gcc-arm-embedded (and I've noticed some of the
contributors to that project are also subscribed to this list). I assume
it is this work which will eventually be the gcc-4.9 you mention?

> 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

Any chance you could point me to some information on how to use a second
remote patch queue with mercurial? I would like to work with these
patches, but I'm rather new to mercurial, never mind its queue add-on.

Why not just have a patch that allows the user to specify the list
themselves?

diff -r 043b9b789b7d config/target.in
--- a/config/target.in  Wed Feb 26 13:53:25 2014 -0500
+++ b/config/target.in  Wed Feb 26 14:45:22 2014 -0500
@@ -77,6 +77,15 @@
       NOTE: The multilib feature in crosstool-NG is not well-tested.
             Use at your own risk, and report success and/or failure.
 
+config MULTILIB_LIST
+    string
+    prompt "Additional multilib architectures to support"
+    depends on MULTILIB
+    default ""
+    help
+      Provide GCC with a comma-separated list of additional
architectures for
+      which to build multilib support.
+
 #--------------------------------------
 config ARCH_SUPPORTS_BOTH_MMU
     bool
diff -r 043b9b789b7d scripts/build/cc/gcc.sh
--- a/scripts/build/cc/gcc.sh   Wed Feb 26 13:53:25 2014 -0500
+++ b/scripts/build/cc/gcc.sh   Wed Feb 26 14:45:22 2014 -0500
@@ -377,6 +377,9 @@
 
     if [ "${CT_MULTILIB}" = "y" ]; then
         extra_config+=("--enable-multilib")
+        if [ -n "${CT_MULTILIB_LIST}" ]; then
+            extra_config+=("--with-multilib-list=${CT_MULTILIB_LIST}")
+        fi
     else
         extra_config+=("--disable-multilib")
     fi


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2014-02-26 19:52 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 ` multilib-list Ray Donnelly
2014-02-26 19:52   ` Trevor Woerner [this message]
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=530E45F5.1040404@linaro.org \
    --to=trevor.woerner@linaro.org \
    --cc=crossgcc@sourceware.org \
    --cc=mingw.android@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).