When libiberty defines psignal, it doesn't use the canonical signature.
This came up as a problem in a configuration where libiberty wants to
define psignal itself, but the build environment's declares
it too.
This was a --with-newlib configuration using the newlib trunk, where newlib
does defi
On Tue, Oct 18, 2011 at 9:49 AM, Roland McGrath wrote:
> When libiberty defines psignal, it doesn't use the canonical signature.
> This came up as a problem in a configuration where libiberty wants to
> define psignal itself, but the build environment's declares
> it too.
>
> This was a --with-ne
On Tue, Oct 18, 2011 at 9:50 AM, Andrew Pinski wrote:
> libiberty is no longer compiled for the target so this should never
> happen really.
I see. I was indeed using an older source base, and just noticed that all
the offending configure logic was still the same. Perhaps all the
--with-newlib
On Tue, Oct 18, 2011 at 9:49 AM, Roland McGrath wrote:
>
> libiberty/
> 2011-10-18 Roland McGrath
>
> * strsignal.c (psignal): Use const second in parameter type.
> * functions.texi: Updated.
This is OK.
Thanks.
Ian
On Tue, Oct 18, 2011 at 10:18 AM, Ian Lance Taylor wrote:
> On Tue, Oct 18, 2011 at 9:49 AM, Roland McGrath wrote:
>>
>> libiberty/
>> 2011-10-18 Roland McGrath
>>
>> * strsignal.c (psignal): Use const second in parameter type.
>> * functions.texi: Updated.
>
> This is OK.
Thank
