public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/40610]  New: [4.5 Regression] hppa-linux trunk/libiberty/strsignal.c:554:1: error: conflicting types for 'psignal'
@ 2009-07-01 18:08 laurent at guerby dot net
  2009-07-01 18:09 ` [Bug bootstrap/40610] " bonzini at gnu dot org
  0 siblings, 1 reply; 2+ messages in thread
From: laurent at guerby dot net @ 2009-07-01 18:08 UTC (permalink / raw)
  To: gcc-bugs

On farm machine gcc61:

/home/guerby/build/./prev-gcc/xgcc -B/home/guerby/build/./prev-gcc/
-B/n/61/guerby/install-trunk/hppa2.0-unknown-linux-gnu/bin/
-B/n/61/guerby/install-trunk/hppa2.0-unknown-linux-gnu/bin/ -B/n/61/guerby/ins\
tall-trunk/hppa2.0-unknown-linux-gnu/lib/ -isystem
/n/61/guerby/install-trunk/hppa2.0-unknown-linux-gnu/include -isystem
/n/61/guerby/install-trunk/hppa2.0-unknown-linux-gnu/sys-include    -c
-DHAVE_CONFIG_\
H -g -O2  -I. -I../../trunk/libiberty/../include  -W -Wall -Wwrite-strings
-Wc++-compat -Wstrict-prototypes -pedantic  ../../trunk/libiberty/strsignal.c
-o strsignal.o
../../trunk/libiberty/strsignal.c:554:1: error: conflicting types for 'psignal'
/usr/include/signal.h:141:13: note: previous declaration of 'psignal' was here
make[3]: *** [strsignal.o] Error 1
make[3]: Leaving directory `/home/guerby/build/libiberty'
make[2]: *** [all-stage2-libiberty] Error 2
make[2]: Leaving directory `/home/guerby/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/home/guerby/build'
make: *** [bootstrap] Error 2

For reference the given /sr/include/signal.h:

#ifdef __USE_MISC
/* Print a message describing the meaning of the given signal number.  */
extern void psignal (int __sig, __const char *__s);
#endif /* Use misc.  */

And libiberty/strsignal.c

#ifndef HAVE_PSIGNAL

void
psignal (int signo, char *message)
{

=> Probably related to -Wc++-compat


-- 
           Summary: [4.5 Regression] hppa-linux
                    trunk/libiberty/strsignal.c:554:1: error: conflicting
                    types for 'psignal'
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: laurent at guerby dot net
 GCC build triplet: hppa-linux
  GCC host triplet: hppa-linux
GCC target triplet: hppa-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40610


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug bootstrap/40610] [4.5 Regression] hppa-linux trunk/libiberty/strsignal.c:554:1: error: conflicting types for 'psignal'
  2009-07-01 18:08 [Bug bootstrap/40610] New: [4.5 Regression] hppa-linux trunk/libiberty/strsignal.c:554:1: error: conflicting types for 'psignal' laurent at guerby dot net
@ 2009-07-01 18:09 ` bonzini at gnu dot org
  0 siblings, 0 replies; 2+ messages in thread
From: bonzini at gnu dot org @ 2009-07-01 18:09 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from bonzini at gnu dot org  2009-07-01 18:08 -------


*** This bug has been marked as a duplicate of 40607 ***


-- 

bonzini at gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40610


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-07-01 18:09 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-07-01 18:08 [Bug bootstrap/40610] New: [4.5 Regression] hppa-linux trunk/libiberty/strsignal.c:554:1: error: conflicting types for 'psignal' laurent at guerby dot net
2009-07-01 18:09 ` [Bug bootstrap/40610] " bonzini at gnu dot org

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).