Summary: | net-wireless/gnuradio-3.7.10.1[grc] fails to detect dev-python/numpy-1.10.4, configuration checked fails (sometimes) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Bolshakov <anton.bugs> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | xmw, zerochaos |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Anton Bolshakov
2016-10-29 08:37:20 UTC
Created attachment 451818 [details]
build.log
somehow, it fails to detect dev-python/numpy-1.10.4 I have upgraded it to the version ~1.11.2-r1 and gnuradio compiled properly: -- Python checking for numpy -- Python checking for numpy - found So the current stable version (1.10.4) could be buggy. odd, I've only hit this problem on x86, and only once. Since I build two profiles for each arch, that means this has a roughly 25% chance of failing (of course I replicated ~4 times in a row and then it worked... ugh) Open to suggestions, likely suggestion is upstream bug though. Anyone have a better explanation though? Science, any ideas why the stable version of numpy may not be detected reliably? is this a gnuradio bug or something known and numpy related? A possible reason (seen in the wild more than once) is this: numpy depends on sci-libs/lapack-reference (also cblas-reference and blas-reference). [Much later] after numpy is installed, gcc is updated, together with fortran, providing the system with libfortran.so.4* libraries. Once old version of gcc is deinstalled/cleaned, portage apparently does not correctly track references to the now missing library libfortran.so.3* (albeit it does excellent job doing that for other libraries for like a decade I believe). That situation can be easily diagnosed with the following commands:
$ python
> import numpy
if you got a stacktrace, go recompiling numpy and/or its dependencies individually (the stacktrace will suggest which ones to blame) with emerge -av1; once the import works, remerge gnuradio and you will get the desired bin/gnuradio-companion (if numpy was the only problem, yet at the moment gnuradio stays to be a very fragile build dependecies wise).
this doesn't seem to have been replicated in a while, so I suspect it's been solved through some deep magic. |