I've built the mpfr library from source, using MinGW in the msys shell. I've
tried mpfr versions 2.3.0, 2.3.1-rc1, and 2.3.1-rc2. The problem persists
with all three - but I don't believe it's an mpfr problem anyway.
I have 2 versions of mingw (both gcc-3.4.5). One is built from available
binaries - and works just fine. Let's refer to that compiler as
Then, in order to create a g77 that works on this Vista box, I built a
second compiler from source. Let's refer to it as "my-mingw". It seems
basically serviceable so far, but there's at least one problem:
When using my-mingw against that mpfr library, none of the mpfr library
functions that take/return a 'long long' can be used (I get, eg 'undefined
reference to `_mpfr_set_uj').
When using their-mingw against that very same library, there's no problem.
This is *irrespective* of whether the library was built using my-mingw, or
whether it was built using their-mingw.
All other mpfr functions that I've tested (and I've tested nearly all of
them) are accessible using either compiler. I suspect the 'long double'
functions might also be inaccessible, but that is untested.
Surprisingly, no matter which compiler I use to build mpfr, *all* tests
pass - even the tests relating to the 'long long' functions. I find this
particularly surprising, since I would have thought those tests would fail
with my-mingw (because my-mingw is incapable of resolving symbols such as
'mpfr_set_uj' - which is one of the functions tested in the test suite).
Any advice on how to proceed with this ?
----- Original Message -----
From: "Sisyphus" <sisyphus1@...>
> When using my-mingw against that mpfr library, none of the mpfr library
> functions that take/return a 'long long' can be used (I get, eg 'undefined
> reference to `_mpfr_set_uj').
> When using their-mingw against that very same library, there's no problem.
I've since found that everything works fine for *both* compilers if
inttypes.h is #included before mpfr.h - which is the way it should be done,