Re: __fpclassifyd problem

From: Scott Long <scottl_at_freebsd.org>
Date: Sun, 19 Oct 2003 15:05:29 -0600
Kris Kennaway wrote:
> On Sun, Oct 19, 2003 at 09:08:25PM +0200, John Angelmo wrote:
> 
>>Hello
>>
>>I'm trying to install java-checkstyle on my 5.1 system, the system is 
>>upto date (p10) but I get this build error:
>>
>>===[root] /usr/ports/java/java-checkstyle # make
>>===>  Extracting for java-checkstyle-3.1
>>
>>>>Checksum OK for checkstyle-src-3.1.tar.gz.
>>
>>===>  Patching for java-checkstyle-3.1
>>===>   java-checkstyle-3.1 depends on file: /usr/local/bin/ant - found
>>===>   java-checkstyle-3.1 depends on file: 
>>/usr/local/diablo-jdk1.3.1/bin/java - found
>>===>  Configuring for java-checkstyle-3.1
>>===>  Building for java-checkstyle-3.1
>>/usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol 
>>"__fpclassifyd"
>>*** Error code 1
>>
>>Stop in /usr/ports/java/java-checkstyle.
>>
>>
>>What I understand is that the problem is that I can have some stale libs 
>>in /usr/lib
>>how can I solve this?
> 
> 
> This symbol is defined in libc.so.5.  One way you can see this problem
> is if you are running a 4.x binary that links to libm.so.2 on a 5.x
> system, because libm has the same version number in 5.x but is not
> binary compatible.  So the 4.x binary links to libc.so.4 and
> libm.so.2, and the latter is actually a 5.x library that expects to
> have __fpclassifyd resolved by linking with libc.so.5.  Is it the case
> on your system that you have old 4.x binaries installed?
> 
> Kris

We need to resolve this before 5.2 in some fashion.  It looks like the
easiest thing to do is bump libm.  Is this advisable?

Scott
Received on Sun Oct 19 2003 - 12:05:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:25 UTC