X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Date:	Fri, 4 Aug 2006 13:13:50 -0400
Message-Id:	<200608041713.k74HDot3026516@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	Gordon DOT Schumacher AT seagate DOT com
CC:	djgpp AT delorie DOT com
In-reply-to:
	<OF3B21CC3C DOT E78E8EDD-ON872571C0 DOT 005B7E4A-872571C0 DOT 005D7244 AT seagate DOT com>
	(Gordon DOT Schumacher AT seagate DOT com)
Subject:	Re: Additional patch for gcc4.10 for cross-compilation
References:	<OF3B21CC3C DOT E78E8EDD-ON872571C0 DOT 005B7E4A-872571C0 DOT 005D7244 AT seagate DOT com>
Errors-To:	nobody AT delorie DOT com

> 2) It's being built not because DJGPP is lacking it, but because the
> host OS (CygWin) is.  That confused me for a while too...

Then it's a gcc/cygwin issue.

>    In the GCC source strsignal.c, I see:
>       psignal (unsigned signo, char *message)
>    In DJGPP's signal.h, there's:
>       void    psignal(int _sig, const char *_msg);
>    In the signal.h on SuSE 10 Linux,
>       extern void psignal (int __sig, __const char *__s);
> 
> So DJGPP and Linux agree, and the GCC source has a different
> prototype.  I couldn't find any other compilers/OSes on a quick
> scan of my systems that implement psignal.

Ah, but psignal shouldn't be compiled unless there *isn't* one, so it
can't be "wrong".  At least, it shouldn't be able to conflict with the
system one.

- Raw text -