From: Andreas Schwab <schwab@linux-m68k.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: libc-alpha@sourceware.org, Mao Han <han_mao@linux.alibaba.com>,
Joseph Myers <joseph@codesourcery.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Darius Rad <darius@bluespec.com>,
Andrew Waterman <andrew@sifive.com>, DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH v2 2/4] m68k: Use an autoconf template to produce `preconfigure'
Date: Fri, 13 May 2022 10:12:43 +0200 [thread overview]
Message-ID: <87o801lukk.fsf@igel.home> (raw)
In-Reply-To: <alpine.DEB.2.20.2205122257100.10833@tpp.orcam.me.uk> (Maciej W. Rozycki's message of "Thu, 12 May 2022 23:28:54 +0100 (BST)")
On Mai 12 2022, Maciej W. Rozycki wrote:
> Switch to using AC_MSG_ERROR rather than `echo' and `exit' directly for
> error handling. Owing to the lack of any kind of error annotation it
> makes it difficult to spot the message in the flood in a parallel build
> and neither it is logged in `config.log'.
Ok.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-05-13 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 22:28 [PATCH v2 0/4] Avoid relying on autoconf internals in `preconfigure' scripts Maciej W. Rozycki
2022-05-12 22:28 ` [PATCH v2 1/4] C-SKY: Use an autoconf template to produce `preconfigure' Maciej W. Rozycki
2022-05-13 8:12 ` Andreas Schwab
2022-05-12 22:28 ` [PATCH v2 2/4] m68k: " Maciej W. Rozycki
2022-05-13 8:12 ` Andreas Schwab [this message]
2022-05-12 22:29 ` [PATCH v2 3/4] MIPS: " Maciej W. Rozycki
2022-05-13 8:15 ` Andreas Schwab
2022-05-13 16:10 ` Maciej W. Rozycki
2022-05-12 22:29 ` [PATCH v2 4/4] RISC-V: " Maciej W. Rozycki
2022-05-12 22:34 ` Palmer Dabbelt
2022-05-12 22:33 ` [PATCH v2 0/4] Avoid relying on autoconf internals in `preconfigure' scripts Palmer Dabbelt
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=87o801lukk.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=andrew@sifive.com \
--cc=darius@bluespec.com \
--cc=dj@redhat.com \
--cc=han_mao@linux.alibaba.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@embecosm.com \
--cc=palmer@dabbelt.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).