c-std-porting.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Sam James <sam@gentoo.org>, GCC Development <gcc@gcc.gnu.org>,
Subject: Re: C89isms in the test suite
Date: Mon, 14 Nov 2022 09:19:26 +0100	[thread overview]
Message-ID: <8735amymlt.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <BAFDDA68-8E38-4EA0-9623-CA32CBFE6192@gentoo.org> (Sam James's message of "Mon, 14 Nov 2022 04:36:17 +0000")

* 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)?

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
            * 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
            * 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
            * configure: Regenerate.


  reply	other threads:[~2022-11-14  8:19 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 [this message]
2022-11-15  5:05     ` Sam James
2022-11-21 11:12     ` Jakub Jelinek

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735amymlt.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=c-std-porting@lists.linux.dev \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=sam@gentoo.org \


* 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 NNTP newsgroup(s).