> I was about to fill a bug report on this, but I thought I asked first.
>
> In r-base 0.63.2/src/unix/system.c there are two references to the C function
> setfpucw
>
> line 545:
>
> #ifdef linux
> __setfpucw(_FPU_IEEE);
> #endif
>
> line 626:
>
> #ifdef linux
> __setfpucw(_FPU_DEFAULT);
> #endif
>
> There is an obvious problem as to why this package could not be built.
> The final executable get compiled and linked with g77, while this function is
> available ONLY in libc (version that I have is 2.0.100).
> Compilation was fine, but linking failed with an unresolved symbol in
> __setfpucw.
>
> I tried commenting out this line, and guess what, it succeeded. Then, I
> thought "yeah, but all tests will fail". Guess again, all tests were
> successful.
> Then I considered that this command was not really that needed after all and
> proceeded to building the package, which was also successful.
>
> So what do you say? I have also CC'd to the package maintainer. Is this a bug
> to fill a report, or is this specific to my specific setup (what is the status
> on other platforms reg this package?)
Hmmm, don't remember such case ... could you try -msoft-float ?
Different libm packages for libc-2.0 and libc-2.1 ??? Please grep also the
kernel source for '__setfpucw'. Possible it is #difdef __KERNEL__ ... #endif
Greetings,
Hartmut
