Package Details: gcc9-fortran 9.5.0-1

Git Clone URL: https://aur.archlinux.org/gcc9.git (read-only, click to copy)
Package Base: gcc9
Description: Fortran front-end for GCC (9.x.x)
Upstream URL: https://gcc.gnu.org
Licenses: GPL, custom, LGPL, FDL
Submitter: dvzrv
Maintainer: severach
Last Packager: severach
Votes: 7
Popularity: 0.003468
First Submitted: 2020-11-23 19:59 (UTC)
Last Updated: 2023-02-05 22:12 (UTC)

Pinned Comments

jonathon commented on 2020-11-30 14:28 (UTC)

Please read the AUR wiki page before reporting issues.

If you are experiencing a build issue then ensure you are not using an AUR helper and are using a clean chroot.

Latest Comments

1 2 3 Next › Last »

severach commented on 2023-02-05 22:17 (UTC)

Try it now. The problem is that the compiler links to the system libicuuc.so, which can only link to the system libstdc++.so.6, not the compiler provided libstdc++. I didn't bump pkgrel because the old compiles still work.

jvanstraten commented on 2023-01-11 10:47 (UTC) (edited on 2023-01-11 14:15 (UTC) by jvanstraten)

I'm not terribly familiar with the AUR system so I can't comment on any of that (I'm building from source directly), but the build issue seems to be due to a bug in GCC's build system. See https://gcc.gnu.org/pipermail/gcc-help/2022-July/141791.html for an explanation and a link to a patch for the source tree. I've yet to finish building successfully, but it fails a lot later with that patch, and my remaining issues might well be down to not yet passing anything but --prefix to configure. Hope this helps someone.

ETA: I also had to patch in https://github.com/gcc-mirror/gcc/commit/2701442d0cf6292f6624443c15813d6d1a3562fe to make it build.

4rty commented on 2022-12-26 19:01 (UTC)

I'm still getting the 'GLIBCXX_3.4.30' not found error as of 12/26/2022 that has been reported over the last few months. I tried using @bialy solution using docker image base-devel-20210418.0.20194 but that isn't working either not sure how he managed to get it to work.

bialy commented on 2022-11-15 16:55 (UTC)

Same issue with GCC10 - https://aur.archlinux.org/packages/gcc10. It seems that there is a problem with one of the building stages if too 'new' compiler is installed in the OS. For me it is GCC12.2.

I was able to build GCC9 using docker image base-devel-20210418.0.20194. GCC packages seems to work after installation on the host OS.

rengolin commented on 2022-11-15 16:53 (UTC) (edited on 2022-11-15 16:54 (UTC) by rengolin)

Same here:

.cache/yay/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/libicuuc.so.72)

My system libstdc++ has the symbol:

$ strings /usr/lib/libstdc++.so.6 | grep "^GLIBCXX_3.4.30" 
GLIBCXX_3.4.30`

But the one that the package brings does not:

$ strings .cache/yay/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6 | grep "^GLIBCXX_3.4." | sort -u
..
GLIBCXX_3.4.27
GLIBCXX_3.4.28

The error is when creating the archive, so it could be that it's mixing system libraries with built libraries. It's possible that libstdc++ at the time of gcc9 didn't have that version and some rogue library (from the system) does and requires it, thus the error.

I don't know enough about the GCC build system to know what's wrong in the PKGBUILD, though.

bialy commented on 2022-11-14 13:11 (UTC) (edited on 2022-11-15 16:55 (UTC) by bialy)

I am trying to build package in a clean chroot makechrootpkg -c -r $CHROOT, but at the end I am receiving this

msgfmt: /build/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/libicuuc.so.72)
msgfmt: /build/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/libicuuc.so.72)

lamp commented on 2022-09-20 17:04 (UTC)

When installing gcc9 I see that it provides gcc9-libs, however it doesn't seem to provide a lib32-gcc9-libs (and there doesn't seem to be another package for this). Is there a known way for me to modify the PKGBUILD in order to build with support for using gcc -m32 with this gcc9 package? Or a different package that I am missing?

saburouta commented on 2022-08-28 20:27 (UTC) (edited on 2022-08-28 20:29 (UTC) by saburouta)

Fails to build in a clean chroot:

/usr/include/linux/mount.h:95:6: error: multiple definition of 'enum fsconfig_command'
   95 | enum fsconfig_command {
      |      ^~~~~~~~~~~~~~~~
In file included from /build/gcc9/src/gcc/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:55:
/usr/include/sys/mount.h:189:6: note: previous definition here
  189 | enum fsconfig_command
      |      ^~~~~~~~~~~~~~~~
In file included from /usr/include/linux/fs.h:19,
                 from /build/gcc9/src/gcc/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:68:
/usr/include/linux/mount.h:129:8: error: redefinition of 'struct mount_attr'

baloe commented on 2022-08-27 02:15 (UTC)

This does not compile in Manjaro.

Exits with make: *** [Makefile:997: all] Error 2

See https://forum.manjaro.org/t/unable-to-build-install-gcc9/119819/16?u=baloe

dbermond commented on 2022-06-17 18:14 (UTC)

@jonathon The package fails to build with lto enabled. This option is enabled by default on devtools, and may be enabled by the user in makepkg.conf. You should explicitly disable lto by adding '!lto' to the 'options' array like is done by repository gcc, repository gcc11, AUR gcc10 and AUR gcc7.