Upstream blacklisted boost-1.52.0 due to broken thread_group::join_all() and automagically disables functionality when that version is found. To avoid users getting nonfunctional gnuradio, I added a dependency !<=dev-libs/boost-1.52.0-r6:0/1.52 If a fix is applied to 1.52.0 we can override cmake detection with -DENABLE_BAD_BOOST=True
I confirm, I have just...
The dependency blocks all versions less than or equal to 1.52.0 (ie, there's no version of boost available that portage thinks will work with gnuradio-3.6.4). Shouldn't it just blacklist 1.52.0 and allow lower versions?
Old versions of boost are allowed: # emerge -pv boost:0/0 gnuradio These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] dev-util/boost-build-1.49.0 [1.52.0-r1] USE="-examples -python (-test%)" 0 kB [ebuild UD ] dev-libs/boost-1.49.0-r2:0/0 [1.52.0-r6:0/1.52] USE="python -debug -doc -icu -mpi -static-libs -tools (-nls%*) (-threads%*)" PYTHON_TARGETS="(-python2_5%) (-python2_6%) (-python2_7%*) (-python3_1%) (-python3_2%*) (-python3_3%)" 0 kB [ebuild N ~] net-wireless/gnuradio-3.6.4 USE="alsa qt4 sdl wxwidgets -doc -examples -fcd -filter -grc -jack -oss -performance-counters -portaudio -uhd -utils -wavelet" 2,854 kB Total: 3 packages (2 downgrades, 1 new), Size of downloads: 2,854 kB
Ah, you're right, sorry. I missed the slotting on the dependency. Unfortunately I have other packages dependent upon a more recent boost (mongodb)...
gnuradio users will have to use boost-1.53