[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#36580



Hi,

I'm trying to track down the above bug reported against my package,
which was caused (among other things) by the failure of the binary to
load against a more recent version of libc.  The particular culprit
appears to be the __setfpucw function:

$yorick
yorick: error in loading shared libraries: yorick: undefined symbol:
__setfpucw

This puzzles me somewhat, because the libc.so.6 from version 2.1.1-1
looks like it includes a __setfpucw function.  Why does the dynamic
loader refuse to make this link?  Is this a bug or change in libc?

I did notice that the fpu_control.h header file in libc6-dev no longer
declares __setfpucw.  I will switch to the _FPU_SETCW macro for the
future, but it would be less painful if the __setfpucw that seems to
be present would link to the older executable.  I presume the function
is retained in the library for backwards compatibility, so the fact
that it doesn't seem to work for that purpose is annoying; you may as
well drop it entirely...

Is there a chance that the _FPU_SETCW macro with its associated bit
macros would be portable across every platform where GNU libc can be
built?

Thanks very much for any help you can provide,

Dave


Reply to: