From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-devel@lists.openembedded.org
Subject: "krb" fails to build, suspect GCC bug
Date: Sat, 05 Sep 2015 14:39:14 +0200 [thread overview]
Message-ID: <55EAE272.5010904@topic.nl> (raw)
I got this weird build failure from the "krb" package:
| make[3]: Entering directory
'/TOPDIR/build/tmp/work/mips32el-oe-linux/krb5/1.13.2-r0/krb5-1.13.2/src/lib/krb5/ccache'
| mipsel-oe-linux-gcc -mel -mabi=32 -mhard-float -march=mips32
--sysroot=/TOPDIR/build/tmp/sysroots/formuler1 -fPIC -DSHARED
-DHAVE_CONFIG_H -I../../../include -I../../../include -I./ccapi -I. -I.
-DKRB5_DEPRECATED=1 -DKRB5_PRIVATE -Os -pipe -g
-feliminate-unused-debug-types -DDESTRUCTOR_ATTR_WORKS=1
-I/TOPDIR/build/tmp/sysroots/formuler1/usr/include/et -Wall -Wcast-align
-Wshadow -Wmissing-prototypes -Wno-format-zero-length -Woverflow
-Wstrict-overflow -Wmissing-format-attribute -Wmissing-prototypes
-Wreturn-type -Wmissing-braces -Wparentheses -Wswitch -Wunused-function
-Wunused-label -Wunused-variable -Wunused-value -Wunknown-pragmas
-Wsign-compare -Werror=uninitialized -Werror=pointer-arith
-Werror=declaration-after-statement
-Werror-implicit-function-declaration -pthread -c cc_file.c -o
cc_file.so.o && mv -f cc_file.so.o cc_file.so
| cc_file.c: In function 'fcc_next_cred':
| cc_file.c:368:9: error: 'maxsize' may be used uninitialized in this
function [-Werror=maybe-uninitialized]
| ret = load_data(context, id, maxsize, buf);
| ^
| cc_file.c:1091:12: note: 'maxsize' was declared here
| size_t maxsize;
| ^
| cc1: some warnings being treated as errors
Looking at the source, this doesn't make any sense at all. The
declaration of the variable isn't even in the same method body. And the
line it complains about is about the fifth time it passes that variable
to another method.
And working around it by initializing maxsize=0 just makes the compiler
choke on a similar situation elsewhere:
| packet.c:50:67: error: 'id' may be used uninitialized in this function
I suspect the problem here is GCC and not the krb code. Anyone seen this?
--
Mike Looijmans
next reply other threads:[~2015-09-05 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 12:39 Mike Looijmans [this message]
2015-10-27 18:21 ` "krb" fails to build, suspect GCC bug Martin Jansa
2015-10-27 18:26 ` Khem Raj
2015-10-27 19:57 ` Martin Jansa
2015-10-27 20:25 ` Martin Jansa
2015-10-28 8:23 ` Mike Looijmans
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=55EAE272.5010904@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.