From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Do not silently continue if config.{build,host,gcc} fails
Date: Mon, 24 Jul 2017 22:23:00 -0000 [thread overview]
Message-ID: <4097353d-06a7-6a49-b790-6fe565517630@redhat.com> (raw)
In-Reply-To: <20170724070313.GQ13471@gate.crashing.org>
On 07/24/2017 01:03 AM, Segher Boessenkool wrote:
> Ping?
>
>
> Segher
>
>
> On Mon, May 15, 2017 at 04:29:24PM +0000, Segher Boessenkool wrote:
>> If config.{build,host,gcc} fails, configure currently silently
>> continues. This then makes it much harder than necessary to notice
>> you made a stupid pasto in config.gcc (and where exactly).
>>
>> This patch fixes it, by terminating if one of the config.* fails.
>>
>> Testing in progress (on powerpc64-linux); is this okay for trunk if
>> it passes?
>>
>>
>> Segher
>>
>>
>> 2017-05-15 Segher Boessenkool <segher@kernel.crashing.org>
>>
>> * configure.ac: If any of the config.* scripts fail, exit 1.
>> * configure: Regenerate.
OK.
jeff
prev parent reply other threads:[~2017-07-24 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 16:48 Segher Boessenkool
2017-07-24 7:03 ` Segher Boessenkool
2017-07-24 22:23 ` Jeff Law [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=4097353d-06a7-6a49-b790-6fe565517630@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).