in reply to Re^3: Relocatable Perl 5.10.0 on Solaris
in thread Relocatable Perl 5.10.0 on Solaris

Alas, no - I checked using a hex editor, and both binaries definitely contain .../../lib. So the problem appears to be a runtime one, not at configure/build.

This is why I was hoping it was a library problem :(.

Regards,
CK.
  • Comment on Re^4: Relocatable Perl 5.10.0 on Solaris

Replies are listed 'Best First'.
Re^5: Relocatable Perl 5.10.0 on Solaris
by Corion (Patriarch) on May 16, 2008 at 10:18 UTC

    Maybe look at what $^X is on the Solaris machine - if it always lacks a path, likely the magic that turns ... into <c>/home/ck/myperl/bin/

    cannot use that value as the path.

      I see!

      I just checked $^X on both installs, and indeed, the Solaris binary returns just the executable name ("perl"), whereas on Linux it returns the full path to the executable.

      The previous perl versions on both boxes behave the same way respectively.

      Next question - is this normal? Or have I missed something in the Solaris build that does the $^X magic correctly?

      The inference given in the documentation is that the relocation should 'just work', so assuming I haven't screwed this install up - does it constitute a perl on solaris bug?

      Thanks for everyones help so far,
      CK.