[Bug 246958] net/mpich: Fails to build with current GCC: configure: error: The Fortran compiler gfortran10 will not compile files that call the same routine with arguments of different types.

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Jun 3 13:48:08 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246958

            Bug ID: 246958
           Summary: net/mpich: Fails to build with current GCC: configure:
                    error: The Fortran compiler gfortran10 will not
                    compile files that call the same routine with
                    arguments of different types.
           Product: Ports & Packages
           Version: Latest
          Hardware: powerpc
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: salvadore at freebsd.org
                CC: gerald at FreeBSD.org, linimon at FreeBSD.org,
                    powerpc at FreeBSD.org, tcberner at freebsd.org
            Blocks: 246700
                CC: powerpc at FreeBSD.org

Please see PR #246700 for details, which is about updating the default version
of GCC from 9 to 10.

  checking whether Fortran 77 compiler processes .F files with C
preprocessor... yes
  checking whether gfortran10 allows mismatched arguments... no
  configure: error: The Fortran compiler gfortran10 will not compile files that
call the same routine with arguments of different types.
  ===>  Script "configure" failed unexpectedly.

This error was produced on powerpc64 (see comment 7 in PR #246700).

This issue is probably due to the -fno-common flag set by default. The easy
workaround is adding CFLAGS=-fcommon until the code can be fixed (preferably
upstream) according to https://gcc.gnu.org/gcc-10/porting_to.html#common .


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246700
[Bug 246700] [exp-run] Update GCC_DEFAULT from 9 to 10
-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-ppc mailing list