[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool and AFS - chronic problem
From: |
Ralf Wildenhues |
Subject: |
Re: libtool and AFS - chronic problem |
Date: |
Tue, 2 Aug 2005 10:18:52 +0200 |
User-agent: |
Mutt/1.4.1i |
Hi Jeff,
Sorry for the late answer.
* Jeff Blaine wrote on Tue, Jul 19, 2005 at 09:08:10PM CEST:
>
> The situation below represents how we build all of our
> applications. After the make install (if it would succeed...),
> we "release" the area /afs/rcf/system/dest/lin24v2/local/myapp/010
> to some of our machines. They have a symlink '/usr/rcf' which
> points to this "beta" release area.
So /usr/rcf is the real prefix.
> The software is tested. When it is found to be legit, we release
> that area to our production machines which have a '/usr/rcf'
> symlink pointing to the 'production' release area.
>
> ./configure --prefix=/usr/rcf
> make
> make install prefix=/afs/rcf/system/dest/lin24v2/local/myapp/010
> ...
> Cannot install foo to a directory not ending in /usr/rcf/whatever-here
Can you do
make install DESTDIR=/afs/rcf/system/dest/lin24v2/local/myapp/010
(which may need another subtree usr/rcf there, which you could move
later on, however)
and then on the production machines once do a
libtool --mode=finish /usr/rcf/lib
? Changing prefix is not the right thing to do here.
I do very much agree that this is a nuisance and a problem, but it is
not easily solved without breaking other stuff, esp. relinking when it
proves necessary. See for example [1] for some more (but by far not
all) information on this. We need to find a better way to do this.
Cheers,
Ralf
[1] http://lists.gnu.org/archive/html/libtool-patches/2005-06/msg00161.html
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: libtool and AFS - chronic problem,
Ralf Wildenhues <=