| Summary: | dev-python/pynacl-1.0.1 : make[3]: *** [Makefile:2113: crypto_auth/libsodium_la-crypto_auth.lo] Error 132 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Tobias Klausmann (RETIRED) <klausman> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | dolsen, python, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dev-python:pynacl-1.0.1:20161206-033311.log
emerge-history.txt environment etc.portage.tbz2 |
||
|
Description
Toralf Förster
2016-12-06 08:05:59 UTC
Created attachment 455220 [details]
dev-python:pynacl-1.0.1:20161206-033311.log
Created attachment 455222 [details]
emerge-history.txt
Created attachment 455224 [details]
environment
Created attachment 455226 [details]
etc.portage.tbz2
This is very odd. "Illegal instruction" aka SIGILL is triggered when a binary is trying to execute an instruction the processor does not know (e.g. SSSE instructions on CPUs that don't have that instruction set). Note that it is the _binary_ that's at fault, not the data it is handling. In this case the binary that is running is gcc, so I am fairly sure it's not pynacl's fault (and I can't reproduce it). So either the gcc used has a bug, or something running in parallel was spamming "pkill -ILL gcc" during a test suite or some such. It has happened before and is very hard to track down. Given comment #5 and no reports of this happening in later releases, I'm closing this as obsolete. |