On Wed, Nov 30, 2016 at 10:45 PM, Orion Poplawski <orion(a)cora.nwra.com> wrote:
On 11/30/2016 04:20 PM, Richard W.M. Jones wrote:
>
> On Wed, Nov 30, 2016 at 10:08:55PM +0000, Richard W.M. Jones wrote:
>>
>> On Wed, Nov 30, 2016 at 02:07:13PM -0700, Jerry James wrote:
>>>
>>> I'm trying to build python-cvxopt, but gcc is failing on aarch64 with
>>> a bus error:
>>>
>>>
http://koji.fedoraproject.org/koji/taskinfo?taskID=16684863
>>
>>
>> As a data point, the build succeeds on F25/aarch64 with:
>>
>> glibc-2.24-3.fc25.aarch64
>> gcc-6.2.1-2.fc25.aarch64
>>
>> I'll spin up a Rawhide VM later to see if I can reproduce this with
>> the suspect glibc etc (don't want to risk upgrading glibc on my main
>> machine :-)
>
>
> On Rawhide (updated partially from F25), the compile works OK with:
>
> glibc-2.24-3.fc25.aarch64
> gcc-6.2.1-2.fc26.aarch64
>
> and it still *works* if I upgrade glibc to:
>
> glibc-2.24.90-19.fc26.aarch64
>
> (leaving all other non-glibc-related packages unchanged).
>
> But it *fails* in exactly the way you describe if I upgrade glibc to:
>
> glibc-2.24.90-20.fc26.aarch64
>
> So it looks fairly conclusively like it's something to do with the
> latest glibc, and you need to be looking at the differences between
> the -19 and -20 packages.
Thanks. I've untaged it.
Seems like it is not actually untagged. My kernel build failed again
today and it is still using -20.
Justin