This is the mail archive of the binutils@sourceware.cygnus.com mailing list for the binutils project.


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

Re: [PATCH]: ld/Makefile.am


> Date: Sat, 11 Mar 2000 15:33:15 -0800
> From: "H . J . Lu" <hjl@lucon.org>

> > I think the right thing to do is to arrange for the libtool
> > wrapper/relinker script to set GCC_EXEC_PREFIX, COMPILER_PATH and
> > LIBRARY_PATH to the values they had when the wrapper script was
> > created, if the compiler in use is GCC.
...
> I have thought about it. I am not very sure if it is a right thing
> to do. Are GCC_EXEC_PREFIX, COMPILER_PATH and LIBRARY_PATH valid
> environment variables for a user to set? Is that ok for a user to
> set them for the old gcc to use? If they are for users to use, a user
> may set them up for the old gcc used to compile the new ld and gcc.

This sounds like the right idea.  You want to use exactly the same
tools to do the relink as the user specified when doing the original
link.  So you want to use the same options, and the same environment
variables.

All the user has to know is that there's magic going on, but it
behaves just as if the program was built when libtool was originally
called.

-- 
- Geoffrey Keating <geoffk@cygnus.com>

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