public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Sat, 25 Sep 2021 01:20:43 +0000 [thread overview]
Message-ID: <bug-91092-4-9SD4hb86B0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #20 from Eric Gallager <egallager at gcc dot gnu.org> ---
So, Apple turned on -Werror=implicit-function-declaration on by default for
their version of clang that ships with macOS, and in response, the MacPorts
project has added features to scan the config.log files of ports built with it
for instances of -Werror=implicit-function-declaration and report them. As
expected, it does indeed turn up a lot of results, but work is being done to
fix them all, producing patches for the configure scripts in many cases.
Upstream projects will just need to apply these patches in order to be ready.
next parent reply other threads:[~2021-09-25 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91092-4@http.gcc.gnu.org/bugzilla/>
2021-09-25 1:20 ` egallager at gcc dot gnu.org [this message]
2022-09-12 20:18 ` sam at gentoo dot org
2023-12-01 7:12 ` cvs-commit at gcc dot gnu.org
2023-12-01 7:15 ` fw at gcc dot gnu.org
2023-12-01 8:20 ` sjames at gcc dot gnu.org
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=bug-91092-4-9SD4hb86B0@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).