Re: diablo-jdk with FreeBSD-8.0

2009-08-03 Thread b. f.
On 8/3/09, Mel Flynn  wrote:
> On Friday 31 July 2009 13:57:34 b. f. wrote:
>> "Stephen Montgomery-Smith"  wrote:
>> >I am running a very recent amd64 version of FreeBSD-8.0.  diablo-jdk is
>> >no longer working.  I am guessing it is the bumped shared library
>> >versions (because I did do "make delete-old-libs" as part of my
>> >installation).
>>
>> Yes, this came up earlier.  libmap.conf(5) is your friend here, until
>> an update.  Or you can try building java/openjdk6, but that takes some
>> time and resources.
>
> Have you tried it? openjdk requires a native jdk to build, doesn't accept
> the
> linux ones, so chicken and egg.

Obviously not. :)  I was mentioning it only as a possibility that I
hadn't explored, and that the OP may wish to look into -- I should
have made that clear.  I see now that it (unfortunately) requires one
of a number of bootstrap JVMs that are now broken , as you say. Thanks
for pointing that out, and for mentioning the problems below with some
of the other JVMs.

> Trying to build java/jdk16 with a linux one also does not work, because of
> unsafe functions in the make program that it builds as one of the first
> things. Also, the linux jdk6 requires one to dig into archives as the port
> is
> at update 10 while Sun is at update 14.
> So for the time being, libmap.conf is the only working solution and to make
> it
> more specific, it needs libz.so.4. The error message java generates points
> no
> where near libz, so kudos to whoever found out it's that library.

Perhaps not, but ldd(1) and a number of other tools will show that
${WRKSRC}/bin/unpack200 expects to find this library, and also show
what other libraries the precompiled binaries need.  In any event, it
was helpful of Carlos to post his notes -- thanks.

b.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: diablo-jdk with FreeBSD-8.0

2009-08-03 Thread Mel Flynn
On Friday 31 July 2009 13:57:34 b. f. wrote:
> "Stephen Montgomery-Smith"  wrote:
> >I am running a very recent amd64 version of FreeBSD-8.0.  diablo-jdk is
> >no longer working.  I am guessing it is the bumped shared library
> >versions (because I did do "make delete-old-libs" as part of my
> >installation).
>
> Yes, this came up earlier.  libmap.conf(5) is your friend here, until
> an update.  Or you can try building java/openjdk6, but that takes some
> time and resources.

Have you tried it? openjdk requires a native jdk to build, doesn't accept the 
linux ones, so chicken and egg.
Trying to build java/jdk16 with a linux one also does not work, because of 
unsafe functions in the make program that it builds as one of the first 
things. Also, the linux jdk6 requires one to dig into archives as the port is 
at update 10 while Sun is at update 14.
So for the time being, libmap.conf is the only working solution and to make it 
more specific, it needs libz.so.4. The error message java generates points no 
where near libz, so kudos to whoever found out it's that library.
-- 
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: diablo-jdk with FreeBSD-8.0

2009-07-31 Thread Stephen Montgomery-Smith

Carlos A. M. dos Santos wrote:

On Fri, Jul 31, 2009 at 6:21 PM, Stephen
Montgomery-Smith wrote:

I am running a very recent amd64 version of FreeBSD-8.0.  diablo-jdk is no
longer working.  I am guessing it is the bumped shared library versions
(because I did do "make delete-old-libs" as part of my installation).


I was bitten by this snake a few hours ago. Solved it by creating a
/etc/libmap.conf with

 # echo libz.so.4 libz.so.5 > /etc/libmap.conf



Thank you.  That worked very well.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: diablo-jdk with FreeBSD-8.0

2009-07-31 Thread Carlos A. M. dos Santos
On Fri, Jul 31, 2009 at 6:21 PM, Stephen
Montgomery-Smith wrote:
> I am running a very recent amd64 version of FreeBSD-8.0.  diablo-jdk is no
> longer working.  I am guessing it is the bumped shared library versions
> (because I did do "make delete-old-libs" as part of my installation).

I was bitten by this snake a few hours ago. Solved it by creating a
/etc/libmap.conf with

 # echo libz.so.4 libz.so.5 > /etc/libmap.conf

That allowed it to run well enough to bootstrap the building of jdk 1.5:

 # cd /usr/ports/java/jdk15
 # make install

Then I deleted Diablo with

 # pkg_delete diablo\*

I built jdk 1.5 because I need it, but I guess you can build jdk 1.6.

> My guess is that the problem will be solved when a version 8.0 of diablo-jdk
> comes out, and I was inquiring about an ETA.

So I guess.

-- 
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: diablo-jdk with FreeBSD-8.0

2009-07-31 Thread b. f.
"Stephen Montgomery-Smith"  wrote:

>I am running a very recent amd64 version of FreeBSD-8.0.  diablo-jdk is
>no longer working.  I am guessing it is the bumped shared library
>versions (because I did do "make delete-old-libs" as part of my
>installation).

Yes, this came up earlier.  libmap.conf(5) is your friend here, until
an update.  Or you can try building java/openjdk6, but that takes some
time and resources.

>My guess is that the problem will be solved when a version 8.0 of
>diablo-jdk comes out, and I was inquiring about an ETA.

I think you are right, but I have seen no announcement.  Did you ask
on freebsd-java@, or email gle...@?

b.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"