Created attachment 143892 [details] Build STDOUT Trying to build java/jboss72 on FreeBSD CURRENT (amd64) fails with the following make error in java/openjdk6: Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. gmake[9]: *** No rule to make target `/usr/ports/java/openjdk6/work/hotspot/src/cpu/amd64/vm/x86_64.ad', needed by `../generated/adfiles/bsd_x86_64.ad'. Stop. gmake[8]: *** [ad_stuff] Error 2 gmake[7]: *** [product] Error 2 gmake[6]: *** [generic_build2] Error 2 gmake[5]: *** [product] Error 2 gmake[4]: *** [hotspot-build] Error 2 gmake[3]: *** [build_product_image] Error 2 # uname -a FreeBSD vmunix.jensenwaud.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r267488: Sun Jun 15 02:13:42 UTC 2014 root@grind.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
it's building everywhere: http://portsmon.freebsd.org/portoverview.py?category=java&portname=openjdk6 A similar report (187921) was closed as "not jobs safe". Is your ports tree up to date?? I think this should be closed as duplicate of 187921
(In reply to John Marino from comment #1) > it's building everywhere: > http://portsmon.freebsd.org/portoverview.py?category=java&portname=openjdk6 > > A similar report (187921) was closed as "not jobs safe". > > Is your ports tree up to date?? > > I think this should be closed as duplicate of 187921 I can confirm that my ports tree is up to date. I ran ``portsnap fetch update'' and recompiled 'make install'. The same error occurs.
Assigning PR to java@. I still think the fact it builds everywhere (according to portsmon) is not a good sign for you though.
I have the same error, FreeBSD 10.0-STABLE #13 r268437
Problem only if built as dependency of anoher port, in my case libreoffice, (pkg_replace libreoffice), but seems ok if I build openjdk6 directly (pkg_replace -N /usr/ports/java/openjdk6), still not finished ...
Is this still relevant or could it be closed?
*** This bug has been marked as a duplicate of bug 187921 ***