Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Sep 2004 15:01:56 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Mike Meyer <mwm@mired.org>
Cc:        phantom@freebsd.org
Subject:   Re: jdk14 not building?
Message-ID:  <20040904140156.GA16402@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <16697.36388.46776.777486@guru.mired.org>
References:  <16697.36388.46776.777486@guru.mired.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--9amGYk9869ThD9tj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 04, 2004 at 04:43:00AM -0500, Mike Meyer wrote:
> I'm getting the attached when trying to build jdk14, using the
> linux-sun-jdk as the pre-installed jdk.
>=20
> /datmp/ports/usr/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java=
/util/CurrencyData.java:1: 'class' or 'interface' expected
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack loc=
ation
> ^
> /datmp/ports/usr/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java=
/util/CurrencyData.java:1: unclosed character literal
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack loc=
ation
>                                        ^
> 2 errors
> gmake[4]: *** [.compile.classlist] Error 1
> gmake[4]: Leaving directory `/datmp/ports/usr/ports/java/jdk14/work/j2se/=
make/java/java'
> gmake[3]: *** [optimized] Error 2
> gmake[3]: Leaving directory `/datmp/ports/usr/ports/java/jdk14/work/j2se/=
make/java/java'
> gmake[2]: *** [all] Error 1
> gmake[2]: Leaving directory `/datmp/ports/usr/ports/java/jdk14/work/j2se/=
make/java'
> gmake[1]: *** [all] Error 1
> gmake[1]: Leaving directory `/datmp/ports/usr/ports/java/jdk14/work/j2se/=
make'
> gmake: *** [j2se-build] Error 2
> *** Error code 2
>=20
> Stop in /usr/ports/java/jdk14.
>=20
> Any hints on how to get it to finish greatly appreciated.

Remove the corrupted file -- the build process should regenerate it
automatically.

Make sure that the linux proc filesystem is mounted:

    # mount -t linprocfs linprocfs /compat/linux/proc

Restart the build.

Failing that, do a 'make clean' and try building from scratch with
linprocfs mounted.

This bug has bitten quite a few people: that's why the port Makefile
does explicitly print out instructions to mount linprocfs nowadays.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--9amGYk9869ThD9tj
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBOcrUiD657aJF7eIRArVIAKCFNFtl0zbt+jEOvxM6rgiG0XL8SACfR5xZ
IhoOVFfWagH7QpAbxm/Irmc=
=vqXK
-----END PGP SIGNATURE-----

--9amGYk9869ThD9tj--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040904140156.GA16402>