On Mar 12, 2000, Geoff Keating <[EMAIL PROTECTED]> wrote:
> 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.
Yup
> 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.
In fact, the user shouldn't have to know that there's magic going on.
It's supposed to be totally transparent. In this particular case, it
wasn't, and that's why I considered it a bug in libtool and fixed it
there.
Since yesterday, I've also been thinking that we should probably
also save PATH for the relink. Otherwise, a change in the PATH could
cause another compiler driver to be used.
Since that's just a matter of adding one more variable to
variables_saved_for_relink, I won't bother to post a revised patch.
Ok to install?
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Enjoy Guaranį
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
