From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@linux-m68k.org>,
"H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: V10 [PATCH] sysconf: Add _SC_MINSIGSTKSZ/_SC_SIGSTKSZ [BZ #20305]
Date: Mon, 19 Jul 2021 16:06:39 -0500 [thread overview]
Message-ID: <e7a5199e-c2e8-a494-e6cf-4c22800a66f6@cs.ucla.edu> (raw)
In-Reply-To: <87tukqpqam.fsf@igel.home>
On 7/19/21 5:10 AM, Andreas Schwab wrote:
> This breaks diffutils.
>
> c-stack.c:55:26: error: missing binary operator before token "("
> 55 | #elif HAVE_LIBSIGSEGV && SIGSTKSZ < 16384
> | ^~~~~~~~
>
> Andreas.
>
I'll start the ball rolling on a new diffutils release, which should fix
the problem.
next prev parent reply other threads:[~2021-07-19 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 13:53 H.J. Lu
2021-07-19 10:10 ` Andreas Schwab
2021-07-19 21:06 ` Paul Eggert [this message]
2021-07-19 11:09 ` Andreas Schwab
2021-07-19 21:06 ` Paul Eggert
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 16:50 PING: V7 " Dave Martin
2020-11-04 17:48 ` H.J. Lu
2020-11-18 14:13 ` H.J. Lu
2020-11-18 14:25 ` Zack Weinberg
2020-11-18 14:40 ` H.J. Lu
2020-11-18 15:12 ` Zack Weinberg
2020-11-18 15:17 ` H.J. Lu
2020-11-18 15:20 ` Florian Weimer
2020-11-18 17:04 ` Dave Martin
2020-11-18 17:35 ` Florian Weimer
2020-11-18 18:09 ` Dave Martin
2020-11-20 14:08 ` H.J. Lu
2020-11-20 14:11 ` Florian Weimer
2020-11-20 23:13 ` V8 " H.J. Lu
2021-01-20 14:16 ` Carlos O'Donell
2021-01-20 15:05 ` V9 " H.J. Lu
2021-01-22 19:41 ` V10 " H.J. Lu
2021-01-25 13:31 ` Carlos O'Donell
2021-01-25 13:57 ` H.J. Lu
2021-01-25 13:59 ` Carlos O'Donell
2021-01-25 13:58 ` Carlos O'Donell
2021-01-25 14:16 ` Florian Weimer
2021-02-02 13:08 ` Carlos O'Donell
2021-01-25 14:34 ` Carlos O'Donell
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=e7a5199e-c2e8-a494-e6cf-4c22800a66f6@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).