bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Bruno Haible <bruno@clisp.org>
Cc: Florian Weimer <fweimer@redhat.com>,
	"bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: Re: make autoconf tests work with -Werror=implicit-function-declaration
Date: Sun, 15 Sep 2019 10:04:25 -0700	[thread overview]
Message-ID: <CA+8g5KFOkf7HiwQd0xEFtz6RXMvx+CKAZ8G-3VJruzhZwqy38w@mail.gmail.com> (raw)
In-Reply-To: <6887158.PPuMJLRhYT@omega>

On Sat, Sep 14, 2019 at 10:51 AM Bruno Haible <bruno@clisp.org> wrote:
> There are indications that future GCC versions may be stricter regarding
> invocations of undeclared functions. [1] Configuring with
>   CC="gcc -Werror=implicit-function-declaration"
> is a way to exercise similar functionality with released GCCs.
>
> So, what I did is
>   1. create a testdir of all of gnulib,
>   2. configure it once with CC="gcc" and once with
>      CC="gcc -Werror=implicit-function-declaration", both with option '-C',
>   3. compare the resulting config.cache files.
>
> I got differences in the cache variables
>   gl_cv_func_ptsname_sets_errno
>   gt_cv_locale_tr_utf8
>
> This patch fixes the issues.
>
> [1] https://lists.gnu.org/archive/html/bug-gettext/2019-09/msg00012.html

Thanks for your constant vigilance and all the proactive work on gnulib.


      reply	other threads:[~2019-09-15 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14 17:50 make autoconf tests work with -Werror=implicit-function-declaration Bruno Haible
2019-09-15 17:04 ` Jim Meyering [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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=CA+8g5KFOkf7HiwQd0xEFtz6RXMvx+CKAZ8G-3VJruzhZwqy38w@mail.gmail.com \
    --to=jim@meyering.net \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=fweimer@redhat.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).