Re: Why relink the library during make install?

[Miles Bader]

Albert Chin <address@hidden> writes:
> > If gettext doesn't follow this, then it should be fixed at once.
> > There are several reasons to use prefix (I favour the usage of DESTDIR
> > though) in conjunction with `make install'.
> 
> Libtool is the one doing the relinking. And, I believe it is correct
> in doing so.

It may be the libtool actually knows what's going on, and is playing
tricks to work around compiler bogosities (on HP-UX or whatever).

As I said in a different thread on this same subject:

   The important point, as I understand it, is that `make install' with a
   different prefix should _not_ embed the new prefix in anything that gets
   installed -- all embedded paths should still use the old prefix.

   I suppose it's OK to violate the letter of the rule as long as you're
   quite sure that the end effect is the same.

So does libtool's relinking do the `right thing' when the two prefixes
are different?

[and also -- am I correct in thinking that the `path embedding' issue is
main problem with relinking at install-time?  Are there other things
that need considering?]

-Miles
-- 
"1971 pickup truck; will trade for guns"