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: Thu, 27 Feb 2014 08:16:00 -0000	[thread overview]
Message-ID: <530EF441.1060302@linaro.org> (raw)
In-Reply-To: <CAOYw7dvR=TSfB64LoWsEtSbVx66hyQTuY-yOzFgV73uvjK92zw@mail.gmail.com>

On 02/26/14 19:37, Ray Donnelly wrote:
>> 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'm not sure what you mean about "custom" version.

Under "Paths and misc options" a user can specify a "Directory
containing custom source components" (CT_CUSTOM_LOCATION_ROOT_DIR). Then
under "Binary utilities" (for example) when choosing the "binutils
version" the user can select "Custom". If no "Full path to custom
binutils source" (CT_BINUTILS_CUSTOM_LOCATION) is provided, crosstool-NG
will look in:

    ${CT_CUSTOM_LOCATION_ROOT_DIR}/binutils

for the binutils source. The same is true for the C compiler version, C
library version, gdb version, and probably others.

This is (IMHO) a very nice feature! In my case I'm investigating using
crosstool-NG to build a toolchain based on the gcc-arm-embedded
sources[1]. Unfortunately the sources for this toolchain are provided as
one tarball which contains the tarballs of all the sub-components (i.e.
gcc, newlib, binutils, etc). Having this feature in crosstool-NG makes
working with these sources much easier and I'm very glad such a thing is
available.

In this case, the gcc-arm-embedded source, although indicated as 4.8.3,
does include multilib capabilities. If the multilib support in
crosstool-NG requires gcc-4.9 or better for ARM toolchains I won't be
able to provide the list of multilib targets for this build.

I think if a crosstool-NG user is making use of the "custom" feature,
there's a chance they're working with pre-release software. In which
case making the multilib facility available would be a good idea. Either
that or abandon trying to determine a priori (based on version number +
architecture alone) which combinations should allow a user to specify
the multilib list :-)



[1] https://launchpad.net/gcc-arm-embedded

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

      parent reply	other threads:[~2014-02-27  8:16 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       ` 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           ` Trevor Woerner [this message]

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=530EF441.1060302@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).