This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [configury patch] don't add 'mpfr' to --with-mpfr-dir
Quoting Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>:
> Paul Brook <paul@codesourcery.com> writes:
>
> > > 2005-06-04 Tobias Schl"uter <tobias.schlueter@physik.uni-muenchen.de>
> > >
> > > * configure.in: Don't add another '/mpfr' to the directory given
> > > in --with-mpfr-dir.
> > > * configure: Regenerate.
> >
> > Ok.
> >
> > This looks like is a copy/paste error from when we assumed a combined
> gmp+mpfr
> > build.
>
> one could argue the other way round: the /mpfr infix is missing from
> gmplibs here. According to the installation docs
>
> --with-gmp=pathname
> --with-mpfr=pathname
> --with-gmp-dir=pathname
> --with-mpfr-dir=pathname
> If you don't have GMP (the GNU Multiple Precision library) and the MPFR
> Libraries installed in a standard location and you want to build the
> Fortran front-end, you can explicitly specify the directory where they
> are installed (`--with-gmp=gmpinstalldir',
> `--with-mpfr=mpfrinstalldir') or where you built them without
> installing (`--with-gmp-dir=gmpbuilddir',
> `--with-mpfr-dir=gmpbuilddir').
>
> i.e. the arg to --with-mpfr-dir is supposed to be gmpbuilddir. With this
> patch and gmp build with --enable-mpfr, you need to know that mpfr is built
> inside an mpfr subdir. On the other hand, omitting mpfr is correct if you
> have a separate build of e.g. mpfr 2.1.1.
This looks like the documentation is out of date or at least misleading. If
your mpfr is the one built together with gmp, --with-mpfr-dir is not needed.
Also, the way --with-mpfr-dir worked made it impossible to use a standalone mpfr
that wasn't installed, effectively rendering that option useless.
> It's probably high time for including a copy of gmp and mpfr in GCC CVS.
It's been for a while. When I asked Paul Brook about this some time ago on IRC,
he said that someone competent -- IIRC rth -- had tried and failed, so I didn't
even try :-)
- Tobi