X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
In-Reply-To: <200608040115.k741FCJD009680@envy.delorie.com>
Subject: Re: Additional patch for gcc4.10 for cross-compilation
To: dj AT delorie DOT com
Cc: djgpp AT delorie DOT com
X-Mailer: Lotus Notes Release 6.5.4  CCH5 September 12, 2005
Message-ID: <OF3B21CC3C.E78E8EDD-ON872571C0.005B7E4A-872571C0.005D7244@seagate.com>
From: Gordon DOT Schumacher AT seagate DOT com
Date: Fri, 4 Aug 2006 11:02:12 -0600
X-MIMETrack: Serialize by Router on SV-GW1/Seagate Internet(Release 7.0.1 HF29|March 07, 2006) at
 08/04/2006 10:00:44 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Proofpoint-FWRule: outbound2
X-Proofpoint-Virus-Version: vendor=fsecure engine=4.64.4171:2.3.9,1.2.33,4.0.164 definitions=2006-08-04_05:2006-08-02,2006-08-04,2006-08-04 signatures=0
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

DJ Delorie <dj AT delorie DOT com> wrote on 08/03/2006 07:15:12 PM:

# Thanks, but consider (1) gcc patches should be posted to the gcc
# patches list (gcc-patches AT gcc DOT gnu DOT org), and (2) are you sure strsignal
# is wrong?  DJGPP has strsignal, so the real question is, why is
# psignal being built at all?

1) You're right, I should post it there as well - but I sent it here
   because it's an impediment to building a DJGPP cross-compiler.  I
   had (perhaps incorrectly!) assumed that the "s2" package was only
   things that are specific to DJGPP, and thus don't necessarily end
   up in the "mainline" GCC code.

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

So it looks wrong to me :)