From: Tim Wilkinson (tim@transvirtual.com)
Date: Thu Sep 10 1998 - 20:16:32 EDT
Nope still don't get it.
Option 1: You link /opt/kaffe/install/bin/kaffe -> /usr/bin/kaffe
Here it'll all work since kaffe is a script with /opt/kaffe/install/Kaffe
configued into it.
Option 2: You link /op/kaffe/install/bin/javac -> /usr/bin/javac (or some
other script)
here it'll work too .. actually it's rather like Option (1).
Give me reason why this is necessary. I suppose if you install it somewhere
then copy the whole damn
lot somewhere else it'll help - but to be honest things breaking at that
point seems perfectly reasonable.
Tim
Godmar Back wrote:
> >
> > Okay, what are these bizzar shell scripts about at the top of each of
> > the scripts/... files? Is their only purpose to find where the 'kaffe'
> > binary is and run it directly (so assuming it's not in the path?). If
> > it is, why don't we just fix these scripts during configure? Or am I
> > missing something?
> >
>
> I think finding it even when it's not in the path is one thing.
> The other thing is that you'd be able to symlink to it, like if you
> configure kaffe to install and live in /opt/kaffe/install, you can symlink
> to /usr/bin/kaffe.
>
> - Godmar
-- Tim Wilkinson Tel: +1 510 704 1660 Transvirtual Technologies, Inc., Fax: +1 510 704 1893 Berkeley, CA, USA. Email: tim@transvirtual.com
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:56:57 EDT