Summary: | sci-libs/arpack-3.5.0 fails with gcc-10 - Error: Rank mismatch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michelangelo Scopelliti <kernelpanic> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | zeekec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 706426 | ||
Attachments: |
build log with MAKEOPTS="-j1"
build log emerge info 2nd build log |
Description
Michelangelo Scopelliti
2020-05-09 13:33:37 UTC
Created attachment 637040 [details]
build log with MAKEOPTS="-j1"
GCC-10 includes some improvements in the Fortran compiler. To compile something that compiled under the previous compiler the FFLAGS environment variable can be set. FFLAGS="-std=legacy" emerge -1 arpack (In reply to Ross Hayward from comment #2) > GCC-10 includes some improvements in the Fortran compiler. To compile > something that compiled under the previous compiler the FFLAGS environment > variable can be set. > > FFLAGS="-std=legacy" emerge -1 arpack Yes, -std=legacy implies -fallow-argument-mismatch. But -std=legacy suppresses other warnings about obsolete extensions, becoming too intrusive. Just my 2c. Used the suggested f flags adjustment,then scipy-python2-1.2.3 fell over with a similar fault follow on comment 4 arpack still falls over with the package.use statement FFlags="-std=legacy". though it did build previously as an emerge statement. but the following build fell over in a similar way. Created attachment 642534 [details]
build log
Created attachment 642536 [details]
emerge info
Created attachment 642566 [details]
2nd build log
(In reply to Geoff Madden from comment #4) > Used the suggested f flags adjustment,then scipy-python2-1.2.3 fell over > with a similar fault Yes, of course. See bug #721860. (In reply to Geoff Madden from comment #5) > follow on comment 4 arpack still falls over with the package.use statement > FFlags="-std=legacy". > though it did build previously as an emerge statement. but the following > build fell over in a similar way. It fails because FFLAGS is not in IUSE. If you want to change FFLAGS (or other env variables), you have to use package.env (see https://wiki.gentoo.org/wiki//etc/portage/package.env) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=56bb49e97ee1dc6ee5a257bed3e45c2154b87dab commit 56bb49e97ee1dc6ee5a257bed3e45c2154b87dab Author: Alexey Shvetsov <alexxy@gentoo.org> AuthorDate: 2020-06-07 21:11:18 +0000 Commit: Alexey Shvetsov <alexxy@gentoo.org> CommitDate: 2020-06-07 21:11:30 +0000 sci-libs/arpack: Fix build with gcc10 Closes: https://bugs.gentoo.org/721858 Package-Manager: Portage-2.3.100, Repoman-2.3.22 Signed-off-by: Alexey Shvetsov <alexxy@gentoo.org> sci-libs/arpack/arpack-3.4.0.ebuild | 13 +++++++------ sci-libs/arpack/arpack-3.5.0.ebuild | 11 ++++++----- sci-libs/arpack/arpack-9999.ebuild | 10 +++++----- 3 files changed, 18 insertions(+), 16 deletions(-) |