[Mvapich-discuss] can't build with gfortran 11

Ryan Novosielski novosirj at rutgers.edu
Tue Aug 3 13:17:05 EDT 2021


No problem, and thank you for such a fast response!

Is there someplace I should have looked for this in advance? I didn’t see anything when doing some web searches.

> On Aug 3, 2021, at 1:14 PM, Subramoni, Hari <subramoni.1 at osu.edu> wrote:
> 
> Hi, Ryan.
> 
> Sorry to hear that you're facing this issue. Unfortunately, setting FFLAGS=-fallow-argument-mismatch is still the recommended method to build with GCC versions greater than 10. We hope to resolve this in the future.
> 
> Please let us know if you face any other performance or functionality issues.
> 
> Best,
> Hari.
> 
> -----Original Message-----
> From: Ryan Novosielski <novosirj at rutgers.edu> 
> Sent: Tuesday, August 3, 2021 1:10 PM
> To: mvapich-discuss at lists.osu.edu
> Cc: Subramoni, Hari <subramoni.1 at osu.edu>
> Subject: Re: [Mvapich-discuss] can't build with gfortran 11
> 
> Sorry to dig up an old thread here, but I still have this problem with both GCC 10.3 and 11.2 and MVAPICH2 2.3.6:
> 
> checking whether gfortran allows mismatched arguments... no
> configure: error: The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types.
> 
> This is during the configure stage. My configure line for both is:
> 
> ../mvapich2-2.3.6/configure --with-pmi=pmi2 --with-pm=slurm
> 
> I’ve seen suggestions up-thread for FFLAGS changes, but is this supposed to be this way still, or am I missing something?
> 
> --
> #BlackLivesMatter
> ____
> || \\UTGERS,  	 |---------------------------*O*---------------------------
> ||_// the State	 |         Ryan Novosielski - novosirj at rutgers.edu
> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
> ||  \\    of NJ	 | Office of Advanced Research Computing - MSB C630, Newark
>     `'
> 
>> On Feb 17, 2021, at 9:08 PM, Subramoni, Hari via Mvapich-discuss <mvapich-discuss at lists.osu.edu> wrote:
>> 
>> Hi, All.
>> 
>> This issue has been resolved through discussions with the user off the list. The fixes will be available with the next version of MVAPICH2 slated to be released in a couple of weeks.
>> 
>> Best,
>> Hari.
>> 
>> -----Original Message-----
>> From: Mvapich-discuss <mvapich-discuss-bounces at lists.osu.edu> On 
>> Behalf Of Honggang LI via Mvapich-discuss
>> Sent: Tuesday, February 2, 2021 11:08 PM
>> To: mvapich-discuss at lists.osu.edu
>> Subject: [Mvapich-discuss] can't build with gfortran 11
>> 
>> hi,
>> 
>> ~]$ gfortran -v
>> Using built-in specs.
>> COLLECT_GCC=gfortran
>> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/11/lto-wrappe
>> r
>> OFFLOAD_TARGET_NAMES=nvptx-none
>> OFFLOAD_TARGET_DEFAULT=1
>> Target: x86_64-redhat-linux
>> Configured with: ../configure --enable-bootstrap 
>> --enable-languages=c,c++,fortran,lto --prefix=/usr 
>> --mandir=/usr/share/man --infodir=/usr/share/info 
>> --with-bugurl=https://urldefense.com/v3/__http://bugzilla.redhat.com/b
>> ugzilla__;!!KGKeukY!mWknHBPQXt1IkaXaKpT7kHQGjB8iXUi3aRkskhUlj9xlGP3ckZ
>> ucCCAf-Pj0kkwFOsh1p7zIQg$  --enable-shared --enable-threads=posix 
>> --enable-checking=release --enable-multilib --with-system-zlib 
>> --enable-__cxa_atexit --disable-libunwind-exceptions 
>> --enable-gnu-unique-object --enable-linker-build-id 
>> --with-gcc-major-version-only --with-linker-hash-style=gnu 
>> --enable-plugin --enable-initfini-array --without-isl 
>> --enable-offload-targets=nvptx-none --without-cuda-driver 
>> --enable-gnu-indirect-function --enable-cet --with-tune=generic 
>> --with-arch_64=x86-64-v2 --with-arch_32=x86-64 
>> --build=x86_64-redhat-linux Thread model: posix Supported LTO 
>> compression algorithms: zlib zstd gcc version 11.0.0 20210123 (Red Hat 
>> 11.0.0-0) (GCC)
>> 
>> 
>> $ tar -zxf mvapich2-2.3.5.tar.gz
>> $ cd mvapich2-2.3.5/
>> $ ./configure
>> 
>> checking for include directory flag for Fortran... -I checking for 
>> Fortran 77 flag for library directories... -L checking whether Fortran 
>> 77 compiler processes .F files with C preprocessor... yes checking 
>> whether gfortran allows mismatched arguments... no
>> configure: error: The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types.
>> error: Bad exit status from /var/tmp/rpm-tmp.WX3UGf (%build)
>> 
>> _______________________________________________
>> Mvapich-discuss mailing list
>> Mvapich-discuss at lists.osu.edu
>> https://lists.osu.edu/mailman/listinfo/mvapich-discuss
>> _______________________________________________
>> Mvapich-discuss mailing list
>> Mvapich-discuss at lists.osu.edu
>> https://lists.osu.edu/mailman/listinfo/mvapich-discuss
> 



More information about the Mvapich-discuss mailing list