On 20/01/2008, Kaveh R. GHAZI <[EMAIL PROTECTED]> wrote:
>
> What does "gcc -v foo.c" say about GMP and MPFR?
[EMAIL PROTECTED]:~/131656/build/gcc$ ./xgcc -v -c -B . foo.c
Reading specs from ./specs
Target: x86_64-unknown-linux-gnu
Configured with: /home/manuel/src/trunk/configure
--prefix=/home/manuel/./131656/install --enable-languages=all
--enable-decimal-float --with-mpfr=/opt/cfarm/mpfr-2.3.0/
Thread model: posix
gcc version 4.3.0 20080119 (experimental) [trunk revision 131656] (GCC)
[snip]
GNU C (GCC) version 4.3.0 20080119 (experimental) [trunk revision
131656] (x86_64-unknown-linux-gnu)
compiled by GNU C version 4.3.0 20080119 (experimental) [trunk
revision 131656], GMP version 4.2.1, MPFR version 2.3.0.
warning: MPFR header version 2.3.0 differs from library version 2.2.0.
> You should always report this when asking about mpfr related issues in
> GCC. Sometimes the version you think you compiled into GCC isn't actually
> the one that got used. E.g. I've had reports that turned out to be shared
> libs differ at runtime, or header file mismatches can caused problems.
Exactly this issue. I am not sure how this can happen. My configure
options are above. I am using the Compile Farm.
It works if I use --with-mpfr=/home/ghazi/gcc-testing/lib/422-230/ instead.
Thanks,
Manuel.
