From: Jakub Jelinek <jakub@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Sam James <sam@gentoo.org>, GCC Development <gcc@gcc.gnu.org>,
c-std-porting@lists.linux.dev
Subject: Re: C89isms in the test suite
Date: Mon, 21 Nov 2022 12:12:58 +0100 [thread overview]
Message-ID: <Y3tdOrLxSetT4+u+@tucnak> (raw)
In-Reply-To: <8735amymlt.fsf@oldenburg.str.redhat.com>
On Mon, Nov 14, 2022 at 09:19:26AM +0100, Florian Weimer wrote:
> * Sam James:
>
> > Would you be able to backport 6be2672e4ee41c566a9e072088cccca263bab5f7
> > and 885b6660c17fb91980b5682514ef54668e544b02 to the active <13
> > branches?
>
> Jakub, okay to backport these two (to 12, 11, 10 I presume)?
Ok.
> commit 6be2672e4ee41c566a9e072088cccca263bab5f7
> Author: Florian Weimer <fweimer@redhat.com>
> Date: Tue Oct 18 16:58:48 2022 +0200
>
> libsanitizer: Avoid implicit function declaration in configure test
>
> libsanitizer/
>
> * configure.ac (sanitizer_supported): Include <unistd.h> for
> syscall prototype.
> * configure: Regenerate.
>
> commit 885b6660c17fb91980b5682514ef54668e544b02
> Author: Florian Weimer <fweimer@redhat.com>
> Date: Tue Oct 18 16:58:48 2022 +0200
>
> libiberty: Fix C89-isms in configure tests
>
> libiberty/
>
> * acinclude.m4 (ac_cv_func_strncmp_works): Add missing
> int return type and parameter list to the definition of main.
> Include <stdlib.h> and <string.h> for prototypes.
> (ac_cv_c_stack_direction): Add missing
> int return type and parameter list to the definitions of
> main, find_stack_direction. Include <stdlib.h> for exit
> prototype.
> * configure: Regenerate.
Jakub
prev parent reply other threads:[~2022-11-21 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wn8tbmdr.fsf@oldenburg.str.redhat.com>
2022-11-14 4:36 ` C89isms in the test suite Sam James
2022-11-14 8:19 ` Florian Weimer
2022-11-15 5:05 ` Sam James
2022-11-21 11:12 ` Jakub Jelinek [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=Y3tdOrLxSetT4+u+@tucnak \
--to=jakub@redhat.com \
--cc=c-std-porting@lists.linux.dev \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=sam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.