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 23:39:00 -0000	[thread overview]
Message-ID: <530E7B42.5070409@linaro.org> (raw)
In-Reply-To: <CAOYw7dvqaneKTLMBgbRzJo06UUkOSDTkMF-K6dZO9mC_VF2-Ug@mail.gmail.com>

Hello Ray, Brian, and everyone else,

On 02/26/14 15:05, Ray Donnelly wrote:
> AFAIK, Bryan Hundven was going to exclude --with-multilib-list for arm
> if gcc < 4.9, and exclude it altogether for all arches other than Intel,
> arm and sh.

It seems like a lot of initial (and on-going) work (multilib_add_archs)
to keep track of which architectures and which versions have multilib
support. I guess it would help users from accidentally creating invalid
configurations, but on the other hand I can't help think it would be
easier and more flexible to have the option always available (when
multilib is selected) and include a strongly worded help message instead :-)

In my case I'd like to use it to build multilib toolchains using the
"custom" version. Could that scenario be added too? It looks like that
won't be easy. I think it would be safe to assume if a user is
performing a build using custom versions that they're knowledgeable
enough to know if they want multilib. It reminds me of the patches you
have to add snapshots and additional versions.

I still think it would just be best to provide the list option if the
user selects multilib since there's a decent chance they might know what
they're doing and a missing multilib list isn't a problem.

It looks like your focus is on 32-bit versus 64-bit tools and libraries.
All I'm looking for is to specify multiple architectures (e.g. armv6-m
armv7e-m). I'm not sure the work you're doing will accommodate my
use-case too. But I'll do some investigation and testing and let you
know how it goes.


> 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.
>
>
> I'm also quite new to mercurial, so someone may need to correct me.
> Tutorial:
> http://mercurial.selenic.com/wiki/MqTutorial

Thank you so much for that list! The "qclone" and "qpush -a" commands
were especially helpful!

Best regards,
    Trevor

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

  reply	other threads:[~2014-02-26 23:39 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   ` multilib-list Trevor Woerner
2014-02-26 20:05     ` multilib-list Ray Donnelly
2014-02-26 23:39       ` Trevor Woerner [this message]
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=530E7B42.5070409@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).