This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH]: fix the --with-mpfr-dir=PATH configure flag
- From: Matt Fago <fago at earthlink dot net>
- To: Kaveh R. GHAZI <ghazi at caip dot rutgers dot edu>
- Cc: gcc-patches at gcc dot gnu dot org, dj at redhat dot com
- Date: Fri, 17 Nov 2006 17:23:00 -0700
- Subject: Re: [PATCH]: fix the --with-mpfr-dir=PATH configure flag
- References: <Pine.GSO.firstname.lastname@example.org>
On Nov 17, 2006, at 4:22 PM, Kaveh R. GHAZI wrote:
Finding mpfr in an installation directory via --with-mpfr=PATH
obviously works okay, or we'd all be hosed and would have noticed. :-)
It does not work if mpfr is in PATH/lib64. Am I the only one on
installed a 64-bit MPFR, or is RHEL odd in how it organizes its
So we need to search .libs, _libs and "." for libmpfr.a. The patch
does this. The analogous --with-gmp-dir=PATH already checks these
because I suspect gmp started using libtool earlier.
It would be really great if --with-mpfr and --with-gmp could also be
check lib64. If not for 4.1, then perhaps for 4.2 and trunk. By the
way, I seem to
recall that 64-bit Ubuntu (?) uses lib32 and lib; this seems to
lib32 as well.
Would it be problematic if the libraries were installed in both lib
and lib64, as 32
and 64 bits, respectively? I suppose if this is the case both paths
should be used
-- the linker is smart enough to pick the correct one (gnu ld is
Thank you for your help!