On Tue, Mar 14, 2000 at 07:09:16PM +0100, Simon Budig [EMAIL PROTECTED] wrote:
Using "env" is much more portable than always using "/usr/bin/python".
Determining the location of the binary at compile time is a good
compromise IMHO. So where is our autoconf/automake guru? :-)
That's not the
On Tue, Mar 14, 2000 at 06:12:39PM +0100, Simon Budig [EMAIL PROTECTED] wrote:
This might work for python, but it will not work for perl. It will find
the first perl in your path (which is often perl4), not the perl gimp
was configured with.
Are there really multiple different
Marc Lehmann ([EMAIL PROTECTED]) wrote:
On Mon, Mar 06, 2000 at 04:16:04PM +0100, Simon Budig [EMAIL PROTECTED]
wrote:
There is a better way.
This might work for python, but it will not work for perl. It will find
the first perl in your path (which is often perl4), not the perl gimp
was
On Tue, 14 Mar 2000, Simon Budig [EMAIL PROTECTED] wrote:
Marc Lehmann ([EMAIL PROTECTED]) wrote:
This might work for python, but it will not work for perl. It will find
the first perl in your path (which is often perl4), not the perl gimp
was configured with.
Are there really multiple
Raphael Quinet ([EMAIL PROTECTED]) wrote:
Are there really multiple different executables named "perl" (not "perl4" or
so!) in your path? So when you work in your shell you always execute
version 4 of perl, when you invoke "perl"?
I suppose that Marc meant that the person running a
