Re: Why relink the library during make install?

[Ralph Corderoy]

Hi Russ,

> >    configure --prefix=/A
> >    make
> >    make install prefix=/B
>
> > cannot expect that auxiliary files (in lib, share, doc, etc) will be
> > found. The "make" process has no chance to put the pathnames /B/lib,
> > /B/share etc. into the executables and libraries because it doesn't
> > know about /B at that moment. In most cases, the installed package
> > will not run.
>
> This works for every other GNU package that I've built, it is required
> by the GNU Coding Standards, and it worked for the previous version of
> gettext.  I don't understand why you're breaking this.

GNU Stow, which is one symlink-creating post-processor, uses this
technique to install under /usr/local/stow/package-ver.sion and then
symlink the contents into /usr/local/{bin,lib,share,etc}.

After years of using this technique without a problem I did stumble
across another package that didn't like it the other day, gphoto2 IIRC.

Cheers,


Ralph.