Date: Tue, 7 Aug 2007 15:39:30 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: RW <fbsd06@mlists.homeunix.com> Cc: ports@FreeBSD.org, glewis@FreeBSD.org, Doug Barton <dougb@FreeBSD.org> Subject: Re: Portmaster and Portmanager problem with jdk15 Message-ID: <20070807153205.M12870@thor.farley.org> In-Reply-To: <20070807205138.6c5759d6@gumby.homeunix.com.> References: <20070807205138.6c5759d6@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 7 Aug 2007, RW wrote:
> Both Portmaster and Portmanager (I haven't tried Portupgrade) install
> java/linux-sun-jdk15 on an upgrade of java/jdk15. If I upgrade jdk15
> manually it isn't built, so it must be done by the tools.
>
> The way the jdk15 makefile works is that it looks for the location of
> an existing jdk installation for bootstrapping and sets
> BOOTSTRAPJDKDIR accordingly. We then have:
>
> # if no valid jdk found, set dependency
> .if !defined(BOOTSTRAPJDKDIR)
> BOOTSTRAPJDKDIR?=${LOCALBASE}/linux-sun-jdk${SUN_LINUX_JDK_VERSION}
> .endif
> BUILD_DEPENDS+=${BOOTSTRAPJDKDIR}/bin/javac:${PORTSDIR}/java/linux-sun-jdk15
>
>
> I don't know why this causes the build-tools to install
> linux-sun-jdk15, but simply moving the BUILD_DEPENDS+= line inside the
> if-endif block, seems to fix the problem. That line is only needed if
> no jdk is present.
The port now depends on the Diablo JDK, but that exposed BUILD_DEPENDS
line still brings in the diablo-jdk15 port even if a native JDK is
already available.
It would be nice to use an installed java/jdk15 port to build itself.
Sean
--
scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070807153205.M12870>