I can't answer why it works in this particular case, but the generic
answer is that using a -j greater than one risks the launching of a job
that requires some output of another job not yet completed, or even
run. I suspect if you hunt through the build log, you will find the
missing
In case anyone encounters the same issue, the problem was solved by
single threaded build using MAKEOPTS="-j1". No other config changes.
Why this works but not otherwise remains a mystery. I also had the same
problem earlier today with dev-python/matplotlib-2.2.2-r1 except the
linker was
Ah, thanks for pointing this out! It appears I'm blind ...
It's rather surprising though, as sci-libs/lapack was neither upgraded
nor rebuilt. Since sci-libs/scipy wasn't upgraded either it ought to
link just fine as it had previously been built against the same version
of sci-libs/lapack. I'm
On Thursday, 7 May 2020 14:31:41 BST Victor Ivanov wrote:
> Hi all,
>
> For some reason SciPy fails to compile after today's Python 3.6 ->
> Python 3.7 global update. It was the only package that failed out of all.
>
> Normally build.log (attached) is helpful enough to get me to resolve the
>
4 matches
Mail list logo
