Package Details: gcc6-gcj 6.5.0-9

Git Clone URL: https://aur.archlinux.org/gcc6.git (read-only, click to copy)
Package Base: gcc6
Description: Java front-end for GCC
Upstream URL: https://gcc.gnu.org/gcc-6/
Licenses: GPL, custom, LGPL, FDL
Replaces: gcc-gcj
Submitter: svenstaro
Maintainer: valandil
Last Packager: valandil
Votes: 20
Popularity: 0.000113
First Submitted: 2018-05-17 20:56 (UTC)
Last Updated: 2023-06-03 19:08 (UTC)

Dependencies (18)

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 2023-06-03 19:09 (UTC)

Thanks, it should be fixed now.

imcb commented on 2023-05-30 23:59 (UTC) (edited on 2023-05-30 23:59 (UTC) by imcb) 

error: failed to commit transaction (conflicting files)
/usr/lib/gcc/x86_64-pc-linux-gnu/6.5.0/libstdc++.a exists in both 'gcc6-libs' and 'gcc6'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.5.0/libstdc++.la exists in both 'gcc6-libs' and 'gcc6'
Errors occurred, no packages were upgraded.

valandil commented on 2023-04-22 01:49 (UTC)

Thanks, I'm testing this out right now. My initial plan was to fix with by either using --with-included-gettext or a statically compiled version of gettext, but for some reason the former didn't work and the latter is very annoying to actually do :)

bone commented on 2023-04-20 16:53 (UTC)

Quote/Solution from gcc8 package which also works here: by "alexf91": "Disabling native language support fixes the build problems. Edit PKGBUILD and add --disable-nls when the configure script is called."

This fixes the "`GLIBCXX_3.4.30' not found" error and makes a build possible.

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}/libstdc++.so*". 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}/libstdc++.so*").

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