>> cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
>> Date: Wed, 02 Aug 2000 13:58:49 -0600
>> From: Tom Christiansen <[EMAIL PROTECTED]>
>> X-UIDL: ab65e2a94d9487f65465be74c21fe152
>>
>> >> Insofar as you can pretend to make a good guess at that--perhaps.
>>
>> >On Linux: /proc/self
>> Insofar as you can pretend to make a good guess at that--perhaps.
>On Linux: /proc/self/exe
What good does that do you? You can't go ../foo with that. It doesn't
tell you the real name, just the dev,ino. And it's a nonportable answer
that cannot be reproduced everywhere that Perl runs.
--
>Yes, but that seems a bit more tractable - surely we could fiddle with
>@INC based on the location of the perl interpreter?
Insofar as you can pretend to make a good guess at that--perhaps.
--tom
On Wed, Aug 02, 2000 at 03:09:19PM -0400, John Tobey wrote:
> > Solaris 7 onwards has a nice linker feature called $ORIGIN. This allows
> > the location of run-time linker dependencies to be specified relative to
> > the location of the executable.
>
> Both Windows and Linux can swing this, too.
> cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> Date: Wed, 02 Aug 2000 13:58:49 -0600
> From: Tom Christiansen <[EMAIL PROTECTED]>
> X-UIDL: ab65e2a94d9487f65465be74c21fe152
>
> >> Insofar as you can pretend to make a good guess at that--perhaps.
>
> >On Linux: /proc/self/exe
>
Tom! Good to see you.
Tom Christiansen <[EMAIL PROTECTED]> wrote:
> >Yes, but that seems a bit more tractable - surely we could fiddle with
> >@INC based on the location of the perl interpreter?
>
> Insofar as you can pretend to make a good guess at that--perhaps.
On Linux: /proc/self/exe
--
John Tobey wrote:
> Both Windows and Linux can swing this, too. I believe linux (GNU
> Libc, to be precise) uses $ORIGIN in a Solaris-compatible way.
So I've just been told by our linker expert. Nice to have it confirmed
though.
--
Alan Burlison
Graham Barr wrote:
> It is not just libraries, but also the perl @INC that needs to
> be dynamic
Yes, but that seems a bit more tractable - surely we could fiddle with
@INC based on the location of the perl interpreter?
--
Alan Burlison
Solaris Kernel Development, Sun Microsystems
[EMAIL PROTECTED] wrote:
> Graham Barr wrote:
>
> > Well I think it is worth an RFC (not that I have time to write one just now)
> > If only to suggest some sample implementations. Do other languages do it ?
> > If so how ?
>
> Ok, Ok, I'll do a RFC then... :-)
>
> Actually the only thing aff
Graham Barr wrote:
> Well I think it is worth an RFC (not that I have time to write one just now)
> If only to suggest some sample implementations. Do other languages do it ?
> If so how ?
Ok, Ok, I'll do a RFC then... :-)
Actually the only thing affected by LD_LIBRARY_PATH is libperl.so, as
On Wed, 2 Aug 2000, Ken Fox wrote:
> Tim Bunce wrote:
> > > Alan Burlison wrote:
> > > > the ability to relocate or install perl in some place other than the
> > > > initial install location without everything breaking.
>
> > Volunteers?
>
> XEmacs does this very well. Can an RFC just say "do w
Tim Bunce wrote:
> > Alan Burlison wrote:
> > > the ability to relocate or install perl in some place other than the
> > > initial install location without everything breaking.
> Volunteers?
XEmacs does this very well. Can an RFC just say "do what xemacs does" or
does it have to be standalone?
On Wed, Aug 02, 2000 at 02:58:37PM +0100, Graham Barr wrote:
> On Wed, Aug 02, 2000 at 02:56:54PM +0100, Alan Burlison wrote:
> > I don't think it is worth generating a RFE for this, but I'd like to see
> > the ability to relocate or install perl in some place other than the
> > initial install lo
At 02:58 PM 8/2/00 +0100, Graham Barr wrote:
>On Wed, Aug 02, 2000 at 02:56:54PM +0100, Alan Burlison wrote:
> > I don't think it is worth generating a RFE for this, but I'd like to see
> > the ability to relocate or install perl in some place other than the
> > initial install location without ev
On Wed, Aug 02, 2000 at 02:56:54PM +0100, Alan Burlison wrote:
> I don't think it is worth generating a RFE for this, but I'd like to see
> the ability to relocate or install perl in some place other than the
> initial install location without everything breaking. This will require
> cleverness i
I don't think it is worth generating a RFE for this, but I'd like to see
the ability to relocate or install perl in some place other than the
initial install location without everything breaking. This will require
cleverness in the manipulation of the search paths for both perl modules
and shared
16 matches
Mail list logo
