From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org, noloader@gmail.com
Cc: Simon Josefsson <simon@josefsson.org>,
Alexandre Duret-Lutz <adl@lrde.epita.fr>,
Jim Meyering <jim@meyering.net>, Paul Smith <psmith@gnu.org>,
Akim Demaille <akim.demaille@gmail.com>
Subject: Re: different CFLAGS for gnulib code?
Date: Fri, 15 Jan 2021 03:11:57 -0800 [thread overview]
Message-ID: <60b3140a-0256-03b5-38c2-2756fab75a36@cs.ucla.edu> (raw)
In-Reply-To: <2567810.aDiGfSFVrs@omega>
On 1/15/21 12:55 AM, Bruno Haible wrote:
> Would compiling the gnulib
> part with options for fewer warnings be OK with you?
Not only is it OK, it's routine. Coreutils, Emacs, etc. do it.
next prev parent reply other threads:[~2021-01-15 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:37 clang++ 11 compilation issues Alexandre Duret-Lutz
2021-01-12 18:23 ` Florian Weimer
2021-01-13 11:31 ` Alexandre Duret-Lutz
2021-01-12 20:19 ` Bruno Haible
2021-01-13 21:04 ` Jeffrey Walton
2021-01-15 8:55 ` different CFLAGS for gnulib code? Bruno Haible
2021-01-15 9:20 ` Alexandre Duret-Lutz
2021-01-15 11:11 ` Paul Eggert [this message]
2021-01-15 16:36 ` Darshit Shah
2021-01-15 11:17 ` Simon Josefsson via Gnulib discussion list
2021-01-15 16:08 ` Jim Meyering
2021-01-17 12:55 ` Pádraig Brady
2021-01-14 0:37 ` clang++ 11 compilation issues Paul Eggert
2021-01-14 1:21 ` Bruno Haible
2021-01-14 1:55 ` Paul Eggert
2021-01-14 2:09 ` Bruno Haible
2021-01-14 18:21 ` Alexandre Duret-Lutz
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=60b3140a-0256-03b5-38c2-2756fab75a36@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=adl@lrde.epita.fr \
--cc=akim.demaille@gmail.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=jim@meyering.net \
--cc=noloader@gmail.com \
--cc=psmith@gnu.org \
--cc=simon@josefsson.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).