From: Jim Meyering <jim@meyering.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: any pending fixes? preparing for diffutils release
Date: Sun, 1 Aug 2021 22:48:51 -0700 [thread overview]
Message-ID: <CA+8g5KGeNriBj1VZ0ncqvVXqZxHOMu9iw+QNDHmsKTE-BLEcTQ@mail.gmail.com> (raw)
In-Reply-To: <61404f5d-d1c7-047f-8a4d-5fb7e61bc04a@cs.ucla.edu>
On Sun, Aug 1, 2021 at 10:36 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
> One minor problem I just discovered with the now-released diffutils 3.8,
> a problem that was caused by my recent Gnulib changes, is that building
> diffutils on RHEL 8.4 results in diagnostics like the following:
>
> In file included from dirname.c:25:
> xalloc.h:133:3: warning: 'malloc (rpl_free)' attribute ignored on
> functions declared 'inline' [-Wattributes]
> 133 | _GL_ATTRIBUTE_ALLOC_SIZE ((1, 2)) _GL_ATTRIBUTE_RETURNS_NONNULL;
> | ^~~~~~~~~~~~~~~~~~~~~~~~
>
>
> These diagnostics are annoying but otherwise harmless. I just now
> installed a Gnulib patch to fix this, here:
>
> https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=9b69ffb766a2f6c0a06ad4b71040209534fde094
Thanks. I won't wait 2.5 years for the next release :-)
prev parent reply other threads:[~2021-08-02 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 19:44 any pending fixes? preparing for diffutils release Jim Meyering
2021-08-01 22:14 ` Paul Eggert
2021-08-02 0:53 ` Jim Meyering
2021-08-02 5:36 ` Paul Eggert
2021-08-02 5:48 ` 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+8g5KGeNriBj1VZ0ncqvVXqZxHOMu9iw+QNDHmsKTE-BLEcTQ@mail.gmail.com \
--to=jim@meyering.net \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).