From: "Arsen Arsenović" <arsen@aarsen.me>
To: Sam James <sam@gentoo.org>
Cc: Gnulib bugs <bug-gnulib@gnu.org>, bug-texinfo@gnu.org
Subject: Re: -Wlto-type-mismatch warning in error()
Date: Wed, 07 Dec 2022 22:10:49 +0100 [thread overview]
Message-ID: <86r0xaj4si.fsf@aarsen.me> (raw)
In-Reply-To: <D666386E-B8DE-4B99-AEF6-6F24A4B97441@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Sam James <sam@gentoo.org> writes:
> ../gnulib/lib/error.h:33:13: error: type of ‘error’ does not match original declaration [-Werror=lto-type-mismatch]
> 33 | extern void error (int __status, int __errnum, const char *__format, ...)
> | ^
> install-info.c:218:1: note: type mismatch in parameter 1
> 218 | error (const char *fmt, ...)
> | ^
> install-info.c:218:1: note: ‘error’ was previously declared here
This appears to be a result of error in install-info.c being non-static.
It could be static, and avoid a potential symbol collision.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2022-12-07 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:57 -Wlto-type-mismatch warning in error() Sam James
2022-12-07 21:10 ` Arsen Arsenović [this message]
2022-12-07 21:37 ` Gavin Smith
2022-12-08 0:21 ` Bruno Haible
2022-12-08 6:16 ` Eli Zaretskii
2022-12-08 8:25 ` Arsen Arsenović via Gnulib discussion list
2022-12-08 10:55 ` Eli Zaretskii
2022-12-08 11:31 ` Arsen Arsenović
2022-12-08 19:00 ` namespacing issues with Gnulib Bruno Haible
2022-12-08 20:10 ` Eli Zaretskii
2022-12-08 20:19 ` Arsen Arsenović
2022-12-08 20:54 ` Paul Eggert
2022-12-10 1:48 ` -Wlto-type-mismatch warning in error() Gavin Smith
2022-12-10 1:50 ` Gavin Smith
2022-12-10 21:42 ` Paul Eggert
2022-12-11 4:24 ` Jeffrey Walton
2022-12-09 12:00 ` Florian Weimer
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=86r0xaj4si.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=bug-gnulib@gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=sam@gentoo.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).