This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Build using --with-gmp and shared libraries

From: François-Xavier Coudert <fxcoudert at gmail dot com>
To: Albert Chin <gcc at mlists dot thewrittenword dot com>
Cc: GCC Development <gcc at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>, GNU GFortran <fortran at gcc dot gnu dot org>
Date: Fri, 4 Nov 2005 13:32:06 +0100
Subject: Re: Build using --with-gmp and shared libraries
References: <19c433eb0511040110y707ba369x750ce40454c44b6c@mail.gmail.com> <20051104122114.GB52284@mail1.thewrittenword.com>

>> Here is a patch to fix PR libfortran/21547: when building with
>> --with-gmp=/foo/bar and a shared libgmp in /foo/bar, the
>> $(RPATH_ENVVAR) variable (usually LD_LIBRARY_PATH) is not set
>> correctly when using the freshly built gfortran to build libgfortran.
>> The same thing happens for the gfortran testsuite, and the fix is also
>> included in this patch.
>
> Why wouldn't mpfr have the same problem?

Sorry not to mention that. It can (although it usually doesn't,
because the default for libmpfr is to build only a static library),
and this is fix by the same patch. In fact, in the gcc configury, all
occurences of GMPLIBS, GMPINCS always take care of both gmp and mpfr.
I followed this lead, and GMPLIBSDIR points to the directories where
gmp and mpfr are installed, if different. All this is done in the
toplevel configure.

FX

Follow-Ups:
- Re: Build using --with-gmp and shared libraries
  - From: Steve Kargl

References:
- Build using --with-gmp and shared libraries
  - From: François-Xavier Coudert
- Re: Build using --with-gmp and shared libraries
  - From: Albert Chin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]