Bug 14215 - SIGILL when building python3-setuptools-native
Summary: SIGILL when building python3-setuptools-native
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 3.1.7
Hardware: x86 x86_64
: Medium+ normal
Target Milestone: 3.3 M3
Assignee: Steve Sakoman
QA Contact:
URL: https://sourceware.org/bugzilla/show_...
Whiteboard: backports of uninative upgrade as nee...
Depends on:
Blocks:
 
Reported: 2021-02-03 01:49 UTC by Tim Blechmann
Modified: 2021-02-25 14:17 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Blechmann 2021-02-03 01:49:50 UTC 
updating to dunfell i've experienced SIGILL crashes when building python3-setuptools-native.

it turned out that an FMA4 instruction from libm was executed because of a bug in the runtime detection in glibc-2.32 which apparently is present in the uninative toolchain v2.9: https://sourceware.org/bugzilla/show_bug.cgi?id=26534

as a workaround i've disabled uninative for my configuration, but i wonder if it's possibly to backport the glibc fix to the uninative toolchain
Comment 1 Richard Purdie 2021-02-04 14:53:05 UTC 
Looks like we should update to use the latest 2.32 branch of glibc and build a new uninative release...
Comment 2 Frieder Schrempf 2021-02-09 14:01:10 UTC 
We also see this issue on our dunfell builds. Would be great if someone could update uninative and add a fix to the dunfell branch.
Comment 3 Måns Andersson 2021-02-17 08:59:57 UTC 
Same thing here, reproducible on our dunfull build. More details on our setup, and the error presented on our end, is noted in my Stack Overflow post for the same at https://stackoverflow.com/q/65178174/414817