[...snip...] GCC generated/bindings/org/gnome/gtk/GtkNotebook.c generated/bindings/org/gnome/gtk/GtkNotebook.c: In function 'Java_org_gnome_gtk_GtkNotebook_gtk_1notebook_1query_1tab_1label_1packing': generated/bindings/org/gnome/gtk/GtkNotebook.c:1141: warning: passing argument 3 of '(*env)->ReleaseBooleanArrayElements' from incompatible pointer type generated/bindings/org/gnome/gtk/GtkNotebook.c:1144: warning: passing argument 3 of '(*env)->ReleaseBooleanArrayElements' from incompatible pointer type generated/bindings/org/gnome/gtk/GtkNotebook.c:1147: warning: passing argument 3 of '(*env)->ReleaseIntArrayElements' from incompatible pointer type GCC generated/bindings/org/gnome/gtk/GtkItem.c gcc: : No such file or directory gcc: no input files make: *** [build-java] Error 1 Note: The file GtkItem.c *does* exist and has the same permissions as all other files in that directory: /var/tmp/portage/dev-java/java-gnome-4.0.6/work/java-gnome-4.0.6/generated/bindings/org/gnome/gtk: -rw-r--r-- 1 portage portage 1598 Apr 10 13:37 GtkItem.c
Created attachment 149342 [details] emerge --info
Created attachment 149344 [details] build log
Um. Whoa. Weird. Two things to do: In /var/tmp/portage/dev-java/java-gnome-4.0.6/work/java-gnome-4.0.6/ you'll find a file called .config Can you attach it here? (it's the output of ./configure running) I'm not sure it'll tell me anything we don't already know, but with GCC of all things misbehaving... Then, as a diagnostic, hop into /var/tmp/portage/dev-java/java-gnome-4.0.6/work/java-gnome-4.0.6/ and manually run # V=1 make and see what it says. It should resume at compiling that C file; the actual command being executed will be shown. That might prove insightful. Or not :| AfC
Created attachment 149633 [details] .config
Created attachment 149635 [details] V=1 emerge =java-gnome-4.0.6
Created attachment 149636 [details] cd /var/tmp/portage/dev-java/java-gnome-4.0.6/work/java-gnome-4.0.6; V=1 make
(In reply to comment #3) > Um. Whoa. Weird. > > Two things to do: > > In /var/tmp/portage/dev-java/java-gnome-4.0.6/work/java-gnome-4.0.6/ you'll > find a file called .config Can you attach it here? (it's the output of > ./configure running) I'm not sure it'll tell me anything we don't already know, > but with GCC of all things misbehaving... > > Then, as a diagnostic, hop into > /var/tmp/portage/dev-java/java-gnome-4.0.6/work/java-gnome-4.0.6/ and manually > run > > # V=1 make > > and see what it says. It should resume at compiling that C file; the actual > command being executed will be shown. That might prove insightful. Or not :| > > AfC > Not. The failed command from the emerge and the equivalent command from the manual build are identical. <sigh>. I am going to try without CCache. I have uploaded the info you requested. BTW, the emerge proceeds normally once all the files have been compiled. I interrupted the manual compile sometime after it had compiled GtkItem.c, and the restarted emerge stopped again (same error) at another file. There seem to be a number of errors at the beginning of the build.log file, but none involving GtkItem.{c,java}.
Created attachment 149641 [details] V=1 FEATURES="-ccache" emerge =java-gnome-4.0.6 | tee /tmp/build.log
Works without CCache. I've attached the output of V=1 FEATURES="-ccache" emerge =java-gnome-4.0.6
Hm. ccahce. We've had problems with that on other distros. Actually, if you look closely at the one the worked, you'll see that it used ccache anyway: /usr/bin/ccache /usr/bin/gcc because java-gnom's build is smart enough to see if it is there and use it if it is. The builds that failed for you seemed to be FEATURES=ccache, which invoked the compiler as: /usr/lib/ccache/bin/gcc which, although it is supposed to work, has caused problems elsewhere [Debian]. I don't really know why. That said, it worked for several hundred files, so why it suddenly didn't work for one is a tad bizarre. I don't run FEATURES=ccache here (unless one is recompiling the same package all the time, what's the point?) but I'll see if I can duplicate this so I can work out a change to suggest for java-gnome 4.0.7 AfC
... but running just /usr/lib/ccache/bin/gcc or /usr/bin/ccache /usr/lib/ccache/bin/gcc as my compiler by hacking it manually doesn't replicate the problem you experienced. Hm. AfC
4.0.6 removed from tree. Please reopen if the issue can be reproduced with the in tree versions.
