On Thu, 2002-10-10 at 11:51, Stephen Leake wrote:
> I'm confused. Since /foo is hardcoded in the executable, it will
> presumably look in /foo/lib for stuff. But it won't find it; it's
> actually been installed in /fake/place/lib. So how does this work?
OK, now I'm confused. I don't know anything about the Fink packaging
system, so maybe I'm missing something. I thought you wanted to
temporarily install in a location other than the configured location. If
you are going permanently install in a particular location, why not pass
that argument to configure? Is the issue that you want to relocate a
compiled package? That's another story...
> In my experience, Gnu packages must be compiled on each machine,
> precisely because configure hardcodes things like this.
Actually, configure does precious little. It's really up to the
application programmer to decide how a program will deal with paths. I
designed the path logic in maxima to be fully relocatable, i.e., if you
do
./configure --prefix=/tmp/foobar && make && make install
then move all the files in /tmp/foobar to, say, /opt/cas/max, you can
invoke /opt/cas/max/bin/maxima and maxima will still be able to find all
of its input files. It is actually more flexible than that, but you can
see the man page if you want more details.
Of course, it is possible that there are bugs in the path logic that
cause maxima to fail under some conditions when relocated. If you find
such a bug, please report it.
--Jim,
who may have again not understood the question.