Date: Thu, 26 May 2005 13:20:45 -0700 From: Vizion <vizion@vizion.occoxmail.com> To: freebsd-java@freebsd.org Cc: "Scott I. Remick" <scott@sremick.net> Subject: Re: OS check fails on JDK 1.4 & FreeBSD 5.4R Message-ID: <200505261320.46272.vizion@vizion.occoxmail.com> In-Reply-To: <20050526163424.GA99627@misty.eyesbeyond.com> References: <pan.2005.05.22.18.40.12.945674@sremick.net> <pan.2005.05.26.16.04.34.914669@sremick.net> <20050526163424.GA99627@misty.eyesbeyond.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 26 May 2005 09:34, the author Greg Lewis contributed to the
dialogue on Re: OS check fails on JDK 1.4 & FreeBSD 5.4R:
>On Thu, May 26, 2005 at 12:04:36PM -0400, Scott I. Remick wrote:
>> On Thu, 26 May 2005 09:54:59 -0600, Greg Lewis wrote:
>> > That would be your problem then. The test expects to use -lc_r on 5.x
>> > and higher:
>> >
>> > .if ${OSVERSION} > 500000
>> > LINKIT= -lc_r
>> > .else
>> > LINKIT= -pthread
>> > .endif
>>
>> Isn't that backwards? The default threading library changed from libc_r to
>> libpthread in 5.3
>
>I don't know that its backwards, but it could probably use some help.
>-lc_r became the official way early on in 5.x, but was reverted to
>-pthread after 5.2.1. So it was correct for a time, but is now out of
>date. I suspect that the variable should just go away and ${PTHREAD_LIBS}
>should take its place.
>
>> > However, you should have libc_r on 5.4:
>>
>> ...
>>
>> > So your machine would seem to be somewhat hosed unless you've
>> > deliberately removed libc_r.
>
>[explanation of removing libc_r snipped]
>
>> So I guess I have 2 questions now:
>>
>> 1) If libpthread is the new default, replacing libc_r, and you have to
>> have all things linked to just one or the other, basically libc_r has been
>> depreciated. How come the OS version check for JDK 1.4 wants libc_r if the
>> OS > 5.0?
>
>Because its old (see above).
>
>> 2) What am I to do now, since the purging of all things libc_r when I
>> upgraded to 5.3 is what ultimately fixed my system and has kept things
>> running smoothly ever since?
>
>You can do one of the following:
>
>1. Try the attached patch. This would be my preference since if it works
> I'll try and get it committed.
>2. Turn on SKIP_OS_CHECK and eliminate the test altogether.
What a nice guy you are - I hope for Scott's sake and for you that the patch
works -- we are all grateful and as I intend at some time to follow the same
path (upgrading from 5.3 > 5.4 with (in my case sdk 5) java development
requirements, that it will fix the bug before I experience it :-)
David
--
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505261320.46272.vizion>