Re: Another libtool problem

[Ralf Wildenhues]

Hi Peter,

* Peter Breitenlohner wrote on Sun, May 07, 2006 at 05:53:30PM CEST:
> 
> I always knew that "make install" with libtool needs write access in the
> build tree (relinking), but only today I encoutered a situation where this
> was a serious problem.
> 
> As usual I did "make all" as non-root, followed by "make install" as root,
> but this time on an nfs-mounted filesystem. Due to root-squashing this
> failed.

Yep.  This is a problem.

> I think there is a general rule that if at all possible
> (1) "make" should not modify the source tree and

Yes, but only if all files that are created by the autotools
(configure, Makefile.in, ...) and for example info files, are
up to date.

> (2) "make install" should not modify the build tree
> because (1) the source tree might be read-only and (2) the build tree might
> be read-only for root.

Yes.

> Is there a way to address that problem? (-no-fast-install?)

There's a TODO list item to make this work everywhere with
--enable-fast-install (which is the default).  Until then,
there is the workaround of doing a
  make install DESTDIR=/tmp/dest

as normal user, and then as root, copying that tree to its final
location, then a
  libtool --mode=finish $libdir..

(listing all library installation directories).

Hope that helps.

Cheers,
Ralf