From: Jeff Law <law@redhat.com>
To: Mike Stump <mikestump@comcast.net>
Cc: "gcc-patches@gcc.gnu.org Patches" <gcc-patches@gcc.gnu.org>,
Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: RFA: speeding up dg-extract-results.sh
Date: Mon, 05 May 2014 18:16:00 -0000 [thread overview]
Message-ID: <5367D594.9080002@redhat.com> (raw)
In-Reply-To: <2C317396-8207-4571-A9A3-604871918E2C@comcast.net>
On 05/05/14 12:14, Mike Stump wrote:
> On May 5, 2014, at 9:08 AM, Jeff Law <law@redhat.com> wrote:
>> It would mean a bit of pain for initial system bootstraps by the
>> distributors,
>
> I donÂ’t expect any pain there. System distributors usually have a
> distribution for the last release that includes binaries for all,
> including python, tcl and gcc. They merely use these to then build
> the new software. I donÂ’t know of any that donÂ’t start with binaries
> someplace. :-)
I'm referring to new system bringups -- ie, there is no prior release to
build from. There's a couple of those in progress right now. Package
interdependencies are a real problem, but as I stated, this in case
python is limited to the testsuite, which can be disabled during the
initial building phases.
jeff
next prev parent reply other threads:[~2014-05-05 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 9:18 Richard Sandiford
2014-05-03 7:34 ` Ping: " Richard Sandiford
2014-05-05 19:17 ` Jakub Jelinek
2014-05-05 20:36 ` Richard Sandiford
2014-05-03 20:07 ` Mike Stump
2014-05-05 16:08 ` Jeff Law
2014-05-05 18:15 ` Mike Stump
2014-05-05 18:16 ` Jeff Law [this message]
[not found] ` <CADnVucCA0ozSz=x3z8vexBOkWRj3pquKVuWsFq4xZre0CfxFyQ@mail.gmail.com>
2014-05-19 18:07 ` Richard Sandiford
2014-05-19 18:49 ` Charles Baylis
2014-05-20 10:09 ` Richard Sandiford
2014-05-24 11:17 ` Bernd Schmidt
2014-05-24 17:15 ` Mike Stump
2014-05-24 17:53 ` Trevor Saunders
2014-05-25 9:35 ` Richard Sandiford
2014-06-12 15:53 ` Bernd Schmidt
2014-06-12 16:32 ` Mike Stump
2014-06-14 9:50 ` Richard Sandiford
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=5367D594.9080002@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=rdsandiford@googlemail.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).