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 quite baffled.
Rebuilding sci-libs/lapack didn't help and neither did ~amd64 keywording it. The error remains the same, which would make sense as there's not really a new version of sci-libs/lapack. Cheers, Victor On 07/05/2020 15:04, Peter Humphrey wrote: > 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 >> issue. However, it fails with a surprisingly unhelpful message during a >> call to gfortran. Or maybe I'm unable to spot the proper error message. > > Isn't this the cause? > > x86_64-pc-linux-gnu-gcc: /var/tmp/portage/sci-libs/scipy-1.1.0/temp/tmpeyMzsQ/ > source.c > /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: > > /var/tmp/portage/sci-libs/scipy-1.1.0/temp/ccGtNhqg.o: in function `main': > source.c:(.text.startup+0x8c): undefined reference to `cblas_ddot' > collect2: error: ld returned 1 exit status >
signature.asc
Description: OpenPGP digital signature
