checking for Fortran 77 libraries of fort... checking for dummy main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... configure: error: in `/var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0': configure: error: cannot compile a simple Fortran program See `config.log' for more details ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-20190815-154659 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * java-config: The following VMs are available for generation-2: emerge -qpvO sci-libs/med [ebuild N ] sci-libs/med-4.0.0 USE="-mpi"
Created attachment 587326 [details] emerge-info.txt
Created attachment 587328 [details] emerge-history.txt
Created attachment 587330 [details] environment
Created attachment 587332 [details] etc.portage.tbz2
Created attachment 587334 [details] logs.tbz2
Created attachment 587336 [details] sci-libs:med-4.0.0:20190818-074717.log
Created attachment 587338 [details] temp.tbz2
I thought the output of configure looked funny :) So configure looks for a fortran compiler. And by the look of it you don't have one installed. And then it found a program called "fort" (thinking it is the fortran front end for llvm, possibly previously known as flang). But it is not a fortran compiler configure:8073: checking for fort configure:8089: found /usr/bin/fort configure:8100: result: fort configure:8126: checking for Fortran 77 compiler version configure:8135: fort --version >&5 /usr/bin/fort: unknown option '--version'. FORT (Framework for Ocaml Regression Testing) Copyright (c) 2001 Patrick Doane. If we don't want fortran in med it looks to me like we need to find a way to disable it, so funny stuff that may look like a fortran compiler is not found. That and the prospect that in the future we may have a name clash when "fort" from llvm sees an official release.
In med's configure options --enable-fortran Compile the MED FORTRAN library. Default: enabled and --with-f90=<compiler> Use <compiler> for F90 compiler (default:no) So there is a possibility to add a fortran flag to the ebuild with corresponding settings or disabling fortran altogether.
med-4.0.0 is gone, the bug is obsolete and med-4.1.0 doesn't have the issue. Closing the bug.
