This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: problem compiling glibc 2.26 with gcc 7.1



On 02/08/2017 15:58, Waldemar Brodkorb wrote:
> Hi,
> Adhemerval Zanella wrote,
> 
>>
>>
>> On 02/08/2017 15:45, Waldemar Brodkorb wrote:
>>> Hi,
>>>
>>> I try to cross-compile latest glibc release 2.26 with binutils 2.28
>>> and gcc 7.1 to aarch64, but the compilation fails with this error:
>>> ./md-unwind-support.h: In function 'aarch64_fallback_frame_state':
>>> ./md-unwind-support.h:58:21: error: field 'uc' has incomplete type
>>>      struct ucontext uc;
>>>                      ^~
>>>
>>> The full log is here:
>>> https://debug.openadk.org/glibc/make.log
>>>
>>> It fails in the final gcc compilation step.
>>>
>>> Anyone have a gcc patch ready?
>>> Or do I make a mistake? Glibc 2.25 worked fine for me with the
>>> same gcc and binutils versions.
>>> I see similar issues with other architectures.
>>>
>>> best regards
>>>  Waldemar
>>>
>>
>> Check wiki release notes [1] and NEWS about this change:
>>
>> * The ucontext_t type no longer has the name struct ucontext.  This changes
>>   the C++ name mangling for interfaces involving this type.
>>
>> You should use ucontext_t instead of struct ucontext.
>>
>> [1] https://sourceware.org/glibc/wiki/Release/2.26
> 
> I have seen the change. But does it mean gcc 7.1 (latest gcc
> release) can not be used with latest glibc release?
> 

Unfortunately it will require a backport as Khem Raj pointed out. 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]