This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html
- From: Alexandre Oliva <aoliva at cygnus dot com>
- Date: 20 May 2000 13:39:25 -0300
- Cc: gcc-patches at gcc dot gnu dot org, "H. J. Lu" <hjl at valinux dot com>
- Organization: Cygnus Solutions, a Red Hat Company
- References: <20000520093135A.mitchell@codesourcery.com>
On May 20, 2000, Mark Mitchell <mark@codesourcery.com> wrote:
> Please describe the situation in complete detail, and explain why you
> need to do this.
The problem is that GCC has used pathnames relative to its
installation directory, such as
${libdir}/gcc-lib/i686-pc-linux-gnu/2.96/../../../../i686-pc-linux-gnu/
when searching for already-installed libraries.
Even though this is often a non-issue for embedded cross compilers,
because they often use newlib, building it in the same build tree,
when building a hosted (?) cross compiler, that uses a pre-installed
glibc, GCC won't be able to find the installed libraries before the
installation directory is created.
Another alternative to solve this problem, that occurs to me only now,
is to append -B${prefix}/${target}/ to the GCC invocation line. Then,
it will find already-installed target libraries regardless of the
existence of the installation directory, and we won't need to
introduce this long configure option. H.J., how does this sound to
you?
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me