The java/openjdk6 port will not build "out of the box". If you try to build it, you will get this error: gmake[6]: *** 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. Apparently, this has been a known problem for for at least a full year now: http://lists.freebsd.org/pipermail/freebsd-java/2012-May/009704.html The solution is apparently to hack the line: MAKE_JOBS_NUMBER=1 into your /etc/make.conf file before building java/openjdk6. This problem should be solved within the port itself, or at the very least, this issue/problem should be mentioned _somewhere_ within the UPDATING file. Fix: I have not developed a fix, but I will, if the port maintainer is either unable or unwilling to do so. Just ask. How-To-Repeat: portinstall java/openjdk6
Responsible Changed From-To: freebsd-ports-bugs->freebsd-java Over to maintainer (via the GNATS Auto Assign Tool)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 MAKE_JOBS_NUMBER=1 is not necessary unless you forced it. % grep JOBS /etc/make.conf % svnversion . 318205 % make -V PORTNAME openjdk6 % make -V MAKE_JOBS_SAFE % make -V MAKE_JOBS_UNSAFE % make -V MAKE_JOBS_NUMBER 1 % sysctl -n kern.smp.cpus 2 Also, QAT had no problem at all: https://qat.redports.org/buildarchive/20130508224800-3579/ Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJRksUbAAoJECXpabHZMqHOOPwH/R8GyDH62VKoYRFUSKb09gZr F3zgv5LVNPLPnwYnkiFj84abilmC2ZJl6bpiEuA4kpenst9P6rLcr0NW/UU1Pcag gAYpiSAoeWWYXgSBSMsnR7nZIk3jNwW21if/If2yZyL4W5+ZVNHm+UdAHX5RLj45 23SqIaTcvkgQ0ABqwSjOixdrk+vavIWRIemMlLboXKyzM1rp06W8OfuESBcz4mt+ gvOdCjqP6rikJAgN7PgfV65jeSrLuA4rbDC+UGu2+4tp8iAyt0yKuE/Iw4pJfU20 0ugB+GqEX2GzGcK2pTtPZo9XRhFrL/RRQbM2+mWh2YNSOenbaJ0S3VhJTswh1KE= =pWlO -----END PGP SIGNATURE-----
In message <5192C51B.9020509@FreeBSD.org>, you wrote: >MAKE_JOBS_NUMBER=1 is not necessary unless you forced it. I do not know what you are talking about. I did not "force" anything. I simply did: portupgrade vlc and then, in the configuration for vlc, there was an option to support Blu-Ray menus by using libbluray... or something like that... so I enabled that. After that, portupgrade started to build the (new) dependencies for vlc and that is when I got the failure building java/openjdk6. The bug exists, it is real, and I did not "force" anything. I believe that anyone and everyone will experience the exact same build failure as I reported if they also simply do what I did, i.e. freshen your ports tree via "portsnap fecth update", and then simply "portupgrade vlc" and then, in the config menu for vlc, enable blu-ray menu support. Regards, rfg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-05-14 19:56:23 -0400, Ronald F. Guilmette wrote: > > In message <5192C51B.9020509@FreeBSD.org>, you wrote: > >> MAKE_JOBS_NUMBER=1 is not necessary unless you forced it. > > I do not know what you are talking about. I did not "force" > anything. I simply did: > > portupgrade vlc > > and then, in the configuration for vlc, there was an option to > support Blu-Ray menus by using libbluray... or something like > that... so I enabled that. > > After that, portupgrade started to build the (new) dependencies for > vlc and that is when I got the failure building java/openjdk6. > > The bug exists, it is real, and I did not "force" anything. > > I believe that anyone and everyone will experience the exact same > build failure as I reported if they also simply do what I did, > i.e. freshen your ports tree via "portsnap fecth update", and then > simply "portupgrade vlc" and then, in the config menu for vlc, > enable blu-ray menu support. I understand your frustration but I can't reproduce the problem at all. In fact, I've heard/seen some intermittent complaints like this before[1] but I was never able to reproduce anything like that. :-( Jung-uk Kim 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=156674 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJRkteLAAoJECXpabHZMqHOBCkIALInFjgdiuW7PlsVb4idPwwP ImVIrIedaqLkkWsYiPUywFOBCcuTNmecJ1V74z7f6UtQjqvVmqZfsiG0FDuenoSA fDZCwtNZhi4CeycfwfxqrPnCQVQl0EZjPOCYiQvbCRaZNtNH/CeAoVel+2E6V/s+ GvNLSoySi0TZn3U+K1qcT9LoG2KNTDZmK/XEmvEapbtv31Qxl0IXMZEn8mYCRLwY 1K2T0lbuqLNCvo3dBLzEIq88d2XQ7JcidBLPinfN+U2Ua+urV2tAj9kBel+Cl09r oj8HuLKupGqzILBMGtq3wFxRvBZVvTtZCvTaGPdhNKTxKrsJtq/TuzAc4Wz4hgA= =BeNS -----END PGP SIGNATURE-----
In message <5192D78B.6090402@FreeBSD.org>, you wrote: >On 2013-05-14 19:56:23 -0400, Ronald F. Guilmette wrote: >> >> In message <5192C51B.9020509@FreeBSD.org>, you wrote: >> >>> MAKE_JOBS_NUMBER=1 is not necessary unless you forced it. >> >> I do not know what you are talking about. I did not "force" >> anything. I simply did: >> >> portupgrade vlc >> >> and then, in the configuration for vlc, there was an option to >> support Blu-Ray menus by using libbluray... or something like >> that... so I enabled that. >> >> After that, portupgrade started to build the (new) dependencies for >> vlc and that is when I got the failure building java/openjdk6. >> >> The bug exists, it is real, and I did not "force" anything. >> >> I believe that anyone and everyone will experience the exact same >> build failure as I reported if they also simply do what I did, >> i.e. freshen your ports tree via "portsnap fecth update", and then >> simply "portupgrade vlc" and then, in the config menu for vlc, >> enable blu-ray menu support. > >I understand your frustration but I can't reproduce the problem at >all. In fact, I've heard/seen some intermittent complaints like this >before[1] but I was never able to reproduce anything like that. :-( Well, if you can't reproduce it, then I do understand that nothing can really be done. If I figure out a way to reliably reproduce it, I'll let you know. Regards, rfg
I have the same environment as Ronald and the fix should be relatively trivial. It's a Makefile problem, as far as I can tell, and all the env and make.conf variables that are being bandied about did not help me. I was able to overcome the compile problem by manually creating the following directories after the compile bombed out /usr/ports/java/openjdk6/work/hotspot/src/cpu/amd64 /usr/ports/java/openjdk6/work/hotspot/src/cpu/amd64/vm /usr/ports/java/openjdk6/work/hotspot/src/os_cpu/bsd_amd64 /usr/ports/java/openjdk6/work/hotspot/src/os_cpu/bsd_amd64/vm and copying the files from the corresponding (bsd_)?x86/vm directory at the same level into them, based on the observation that they contain both x86 and amd64 files. I have not checked whether these vm directories are distributed or generated during build. I also can't tell if these directories could be created automatically under different circumstances - I'm simply building a fresh machine with updated ports (head) and followed the handbook instructions for installing the IcedTea plugin.
I just marked the port as MAKE_JOBS_UNSAFE (r356867).