From: Steve Ellcey <sellcey@caviumnetworks.com>
To: Joseph Myers <joseph@codesourcery.com>, <libc-alpha@sourceware.org>
Subject: Re: Add script to build many glibc configurations
Date: Thu, 10 Nov 2016 17:09:00 -0000 [thread overview]
Message-ID: <1478797774.4630.80.camel@caviumnetworks.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611091625430.7263@digraph.polyomino.org.uk>
On Wed, 2016-11-09 at 16:27 +0000, Joseph Myers wrote:
> This patch adds a Python (3.5 or later) script to build many
> different
> configurations of glibc, including building the required cross
> compilers first.  It's not intended to change any patch testing
> requirements, although some people may wish to use it for high-risk
> patches such as adding warning options (and it can also be used to
> test building, including compiling tests, for an individual
> configuration, if e.g. you wish to do such a compilation test of a
> patch for an architecture it touches).
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
the maximum flexibility in what glibc libraries to build later but on
the other hand, that is a lot of cross-compilers. Â I could see people
using this script to test the build of a particular platform that they
don't have access to as well as for testing multiple builds. Â What do
you think about allowing a list of targets on the compilers build?
Steve Ellcey
sellcey@caviumnetworks.com
next prev parent reply other threads:[~2016-11-10 17:09 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 [this message]
2016-11-10 17:22 ` Joseph Myers
2016-11-10 17:39 ` Steve Ellcey
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=1478797774.4630.80.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).