Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Oct 2003 00:01:35 -0700
From:      Scott Long <scottl@freebsd.org>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        kris@obsecurity.org
Subject:   Re: __fpclassifyd problem
Message-ID:  <3FA208CF.9070001@freebsd.org>
In-Reply-To: <20031030.234813.72025638.imp@bsdimp.com>
References:  <20031029211951.GA12398@rot13.obsecurity.org> <20031029152202.C7702@pooker.samsco.home> <20031029154141.T7702@pooker.samsco.home> <20031030.234813.72025638.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote:
> In message: <20031029154141.T7702@pooker.samsco.home>
>             Scott Long <scottl@freebsd.org> writes:
> : To respond to myself, I got ahold of a 4.8 libm.so and made sure that the
> : linker used it.  No change in the problem, and it still hints that the
> : native libc is being linked in.
> 
> You might want to enable debugging of ld.so to confirm.
> 
> Warner
> 
> 
> 

This was already resolved.  Java does a dlopen() on /usr/lib/libc.so.
Rumor has it that this is fixed.

Scott



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