On Sun, 20 Jan 2008, [ISO-8859-1] Manuel López-Ibáñez wrote:
> Hi,
>
> I am seeing these kind of failures in a pristine GCC checkout with mpfr-2.3.0
>
> FAIL: gcc.dg/torture/builtin-math-2.c -O0 (test for excess errors)
> Excess errors:
> /home/manuel/131656/build/gcc/cc1: symbol lookup error:
> /home/manuel/131656/build/gcc/cc1: undefined symbol: mpfr_remquo
>
> FAIL: gcc.dg/torture/builtin-math-4.c -Os (test for excess errors)
> Excess errors:
> /home/manuel/131656/build/gcc/cc1: symbol lookup error:
> /home/manuel/131656/build/gcc/cc1: undefined symbol: mpfr_j0
>
> PASS: gcc.dg/torture/builtin-pow-mpfr-1.c -O0 (test for excess errors)
> FAIL: gcc.dg/torture/builtin-pow-mpfr-1.c -O0 scan-tree-dump original "pow"
>
> Anyone seeing the same or know what might be the reason?
> Cheers,
> Manuel.
What does "gcc -v foo.c" say about GMP and MPFR?
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.
The file foo.c can be empty, you have to mention something.c in order to
invoke cc1 which has the info.
Thanks,
--Kaveh
--
Kaveh R. Ghazi [EMAIL PROTECTED]
