Bug 14215

Summary: SIGILL when building python3-setuptools-native
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Tim Blechmann <tim>
Component: Scripts and ToolsAssignee: Steve Sakoman <steve>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: frieder.schrempf, mans, randy.macleod, richard.purdie, ross.burton
Version: 3.1.7   
Target Milestone: 3.3 M3   
Hardware: x86   
OS: x86_64   
URL: https://sourceware.org/bugzilla/show_bug.cgi?id=26534
Whiteboard: backports of uninative upgrade as needed.
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Done (doc changes complete)

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