« Return to Thread: Configuration problem: not recognizing MPFR

Re: Configuration problem: not recognizing MPFR

by Kai Ruottu-3 :: Rate this Message:

Reply to Author | View in Thread

Damian Rouson wrote:

 > Thanks.  Apparently the mpfr.h header file is in /usr/local/include.
 > How do I point gcc to this location?  I've tried each of the following
 > flags on the configure command:
 >
 > --with-mpfr=/usr/local

By the :

http://gcc.gnu.org/install/configure.html

this should be the right one, to point to where the 'include' and 'lib'
with the gmp and mpfr headers and libraries are... I haven't ever tried
or required these options, after installation they should be found
automatically, ie the installed GCC trying to compile the new sources
should find them...

At least the '/usr/local/include' should be searched before the
'/usr/include' in every GCC, this being the LOCAL_INCLUDE_DIR.

But the GCC_INCLUDE_DIR may become before this and in it being
some old "fixed" 'mpfr.h':(  The :

   $prefix/lib/gcc/$target/$gcc-version/include-fixed

is the current install place for the fixed headers, the :

   $prefix/lib/gcc/$target/$gcc-version/include

being the old combined place for GCC's own and fixed target headers. The
GCC in Fedora8 searches the LOCAL_INCLUDE_DIR earlier, it's 'cpp -v'
gives :

----- clip -----
gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
  /usr/libexec/gcc/i386-redhat-linux/4.1.2/cc1 -E -quiet -v - -mtune=generic
#include "..." search starts here:
#include <...> search starts here:
  /usr/local/include
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include
  /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../i386-redhat-linux/include
  /usr/include
End of search list.
^C
----- clip -----

but all kind of local/custom orders may exist, it isn't any rocket
science to tinker with the 'gcc/cppdefault.*' files... Whether MacOS
has some "custom" GCC with a tinkered search order, for that I have no
clue. In any case the options in 'configure' should cause the pointed
'<value>/include' being searched before the built-in ones...

Of course you should use the same value for the 'gmp' too... It is weird
that its right header was found despite of the wrong value in configure.


 « Return to Thread: Configuration problem: not recognizing MPFR