From: Steve Ellcey <sellcey@caviumnetworks.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Add script to build many glibc configurations
Date: Thu, 10 Nov 2016 17:39:00 -0000 [thread overview]
Message-ID: <1478799526.4630.83.camel@caviumnetworks.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611101720070.26763@digraph.polyomino.org.uk>
On Thu, 2016-11-10 at 17:22 +0000, Joseph Myers wrote:
> On Thu, 10 Nov 2016, Steve Ellcey wrote:
>
> >
> > Joseph, it appears that when building the cross compilers, there is
> > no
> > way to restrict that to just the compilers for certain targets. Â Is
> > that correct? Â On one hand I can understand that, since that gives
> > you
> You can specify arguments <dir> compilers target1 target2 ...
>
> (where the targets are ARCH-linux-gnu or ARCH-linux-gnu-variant for
> one ofÂ
> the variants listed in the script).  Then for the glibc step specifyÂ
> similar arguments (note that ARCH and variant names may be different
> forÂ
> the glibcs in cases where a compiler has more than one glibc).
OK, I tried 'aarch64' instead of 'aarch64-linux-gnu' and when I got an
error I thought it meant that targets were not allowed and not that I
had just messed up on the target name. Â Using proper triplet target
names is working much better.
Steve Ellcey
next prev parent reply other threads:[~2016-11-10 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 16:27 Joseph Myers
2016-11-10 14:27 ` Joseph Myers
2016-11-10 16:44 ` Joseph Myers
2016-11-23 17:36 ` Chris Metcalf
2016-11-10 17:09 ` Steve Ellcey
2016-11-10 17:22 ` Joseph Myers
2016-11-10 17:39 ` Steve Ellcey [this message]
2016-11-11 15:20 ` Joseph Myers
2016-11-11 19:37 ` Carlos O'Donell
2016-11-14 15:06 ` Mike Frysinger
2016-11-14 15:23 ` Joseph Myers
2016-11-14 19:27 ` Mike Frysinger
2016-11-14 23:28 ` Joseph Myers
2016-11-14 23:57 ` Joseph Myers
2016-11-17 16:52 ` Zack Weinberg
2016-11-17 17:26 ` Zack Weinberg
2016-11-17 17:47 ` Joseph Myers
2016-11-17 17:54 ` Andreas Schwab
2016-11-17 17:51 ` Joseph Myers
2016-11-18 16:28 ` Zack Weinberg
2016-11-18 18:27 ` Joseph Myers
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=1478799526.4630.83.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).