Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: gcc-gcj 6.3.1-2

Git Clone URL: (read-only)
Package Base: gcc-gcj
Description: The GNU Compiler for Java
Upstream URL:
Licenses: GPL, LGPL
Submitter: Allan
Maintainer: valandil
Last Packager: valandil
Votes: 243
Popularity: 3.271133
First Submitted: 2009-05-08 17:48
Last Updated: 2017-01-14 15:55

Pinned Comments

valandil commented on 2016-05-11 14:02

This package, gcc-gcj, is a subset of the GNU Compiler Collection, specifically the Java compiler part. In Arch Linux, it is mostly used to compile pdftk, a very nifty command-line PDF tool.

When reporting any build issue, please provide your current version of gcc and any error message.

It is *very* long to compile and takes up a lot of disk space while doing so. Do not use AUR helpers to compile this thing, you'll probably end up filling your /tmp partition and crash the compilation process. Download the PKGBUILD (either with yaourt -G gcc-gcj, with the helper of your choice or even manually) and run makepkg.

If you do not want to compile this and only need it for pdftk, consider using pdftk-bin. As its name indicates, it is a precompiled version of pdftk and depends only on libgcj, also precompiled.

Latest Comments

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

valandil commented on 2017-01-14 23:23

@cfr42 Somebody flagged the package out of date saying that the integrity check failed. I assumed that the SHA sums were wrong and blindly pushed a new update after running updpkgsums. My bad.

I won't downgrade the package, as people who already upgraded would have to recompile again.

cfr42 commented on 2017-01-14 22:54

Today I got an update for this package. The only difference between the new package build and yesterday's is that the release number is now 2 rather than 1. Is this a mistake? If not, it seems egregious, especially given the length of time it takes to build this. Now I'm going to keep getting messages saying this is outdated unless I rebuild just to change the version number of the package, which is ridiculous.

valandil commented on 2017-01-11 14:27

@bidulock Oh, I hadn't checked that yet. I had deferred this until the gcc update.

I don't change anything then in the next update :)

bidulock commented on 2017-01-09 20:07

flex, bison and pkg-config are in 'base-devel'. You need to load base-devel to build anything on AUR. It is normal practice to not include 'depdends' on packages in 'base' and to not include 'makedepends' on packages in 'base-devel'. So, why do they need to be added as dependencies?

valandil commented on 2017-01-09 16:17

@afwlehmann Thanks, I will do that in the next update to gcc.

afwlehmann commented on 2017-01-09 09:58

Please add missing dependencies to `flex`, `pkg-config` and `bison` (not sure about `bison`, but 100% about `flex` and `pkg-config`).

valandil commented on 2016-10-31 15:19

@Alad Please provide your gcc version.

Alad commented on 2016-10-31 11:23

Doesn't build:

./.libs/ undefined reference to `__cxa_throw_bad_array_new_length'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:9535: jv-convert] Error 1
make[3]: *** Waiting for unfinished jobs....
./.libs/ undefined reference to `__cxa_throw_bad_array_new_length'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:9482: gcj-dbtool] Error 1
/home/archie/.cache/aursync/gcc-gcj/src/gcc-c2103c17ed399b38670fbcdb8c0d5bd750a9e754/build/x86_64-pc-linux-gnu/libjava/.libs/ undefined reference to `__cxa_throw_bad_array_new_length'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:9496: gij] Error 1

kal commented on 2016-10-20 11:52


Thanks a lot for your tip about pdftk-bin. I desperately needed to edit some pdfs fast and your help was really appreciated.

Keep up the good work !

cfr42 commented on 2016-06-19 16:11

@valandil Thanks. The new version works fine. I don't remember but I routinely remove the src and pkg directories. (Actually, I routinely use a new directory and copy in anything I want, mostly any links to older packaged versions.) So although it is possible I failed to remove the src directory, it is relatively unlikely. This time I removed the git checkout of gcc from the relevant subdirectory of ~ as well. I don't know if that mattered, but it compiled fine this time.