bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compiler error on macOS Siera with address@hidden


From: Denis Davydov
Subject: Re: compiler error on macOS Siera with address@hidden
Date: Fri, 23 Sep 2016 20:19:17 +0200

Hi Eric,

Thanks for the swift reply.

> On 23 Sep 2016, at 19:51, Eric Blake <address@hidden> wrote:
> 
> [adding gnulib]
> 
> On 09/23/2016 12:38 PM, Denis Davydov wrote:
>> Dear developers,
>> 
>> m4 fails to compile on macOS Sierra with GCC:
>> 
>> ./sched.h:42:8: error: redefinition of 'struct sched_param'
>> struct sched_param
>>        ^~~~~~~~~~~
>> In file included from ./sched.h:27:0,
>>                 from ./spawn.h:37,
>>                 from execute.c:47:
>> /usr/include/sched.h:35:8: note: originally defined here
>> struct sched_param { int sched_priority;  char 
>> __opaque[__SCHED_PARAM_SIZE__]; };
>>        ^~~~~~~~~~~
> 
> Thanks for the report.
> 
> Can you look in config.log, and see why configure seems to think that
> HAVE_STRUCT_SCHED_PARAM was set to 0 on your platform (since it is

it is indeed set to 0. Searching for HAVE_STRUCT_SCHED_PARAM in config.log
reveals a single line only, so i don’t know where it is set and why.
Config log is attached.

> obvious from the error message that your platform DOES have struct
> sched_param after all)?  Is this a case of you doing incremental
> compilation, where the cache variables are from one run on an earlier
> version of macOS, and not updated for the change in headers when you
> moved to Sierra?  If so, does a fresh build change things?  Can you work

no, it’s not incremental build. It is a build within Spack package manager with 
a fresh
build folder, see https://github.com/LLNL/spack/issues/1838

> around the issue by setting appropriate cache variables during the
> configure run?

I tried adding

HAVE_STRUCT_SCHED_PARAM=1

to ./configure but it does not change anything. How do I do that?

Regards,
Denis.

Attachment: config.log.zip
Description: Zip archive


reply via email to

[Prev in Thread] Current Thread [Next in Thread]