Date: Fri, 31 Oct 2003 17:55:46 +0100 From: John Angelmo <john@veidit.net> To: Scott Long <scottl@freebsd.org> Cc: kris@obsecurity.org Subject: Re: __fpclassifyd problem Message-ID: <3FA29412.60707@veidit.net> In-Reply-To: <3FA208CF.9070001@freebsd.org> References: <20031029211951.GA12398@rot13.obsecurity.org> <20031029152202.C7702@pooker.samsco.home> <20031029154141.T7702@pooker.samsco.home> <20031030.234813.72025638.imp@bsdimp.com> <3FA208CF.9070001@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > 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 But still after importing e_scalb.c or e_scalbf.c and rebuilding gives me this: cc -fpic -DPIC -O -pipe -march=pentium3 -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c i387_s_tan.S -o i387_s_tan.So building shared library libm.so.2 e_scalb.So: In function `__ieee754_scalbf': e_scalb.So(.text+0x0): multiple definition of `__ieee754_scalbf' e_scalbf.So(.text+0x0): first defined here *** Error code 1 /John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FA29412.60707>