Package Details: gcc6 6.5.0-7

Git Clone URL: (read-only, click to copy)
Package Base: gcc6
Description: The GNU Compiler Collection - C and C++ frontends (6.x.x)
Upstream URL:
Licenses: GPL, custom, LGPL, FDL
Submitter: Svenstaro
Maintainer: valandil
Last Packager: valandil
Votes: 21
Popularity: 0.166696
First Submitted: 2018-05-17 20:56 (UTC)
Last Updated: 2021-08-25 01:29 (UTC)

Dependencies (16)

Sources (6)

Pinned Comments

valandil commented on 2020-08-24 15:06 (UTC)

I highly recommend building this package in a clean chroot. This avoids the use of a AUR helper, which sometimes uses /tmp as the stating directory, which often gets filled completely by gcc's build process.

It also provides a clean environment, which minimizes interactions between your current environment and gcc's build process.

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

valandil commented on 2022-07-13 01:04 (UTC) (edited on 2022-07-13 01:05 (UTC) by valandil)

It is required by the java component:

checking for glib-2.0 >= 2.4 gthread-2.0 >= 2.4... yes
checking GLIB_CFLAGS... -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-4 -pthread 
checking GLIB_LIBS... -lgthread-2.0 -pthread -lglib-2.0 
checking for libart-2.0 >= 2.1... Package libart-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libart-2.0.pc' to the PKG_CONFIG_PATH environment variable Package 'libart-2.0', required by 'virtual:world', not found
configure: error: Library requirements (libart-2.0 >= 2.1) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.
make[1]: *** [Makefile:19636: configure-target-libjava] Error 1

I started maintaining gcc6 to be able to compile pdftk, then written in java. I believe it is now pdftk-gcj in the AUR. gcc6 is the last version of gcc with the gcj component, so it's normal that gcc7 doesn't require it.

petronny commented on 2022-07-11 10:14 (UTC)

Could you confirm if libart-lgpl is realy needed to build this package?

It's a little wierd since gcc{5,7,8,9} don't require it. Especially for gcc7, I just successfully build it in a clean chroot.

valandil commented on 2021-08-25 01:30 (UTC)

Hmm, it probably was needed a long time ago. I've removed it, tested the build and it works fine. Just pushed a new version.

bartus commented on 2021-08-22 11:21 (UTC)

Why option=(!makeflags) it builds fine with 16 threads here.

valandil commented on 2021-04-09 11:08 (UTC) (edited on 2021-04-09 11:09 (UTC) by valandil)

@xdavidwu Just letting know that I did see your messages, and that I'm working on cleaning up the PKGBUILD a bit more before publishing the fix. If that's too inconvenient I can revert the changes of the offending commit and push a cleaner PKGBUILD later.

Thanks for the link, it was helpful!

xdavidwu commented on 2021-04-07 13:34 (UTC)

The latest commit in PKGBUILD (ea4ffd34ed11) makes this package fails to build.

The commit contains changes that squash pattern matching into double quotes, like this one + rm "${pkgdir}/${_libdir}/*". This will not work. Double-quotes allow parameter expansion, arithmetic expansion and command subsitution but not pattern matching. The asterisks are treated as literals and do not expand. Reference: POSIX definition of shell command language, section 2.2.3 Double-Quotes. A quick test with echo * (which expands) and echo "*" (which prints the asterisk) indicates that bash seems to do the same thing.

makepkg in a clean container fails at that line (rm "${pkgdir}/${_libdir}/*").

ffcc commented on 2020-09-28 12:56 (UTC)

Forget it. It installs without any file conflicts all right. It did not due to the AUR helper and some ancient aur database.

Sorry for the inconvenience.

valandil commented on 2020-09-28 12:49 (UTC)

I can't reproduce this issue. I rebuilt the latest version (6.5.0-4) in a clean chroot, and was able to install all packages without file conflicts. Can you show the detailed pacman output?

ffcc commented on 2020-09-24 16:11 (UTC)

"gcc6" and "gcc6-libs" have conflicting files. As mentioned in former comments they can be installed using pacman's --overwrite flag:

pacman -S --overwrite /usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/libstdc++.a,/usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/ gcc6 gcc6-libs

But, "libstdc++.a" file is not the same in both packages. Which "libstdc++.a" file should we keep? "gcc6"'s or "gcc6-libs"'?

valandil commented on 2020-08-27 12:35 (UTC)

No worries. gcc can be a pain to build, so I always build the versions of gcc I maintain in a clean chroot.

I'll look into some of the makedepends, I don't recall needing all of them when I maintained the package before it went to community. But my memory might be flawed...