Re: spec file with aarch64 specific Fortran build flags

* Tulio Magno Quites Machado Filho: > Have you already reported this issue upstream? To close the loop here, Sébastien has reported this as: -fstack-protector-strong FLAG causes compiler error on aarch64 I find the upstream decision not

Re: spec file with aarch64 specific Fortran build flags

Sébastien Le Roux writes: > Dear all, > in the past weeks the updates of GCC for both Fedora and Debian have > introduce few identical Fortran modifications: > > fortran/108961 > fortran/109684 > fortran/110825 > > As a result my I cannot build the RPM package (nor th

spec file with aarch64 specific Fortran build flags

Dear all, in the past weeks the updates of GCC for both Fedora and Debian have introduce few identical Fortran modifications: fortran/108961 fortran/109684 fortran/110825 As a result my I cannot build the RPM package (nor the Debian package) for my program 'atomes' anymore, because the ARM

Re: hdf5 fortran build failure with gcc 12

Dave Love wrote on 2022/02/01 19:20: Orion Poplawski writes: On 1/29/22 19:40, Mamoru TASAKA wrote: Looks like "minusone" variable looking like constant value defined in fortran/test/tH5A_1_8.F90 needs PARAMETER attribute. Tried this diff: ``` diff --git a/hdf5.spec b/hdf5.

Re: hdf5 fortran build failure with gcc 12

Orion Poplawski writes: > On 1/29/22 19:40, Mamoru TASAKA wrote: >> Looks like "minusone" variable looking like constant value defined >> in >> fortran/test/tH5A_1_8.F90 needs PARAMETER attribute. Tried this diff: >> ``` >> diff --git a/hdf5.spec b

Re: hdf5 fortran build failure with gcc 12

On 1/29/22 19:40, Mamoru TASAKA wrote: Orion Poplawski wrote on 2022/01/30 3:48: hdf5 is starting to fail to build with gcc 12 in rawhide with: make[2]: Entering directory '/builddir/build/BUILD/hdf5-1.12.1/build/fortran/test' /bin/sh ../../libtool  --tag=FC   --mode=link gfortran -std=f2008

Re: hdf5 fortran build failure with gcc 12

Orion Poplawski wrote on 2022/01/30 3:48: hdf5 is starting to fail to build with gcc 12 in rawhide with: make[2]: Entering directory '/builddir/build/BUILD/hdf5-1.12.1/build/fortran/test' /bin/sh ../../libtool  --tag=FC   --mode=link gfortran -std=f2008 -Waliasing -Wall -Wcharacter-truncation

hdf5 fortran build failure with gcc 12

hdf5 is starting to fail to build with gcc 12 in rawhide with: make[2]: Entering directory '/builddir/build/BUILD/hdf5-1.12.1/build/fortran/test' /bin/sh ../../libtool --tag=FC --mode=link gfortran -std=f2008 -Waliasing -Wall -Wcharacter-truncation -Wextra -Wimplicit-interface -Wsurprising

Re: Review swaps and advice for python / fortran / octave modules

On 11/6/20 2:09 AM, Mattia Verga via devel wrote: Hello all, I have a couple of new review tickets for which I may need some advice from experts of Python / Fortran / Octave modules: - https://bugzilla.redhat.com/show_bug.cgi?id=1893539 (calceph) - https://bugzilla.redhat.com/show_bug.cgi?id

Review swaps and advice for python / fortran / octave modules

Hello all, I have a couple of new review tickets for which I may need some advice from experts of Python / Fortran / Octave modules: - https://bugzilla.redhat.com/show_bug.cgi?id=1893539 (calceph) - https://bugzilla.redhat.com/show_bug.cgi?id=1895290 (python-calcephpy) Ideally, the python

Re:gcc-10 Fortran argument mismatch issue

On Tue, 2020-01-21 at 20:41 +, devel- requ...@lists.fedoraproject.org wrote: > -- > > Date: Tue, 21 Jan 2020 21:27:47 +0100 > From: Dominik 'Rathann' Mierzejewski > Subject: Re: gcc-10 Fortran argument mismatch issue > To: devel@lists.fedorapro

Re: gcc-10 Fortran argument mismatch issue

s. > > gcc has traditionally allowed certain type mismatches for arguments in > Fortran code. GCC would issue a diagnostic under -Wargument-mismatch > for these cases, but the issue was not considered fatal. > > Starting with gcc-10, these are now fatal errors which look something &g

Re: gcc-10 Fortran argument mismatch issue

On Tue, Jan 21, 2020 at 01:16:30PM -0700, Jeff Law wrote: > Starting with gcc-10, these are now fatal errors which look something > like this: > > > > Error: Rank mismatch in argument ‘array’ at (1) (rank-1 and scalar) Indeed, and https://gcc.gnu.org/gcc-10/porting_to.html#argument-mismatch

gcc-10 Fortran argument mismatch issue

So this is another issue that's going to be seen with gcc-10. I'd been hoping to get the time to fix packages correctly, but I think it's ultimately going to have to fall to the package maintainers. gcc has traditionally allowed certain type mismatches for arguments in Fortran code. GCC

mpi/fortran with -Wl,--as-needed

Hi, I saw that -Wl,--as-needed would be enabled by default on Fedora 29, it seems that we can't build a simple fortran program with this flag either on Fedora 28 or 29 with openmpi at least. Is this an MPI bug? Is this flag supposed to work in this context? Any help here would be really welcome

Re: fortran

On Sat, 06 Aug 2016 15:26:12 - ba...@laposte.net wrote: > Hello, > > i use fortran in my university : is it possible to have the last GNU > fortran (version 6) integrated in the spin distribution ! > gcc-gfortran package (6.1.x on >=f23)? -- devel mailing list devel@lists

fortran

Hello, i use fortran in my university : is it possible to have the last GNU fortran (version 6) integrated in the spin distribution ! bests regards -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[EPEL-devel] Re: MPI Fortran compiler detection failed on EPEL7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/17/2016 12:08 AM, Orion Poplawski wrote: > On 01/16/2016 03:44 PM, Antonio Trande wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> Hello everybody, >> >> OpenMPI Fortran compiler detection

[EPEL-devel] MPI Fortran compiler detection failed on EPEL7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello everybody, OpenMPI Fortran compiler detection fails during Sundials-OpenMPI(1.10.0) rebuilds on EPEL7: http://koji.fedoraproject.org/koji/taskinfo?taskID=12582324 Unexpectedly, cmake's Fortran compiler test works on ppc64le arch, but fails

[EPEL-devel] Re: MPI Fortran compiler detection failed on EPEL7

On 01/16/2016 03:44 PM, Antonio Trande wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello everybody, OpenMPI Fortran compiler detection fails during Sundials-OpenMPI(1.10.0) rebuilds on EPEL7: http://koji.fedoraproject.org/koji/taskinfo?taskID=12582324 Unexpectedly, cmake's Fortran

Re: Mass Fortran rebuilds due to new GCC?

:1.8.14-1.fc22.x86_64 healpix-devel-0:2.13a-15.fc22.x86_64 libxc-devel-0:2.1.0-4.fc22.x86_64 netcdf-fortran-devel-0:4.4.1-1.fc22.x86_64 plplot-fortran-devel-0:5.10.0-17.fc22.x86_64 qd-devel-0:2.3.15-1.fc22.x86_64 wannier90-devel-0:2.0.0-3.fc22.x86_64 And then I suppose everything that buildrequires

Re: Mass Fortran rebuilds due to new GCC?

in rawhide has broken all Fortran packages, desperately needing a mass rebuild. Can you expand on the breakage? Is it that they no longer rebuild? Or that they no longer run? I think, he's talking about the fact they are segfaulting… ;) Well, thats not really clear to me at least

Re: Mass Fortran rebuilds due to new GCC?

I need FORTRAN for R and R packages - if it's not 100% for the R ecosystme I'd consider any bugs to be at least blockers for beta, if not alpha. On Fri, Feb 13, 2015 at 12:59 PM, Björn Esser bjoern.es...@gmail.com wrote: Am Freitag, den 13.02.2015, 13:53 -0700 schrieb Kevin Fenzi: On Fri, 13

Re: Mass Fortran rebuilds due to new GCC?

On Fri, Feb 13, 2015 at 01:53:12PM -0700, Kevin Fenzi wrote: On Fri, 13 Feb 2015 12:47:07 -0800 Susi Lehtola jussileht...@fedoraproject.org wrote: as has happened many times before, the GCC bump in rawhide has broken all Fortran packages, desperately needing a mass rebuild. Can you

Re: Mass Fortran rebuilds due to new GCC?

On Fri, 13 Feb 2015 12:47:07 -0800 Susi Lehtola jussileht...@fedoraproject.org wrote: Hi, as has happened many times before, the GCC bump in rawhide has broken all Fortran packages, desperately needing a mass rebuild. Can you expand on the breakage? Is it that they no longer rebuild

Fortran module ABI issue

Often (though not always) with new GCC versions there is a new version for Fortran modules that is incompatible with old versions. An example error is here from the rebuild of the netcdf-fortran package: use mpi 1 Fatal Error: Cannot read module file 'mpi.mod' opened at (1), because

gfortran module versioning - f17/rawhide fortran module rebuild needed

It appears that gcc-gfortran-4.7.0-0.11.fc17.x86_64 (in rawhide) and gcc-gfortran-4.7.0-0.12.fc17.x86_64 (in f17 - branching fun!) produces and uses Fortran modules version 9 as I'm getting this trying to rebuild netcdf: use mpi 1 Fatal Error: Wrong module version '8' (expected '9