From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Subject: build error with latest gir tree at a 32 bit Linux
Date: Thu, 06 Mar 2014 18:18:43 +0100 [thread overview]
Message-ID: <5318ADF3.5030905@gmx.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
i686-pc-linux-gnu-gcc -O2 -march=native -pipe -g -ggdb -Wall -W -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -D__linux__ -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wlogical-op -Wnested-externs -Wpacked -Wshadow -Wstrict-aliasing=3 -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Werror -Wl,-O1 -Wl,--as-needed -o interesting-numbers.o -c interesting-numbers.c
i686-pc-linux-gnu-gcc -O2 -march=native -pipe -g -ggdb -Wall -W -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -D__linux__ -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wlogical-op -Wnested-externs -Wpacked -Wshadow -Wstrict-aliasing=3 -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Werror -Wl,-O1 -Wl,--as-needed -o locks.o -c locks.c
i686-pc-linux-gnu-gcc -O2 -march=native -pipe -g -ggdb -Wall -W -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -D__linux__ -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wlogical-op -Wnested-externs -Wpacked -Wshadow -Wstrict-aliasing=3 -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Werror -Wl,-O1 -Wl,--as-needed -o log.o -c log.c
locks.c: In function ‘lock’:
locks.c:4:19: error: declaration of ‘lock’ shadows a global declaration [-Werror=shadow]
locks.c:4:6: error: shadowed declaration is here [-Werror=shadow]
locks.c: In function ‘unlock’:
locks.c:12:21: error: declaration of ‘lock’ shadows a global declaration [-Werror=shadow]
locks.c:4:6: error: shadowed declaration is here [-Werror=shadow]
cc1: all warnings being treated as errors
make: *** [locks.o] Error 1
make: *** Waiting for unfinished jobs....
* ERROR: dev-util/trinity-9999::toralf failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=dev-util/trinity-9999::toralf'`,
- --
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlMYrfIACgkQxOrN3gB26U4W2AD9EjBYwm07R8MgTHt0x8HwwNtD
h89c9Ebx7VZAkGW7e8cA+gKUgk+wfe69o2r55Sz2drcj4gKb3yTWxj3ON08I59QF
=w/Mb
-----END PGP SIGNATURE-----
next reply other threads:[~2014-03-06 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:18 Toralf Förster [this message]
2014-03-07 18:16 ` build error with latest gir tree at a 32 bit Linux Dave Jones
2014-03-07 18:42 ` Toralf Förster
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=5318ADF3.5030905@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=trinity@vger.kernel.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).