Build failure with gcc14: Error: There is no specific subroutine for the generic 'set_string' at (1) #1059
Description
Description
---> Building fpm
Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.10.1" && FPM_CFLAGS="-Os -arch arm64" FPM_LDFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch arm64" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.10.1/install.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 27309 0 27309 0 0 24654 0 --:--:-- 0:00:01 --:--:-- 24669
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 1513k 100 1513k 0 0 586k 0 0:00:02 0:00:02 --:--:-- 1854k
fpm.F90:28554:101:
28554 | call set_string(table, "descriptor", descriptor_name(self%descriptor), error, 'git_target_t')
| 1
Error: There is no specific subroutine for the generic 'set_string' at (1)
fpm.F90:30325:93:
30325 | call set_string(table,"os-type",os_type_name(self%os_type), error, 'profile_config_t')
| 1
Error: There is no specific subroutine for the generic 'set_string' at (1)
fpm.F90:31376:9:
31376 | use fpm_git, only: git_target_t, git_target_tag, git_target_branch, &
| 1
Fatal Error: Cannot open module file 'fpm_git.mod' for reading at (1): No such file or directory
compilation terminated.
Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.10.1" && FPM_CFLAGS="-Os -arch arm64" FPM_LDFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch arm64" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.10.1/install.sh
Exit code: 1
Expected Behaviour
It should build with the current release of GCC.
Version of fpm
0.10.1
Platform and Architecture
macOS 14.5 / arm64
Additional Information
Also failed on buildbots: https://github.com/macports/macports-ports/actions/runs/9792802490/job/27039380730?pr=24796
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
barracuda156 commentedon Jul 4, 2024
No error with gcc 13.3.0:
perazz commentedon Jul 5, 2024
@barracuda156 This is a regression issue introduced by gfortran-14. It was fixed in #1013 already. It will appear as soon as a new release is deployed.
barracuda156 commentedon Jul 6, 2024
@perazz Thank you! I will try the fix.
If it is a regression in
gfortranitself, is GCC upstream made aware of it?barracuda156 commentedon Jul 6, 2024
Well, I will need to wait until the release, since FPM fetches its bootstrap version during the build, and it is non-trivial to implement patching it.
fpm, fortran PG: avoid gcc14 until next release of fpm
fpm, fortran PG: avoid gcc14 until next release of fpm
rouson commentedon Jul 16, 2024
On a different but related note, at some point it would be great to remove anything
gfortran-specific infpmso that buildingfpmwith other compilers becomes an option too. I have tried building with the Cray, Intel (ifx), and NAG compilers and errors prevented building with all three. This is usually a sign that there are non-standard extensions or possibly even errors in the code.perazz commentedon Jul 17, 2024
It's a great idea @rouson. If you or anyone in your team has patches to contribute, it would be great.
I had only tried to add the Intel compiler in the fpm CI and last year I spent quite a lot of time on it: see #894 #898 #901 #964. Then, the switch to
ifxexposed compiler bugs that are still currently not fixed, see #994, so it was removed from the CI.barracuda156 commentedon Dec 9, 2024
@perazz It’s been quite a while, maybe it is possible to make a new micro-version tag?
barracuda156 commentedon Dec 27, 2024
@perazz I tried building from “current” (which includes your patches), but it still fails:
P. S. Notice, this is a different error though.
perazz commentedon Dec 27, 2024
Yes, a new release is definitely necessary.
What compiler version is causing this? By running "current":
everything works fine:
2 remaining items