| 1 |
In case anyone encounters the same issue, the problem was solved by |
| 2 |
single threaded build using MAKEOPTS="-j1". No other config changes. |
| 3 |
|
| 4 |
Why this works but not otherwise remains a mystery. I also had the same |
| 5 |
problem earlier today with dev-python/matplotlib-2.2.2-r1 except the |
| 6 |
linker was complaining about an incompatible version of libc. Again |
| 7 |
solved by -j1 and no other config modifications. |
| 8 |
|
| 9 |
I have sometimes experienced this with some packages but exceptionally |
| 10 |
rarely which is why it's not on usually on my "to try" list. If anyone |
| 11 |
has any insights as to why this might be happening (in general), I would |
| 12 |
be grateful and happy to expand my knowledge :) |
| 13 |
|
| 14 |
Cheers, |
| 15 |
Victor |
| 16 |
|
| 17 |
On 07/05/2020 15:53, Victor Ivanov wrote: |
| 18 |
> Ah, thanks for pointing this out! It appears I'm blind ... |
| 19 |
> |
| 20 |
> It's rather surprising though, as sci-libs/lapack was neither upgraded |
| 21 |
> nor rebuilt. Since sci-libs/scipy wasn't upgraded either it ought to |
| 22 |
> link just fine as it had previously been built against the same version |
| 23 |
> of sci-libs/lapack. I'm quite baffled. |
| 24 |
> |
| 25 |
> Rebuilding sci-libs/lapack didn't help and neither did ~amd64 keywording |
| 26 |
> it. The error remains the same, which would make sense as there's not |
| 27 |
> really a new version of sci-libs/lapack. |
| 28 |
> |
| 29 |
> Cheers, |
| 30 |
> Victor |
| 31 |
> |
| 32 |
> On 07/05/2020 15:04, Peter Humphrey wrote: |
| 33 |
>> On Thursday, 7 May 2020 14:31:41 BST Victor Ivanov wrote: |
| 34 |
>>> Hi all, |
| 35 |
>>> |
| 36 |
>>> For some reason SciPy fails to compile after today's Python 3.6 -> |
| 37 |
>>> Python 3.7 global update. It was the only package that failed out of all. |
| 38 |
>>> |
| 39 |
>>> Normally build.log (attached) is helpful enough to get me to resolve the |
| 40 |
>>> issue. However, it fails with a surprisingly unhelpful message during a |
| 41 |
>>> call to gfortran. Or maybe I'm unable to spot the proper error message. |
| 42 |
>> |
| 43 |
>> Isn't this the cause? |
| 44 |
>> |
| 45 |
>> x86_64-pc-linux-gnu-gcc: /var/tmp/portage/sci-libs/scipy-1.1.0/temp/tmpeyMzsQ/ |
| 46 |
>> source.c |
| 47 |
>> /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
| 48 |
>> /var/tmp/portage/sci-libs/scipy-1.1.0/temp/ccGtNhqg.o: in function `main': |
| 49 |
>> source.c:(.text.startup+0x8c): undefined reference to `cblas_ddot' |
| 50 |
>> collect2: error: ld returned 1 exit status |
| 51 |
>> |
| 52 |
> |
Archives