Proc::FastSpawn test failure

[Darin McBride]

On Friday November 22 2013 5:34:55 PM Marc Lehmann wrote:
> On Fri, Nov 22, 2013 at 09:13:41AM -0700, Darin McBride 
<darin.mcbride at shaw.ca> wrote:
> > The problem is that this doesn't work when using a relocatable perl if
> > it's
> > not located where it's compiled against.  Unfortunately, $^X works better
> > then.
> 
> That sounds like a bug in your perl distribution then - $Config{perlpath}
> is not supposed to be empty, relocated or not (on relocatable perl
> installs, this value is updated according to the installation path). You
> should report this to whoever maintains your perl distribution.
> 
> $^X is not portable (and very unreliable). It's up to your perl
> distribution to get the configuration right (and not the poor modules that
> have to run with broken installations :).
> 
> (I wonder which distro it is - both strawberry and activestate perl for
> example are relocatable and get this right).

It's not a distribution per se.  This is Linux.  Code compiled directly from 
source, but I'm putting it all together (including Coro, AE, etc.) in the 
temporary directory so I can tar it up and install it on the target machines 
later.

I give Configure a "-Dprefix=/real/destination/path/here" and then when it comes 
time to install, since I need everything separated out for a real install to a 
different machine, I do "make install DESTDIR=/home/dmcbride/tmp/perl" and 
then, once all 165+ modules are built to that path, I can cd into DESTDIR and 
tar everything up to be untarred at the root of the destination system.

But when I run /home/dmcbride/tmp/perl/real/destination/path/here/bin/perl -
MConfig -E 'say $Config{perlpath}', I get /real/destination/path/here/bin/perl - 
which is where everything will eventually go, but isn't yet.