public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/47733] New: psignal (int, const? char*) in libiberty/strsignal.h
Date: Mon, 14 Feb 2011 14:56:00 -0000 [thread overview]
Message-ID: <bug-47733-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47733
Summary: psignal (int, const? char*) in libiberty/strsignal.h
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dilyan.palauzov@aegee.org
I compile gcc with:
../gcc-4.5.2/configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--enable-threads=posix --enable-languages=c,c++ --enable-targets=all
--with-newlib --with-build-time-tools=/usr/x86_64-pc-linux-gnu/bin/
--disable-shared --disable-libgomp --disable-lto --disable-libssp
--disable-libmudflap
libiberty/strsignal.c compiles differently, depending on if HAVE_PSIGNAL is
defined or not.
HAVE_PSIGNAL is nowhere defined in the whole gcc-4.5.2 tree.
In turn strsignal.c defines in all cases a function
void
psignal (int signo, char *message)
In libc-2.13 signal.h defines the function as
void
psignal (int __sig, __const char *__s);
When I compile gcc 4.5.2 with the above configuration I get the message:
[...]
/src/gcc452-build/./gcc/xgcc -B/src/gcc452-build/./gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
/usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include
-c -DHAVE_CONFIG_H -O3 -I. -I../../../gcc-4.5.2/libiberty/../include -W -Wall
-Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic
../../../gcc-4.5.2/libiberty/strsignal.c -o strsignal.o
../../../gcc-4.5.2/libiberty/strsignal.c:554:1: error: conflicting types for
'psignal'
/usr/include/signal.h:150:13: note: previous declaration of 'psignal' was here
make[2]: *** [strsignal.o] Error 1
make[2]: Leaving directory `/src/gcc452-build/i686-pc-linux-gnu/libiberty'
make[1]: *** [all-target-libiberty] Error 2
make[1]: Leaving directory `/src/gcc452-build'
make: *** [all] Error 2
Changing in libiberty/strsignal.c
psignal (int signo, char *message)
with
psignal (int signo, const char *message)
does solve the problem.
next reply other threads:[~2011-02-14 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 14:56 dilyan.palauzov at aegee dot org [this message]
2011-06-01 15:06 ` [Bug other/47733] " jan.smets@alcatel-lucent.com
2011-06-22 20:20 ` hp at gcc dot gnu.org
2011-06-22 21:31 ` hp at gcc dot gnu.org
2011-06-27 20:57 ` hp at gcc dot gnu.org
2011-06-27 21:06 ` hp at gcc dot gnu.org
2011-12-15 1:44 ` pinskia at gcc dot gnu.org
2011-12-15 1:46 ` pinskia at gcc dot gnu.org
2011-12-15 1:52 ` pinskia at gcc dot gnu.org
2012-01-15 19:24 ` pinskia at gcc dot gnu.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-47733-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).