From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/23884] New: error: ‘__elf32_msize’ specifies less restrictive attribute than its target ‘elf32_fsize’: ‘const’ [-Werror=missing-attributes]
Date: Thu, 15 Nov 2018 08:48:00 -0000 [thread overview]
Message-ID: <bug-23884-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23884
Bug ID: 23884
Summary: error: ‘__elf32_msize’ specifies less restrictive
attribute than its target ‘elf32_fsize’: ‘const’
[-Werror=missing-attributes]
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libelf
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
It's a new warning that comes with recent GCC 9:
$ make V=1
make --no-print-directory all-recursive
Making all in config
make[2]: Nothing to be done for 'all'.
Making all in m4
make[2]: Nothing to be done for 'all'.
Making all in lib
make[2]: Nothing to be done for 'all'.
Making all in libelf
gcc -D_GNU_SOURCE -DHAVE_CONFIG_H -DLOCALEDIR='"/usr/local/share/locale"' -I.
-I.. -I. -I. -I../lib -I.. -std=gnu99 -Wall -Wshadow -Wformat=2
-Wold-style-definition -Wstrict-prototypes -Wlogical-op -Wduplicated-cond
-Wnull-dereference -Wimplicit-fallthrough=5 -Werror -Wunused -Wextra
-Wstack-usage=262144 -D_FORTIFY_SOURCE=2 -g -O2 -MT elf32_fsize.o -MD -MP
-MF .deps/elf32_fsize.Tpo -c -o elf32_fsize.o elf32_fsize.c
In file included from ../config.h:134,
from elf32_fsize.c:31:
libelfP.h:47:30: error: ‘__elf32_msize’ specifies less restrictive attribute
than its target ‘elf32_fsize’: ‘const’ [-Werror=missing-attributes]
47 | #define __elfw2_(Bits, Name) __elf##Bits##_##Name
| ^~~~~
../lib/eu-config.h:60:26: note: in definition of macro ‘strong_alias’
60 | extern __typeof (name) aliasname __attribute__ ((alias (#name)));
| ^~~~~~~~~
elf32_fsize.c:68:1: note: in expansion of macro ‘local_strong_alias’
68 | local_strong_alias (elfw2(LIBELFBITS, fsize), __elfw2(LIBELFBITS,
msize))
| ^~~~~~~~~~~~~~~~~~
libelfP.h:52:29: note: in expansion of macro ‘__elfw2_’
52 | #define __elfw2(Bits, Name) __elfw2_(Bits, Name)
| ^~~~~~~~
elf32_fsize.c:68:47: note: in expansion of macro ‘__elfw2’
68 | local_strong_alias (elfw2(LIBELFBITS, fsize), __elfw2(LIBELFBITS,
msize))
| ^~~~~~~
In file included from elf32_fsize.c:35:
libelfP.h:48:28: note: ‘__elf32_msize’ target declared here
48 | #define elfw2_(Bits, Name) elf##Bits##_##Name
| ^~~
libelfP.h:53:27: note: in expansion of macro ‘elfw2_’
53 | #define elfw2(Bits, Name) elfw2_(Bits, Name)
| ^~~~~~
elf32_fsize.c:43:1: note: in expansion of macro ‘elfw2’
43 | elfw2(LIBELFBITS, fsize) (Elf_Type type, size_t count, unsigned int
version)
| ^~~~~
cc1: all warnings being treated as errors
make[2]: *** [Makefile:786: elf32_fsize.o] Error 1
make[1]: *** [Makefile:485: all-recursive] Error 1
make: *** [Makefile:401: all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-11-15 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 8:48 mliska at suse dot cz [this message]
2018-11-15 16:03 ` [Bug libelf/23884] " mark at klomp dot org
2018-11-15 16:17 ` mark at klomp dot org
2018-11-16 8:31 ` mark at klomp dot 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-23884-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).