From owner-freebsd-questions@FreeBSD.ORG Wed Mar 31 09:43:34 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35C8616A4CE for ; Wed, 31 Mar 2004 09:43:34 -0800 (PST) Received: from nobilis.com (host51.216.41.46.conversent.net [216.41.46.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B22743D1D for ; Wed, 31 Mar 2004 09:43:33 -0800 (PST) (envelope-from jwilson@nobilis.com) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 31 Mar 2004 12:43:32 -0500 Content-class: urn:content-classes:message Message-ID: <76CBA4753FF32448894B0E13B59C96B81D30B3@yoda.us.nobilis.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problems building JDK 1.4 Thread-Index: AcQWf5KBBW3Q4ooaQ++WqgOeFPahGAAxWjCw From: "Jason Wilson" To: "FreeBSD Questions" Subject: RE: Problems building JDK 1.4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2004 17:43:34 -0000 Babbling Blatherscythe! Chris Meyers had this to say: > I am trying to build java/jdk14 with portupgrade, and I have run into > a problem. After downloading all the necessary patches and the j2sdk > binaries and src files from Sun, I ran the following: =20 >=20 > portupgrade --new java/jdk14 >=20 > Things went along fine for about 2 hours, and then wham I get the > following error:=20 >=20 > Java HotSpot(TM) Client VM warning: Can't detect initial thread stack > location > /usr/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java/util/Curre ncyData.java:1: > 'class' or 'interface' > expected Java HotSpot(TM) Client VM warning: Can't detect initial > thread stack location ^ > /usr/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java/util/Curre ncyData.java:1: > unclosed character literal Java HotSpot(TM) Client VM warning: Can't > detect initial thread stack location ^ 2 errors =20 > gmake[4]: *** [.compile.classlist] Error 1 > gmake[4]: Leaving directory > `/usr/ports/java/jdk14/work/j2se/make/java/java'=20 > gmake[3]: *** [optimized] Error 2 > gmake[3]: Leaving directory > `/usr/ports/java/jdk14/work/j2se/make/java/java'=20 > gmake[2]: *** [all] Error 1 > gmake[2]: Leaving directory > `/usr/ports/java/jdk14/work/j2se/make/java'=20 > gmake[1]: *** [all] Error 1 > gmake[1]: Leaving directory `/usr/ports/java/jdk14/work/j2se/make' > gmake: *** [j2se-build] Error 2 > *** Error code 2 >=20 > Stop in /usr/ports/java/jdk14. > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portupgrade8248.0 make=20 > ** Fix the problem and try again. > ** The following packages were not installed or upgraded (*:skipped / > !:failed) > ! java/jdk14 (unknown build error) >=20 > I did some searching and noticed that someone else posted the exact > same problem a couple weeks ago, but unfortunately no one replied to > his problem. =20 >=20 > Has anyone solved this, or know what I should do to fix the problem? > Here's some more info that may be helpful:=20 >=20 > port: jdk-1.4.2p6_4 > uname -mp: 5.1-RELEASE-p2 i386 >=20 > Thanks for any help, > Chris >=20 > p.s. sorry for the long lines in the error I know it flies by rather quickly, but paying attention while the Makefile flies by never hurts. -- To build JDK 1.4.2 port, you should have linux emulation -- enabled in the kernel and linux procfs (linprocfs) filesystem -- mounted. I had a failure in just about the same spot, if I recall correctly. Sun has a linux release for the jdk, but no FreeBSD release. In order to build a native compile of the jdk on FreeBSD, the linux build is used to compile it. Hence, linux emulation is require for the build phase. You can go ahead and remove the linux emulation ports after you're done with the build if you like. Part of the build process from new I believe installs the necessaru linuxbase port, if they're not there already. What it doesn't do is load the kernel module and mount the linprocfs filesystem for you - which is where my failure happened, and probably yours as well. So... Granted that you have the linux ports installed (pkg_info linux_base, or if you like waiting... portversion | grep linux_base), load the linprocfs kernel module and mount a linprocfs file system: kldload linprocfs mount -t linprocfs linprocfs /compat/linux/proc (or, add a linprocfs entry with the above mountpoint to your fstab and do a mount linprocfs) Now try rebuilding the jdk14 port. Regards, Jason Wilson Director of Technology Nobilis Software