-----BEGIN PGP SIGNED MESSAGE-----
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?)
--
Konstantinos Margaritis
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: OxHVGT+MigiwDUbYd1fbkQL2Ts2axLcM
iQEVAwUBNtW1mHLbhkskV78BAQG11gf/W0bmfG7E357hBc/cRd1oOfZUDffeNdH/
wiJ6CZbK/AmyuzhrX6fNHGzv7iyW/9U59Y0UiDtD9kav/qhcZ7sDzg4uc3j87zp1
mgtqgiKUIwK/1QuS1iXL6CbjNRsj7CoyYmnlKtHEWh6PaeLltlw5C6f0Txal2gu+
pP3Y8saOjLf/Y7dK/4zerp+Vbn/2WC35FNOPuFrJcrvhW6Jum06JnU2cHFflIQnb
TuedTSCmX1D/9SNdWPaf1lCjNCJoBEnAhG6QOXVb7FvHHfixsWp4heMHqx90tsdD
VALLS3jj5AfVMBBY+EaA8rNtnGS+pzPDNKGhwMzk00mWwElpg4nzFw==
=EVsC
-----END PGP SIGNATURE-----
