Re: build failure -> declaration of strsignal?

[Ralf Gütlein <ralf dot guetlein at aranea dot de>]

Problem solved. Was my fault. I changed the definition in strsignal.c
to meet the requirements of an older cygwin installation. I forgot
to restore when switching to a newer installation.
I apologize any inconvenience my post may have caused.

Regards,
Ralf

----- Original Message -----
From: Ralf Gütlein <ralf.guetlein@aranea.de>
To: gnuh8 <gnuh8@pcserv.demon.co.uk>; gcc <gcc@gcc.gnu.org>
Sent: Wednesday, August 16, 2000 10:05 AM
Subject: build failure -> declaration of strsignal?


> My attempts to build a cross compiler (host: cygwin, target: h8300,
> build: gygwin) stumble over an inconsistency between the declaration
> of strsignal in the cygwin headers (latest binaries) and its definition
> in gcc/libiberty/strsignal.c (latest snapshot)
>
> in string.h (cygwin):
>
> char    *_EXFUN(strsignal, (int __signo));
>
> in strsignal.c (libiberty):
>
> const char *
> strsignal (signo)
>   int signo;
>
> The compiler moans about the different return type (const vs. non-const).
> What version is the right one?
>
> Regards,
> Ralf
>

           .....
           ô ô )
-----oOOo--(_)---oOOo------

Ralf Guetlein
Biotest Medizintechnik GmbH
Industriestrasse 19
D-63755 Alzenau
Germany
---------------------------
Tel. +49 6023 9487-42
Fax. +49 6023 9487-33
ralf.guetlein@biotest-mt.de
---------------------------