On 25 Jan 2021, Nathan Sidwell said:
> I think you're right about checking though, not
I'll look at it once I've dealt with this unfortunate "installing
binutils leaves the system linker broken" disaster I've caused. :)
--
NULL && (void)
On 1/25/21 12:50 PM, Nick Alcock wrote:
On 25 Jan 2021, Nathan Sidwell uttered the following:
On 1/22/21 12:19 PM, Nick Alcock wrote:
Searching for sighander_t is unlikely to succeed anywhere.
The attempt to #include is also not working,
and fixing it shows that doing an AC_DEFINE in the bod
On 25 Jan 2021, Nathan Sidwell uttered the following:
> On 1/22/21 12:19 PM, Nick Alcock wrote:
>> Searching for sighander_t is unlikely to succeed anywhere.
>>
>> The attempt to #include is also not working,
>> and fixing it shows that doing an AC_DEFINE in the body of
>> an AC_CHECK_TYPE like t
On 1/22/21 12:19 PM, Nick Alcock wrote:
Searching for sighander_t is unlikely to succeed anywhere.
The attempt to #include is also not working,
and fixing it shows that doing an AC_DEFINE in the body of
an AC_CHECK_TYPE like that is also risky: both fixed.
(The purpose of this check is opaque
On Jan 22 2021, Nick Alcock via Gcc-patches wrote:
> (The purpose of this check is opaque to me: neither libcody
> nor GCC ever includes , and though is
> widely included, it is not directly included by any of the
> headers checking this macro... for now I've fixed things
> to conform to the com
