| 1 |
Ah, thanks for pointing this out! It appears I'm blind ... |
| 2 |
|
| 3 |
It's rather surprising though, as sci-libs/lapack was neither upgraded |
| 4 |
nor rebuilt. Since sci-libs/scipy wasn't upgraded either it ought to |
| 5 |
link just fine as it had previously been built against the same version |
| 6 |
of sci-libs/lapack. I'm quite baffled. |
| 7 |
|
| 8 |
Rebuilding sci-libs/lapack didn't help and neither did ~amd64 keywording |
| 9 |
it. The error remains the same, which would make sense as there's not |
| 10 |
really a new version of sci-libs/lapack. |
| 11 |
|
| 12 |
Cheers, |
| 13 |
Victor |
| 14 |
|
| 15 |
On 07/05/2020 15:04, Peter Humphrey wrote: |
| 16 |
> On Thursday, 7 May 2020 14:31:41 BST Victor Ivanov wrote: |
| 17 |
>> Hi all, |
| 18 |
>> |
| 19 |
>> For some reason SciPy fails to compile after today's Python 3.6 -> |
| 20 |
>> Python 3.7 global update. It was the only package that failed out of all. |
| 21 |
>> |
| 22 |
>> Normally build.log (attached) is helpful enough to get me to resolve the |
| 23 |
>> issue. However, it fails with a surprisingly unhelpful message during a |
| 24 |
>> call to gfortran. Or maybe I'm unable to spot the proper error message. |
| 25 |
> |
| 26 |
> Isn't this the cause? |
| 27 |
> |
| 28 |
> x86_64-pc-linux-gnu-gcc: /var/tmp/portage/sci-libs/scipy-1.1.0/temp/tmpeyMzsQ/ |
| 29 |
> source.c |
| 30 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
| 31 |
> /var/tmp/portage/sci-libs/scipy-1.1.0/temp/ccGtNhqg.o: in function `main': |
| 32 |
> source.c:(.text.startup+0x8c): undefined reference to `cblas_ddot' |
| 33 |
> collect2: error: ld returned 1 exit status |
| 34 |
> |
Archives