Hi David,
David Abbott wrote:
The only difference I can see is between Perl versions;
Perl 5.8.8 box (fails)
[ebuild R ] dev-lang/perl-5.8.8-r8 USE="berkdb doc gdbm -build
-debug -ithreads -perlsuid" 0 kB [0]
[ebuild R ] perl-core/ExtUtils-ParseXS-2.22.02 0 kB [0]
[ebuild R ] dev-perl/ExtUtils-XSpp-0.08 USE="-test" 0 kB [0]
[ebuild N ] dev-perl/wxperl-0.97-r1 0 kB [1]
xsubpp -v
xsubpp version 1.9508
Perl 5.10.1 box (ok)
[ebuild R ] dev-lang/perl-5.10.1 USE="berkdb gdbm -build -debug
-doc -ithreads" 0 kB
[ebuild R ] perl-core/ExtUtils-ParseXS-2.22.02 0 kB
[ebuild R ] dev-perl/ExtUtils-XSpp-0.08 USE="-test" 0 kB
[ebuild R ] dev-perl/wxperl-0.97 0 kB
xsubpp -v
xsubpp version 2.2202
No idea what output that is. Is ebuild some kind of source package manager?
The xsubpp version is the clue, I think. It's part of ExtUtils::ParseXS.
*If* you have ExtUtils::ParseXS 2.22 on both computers, the xsubpp
versions should be the same. Maybe due to the setup of your vendor (I
guess these are system perls), the core library is shadowing the
upgraded ExtUtils::ParseXS/xsubpp?
You can try to:
- install ExtUtils::XSpp and ExtUtils::ParseXS from CPAN ("sudo cpan
ExtUtils::XSpp")
- determine whether there's another xsubpp/ExtUtils::ParseXS that's not
being found by your shell/perl because it's shadowed by the one you're
running via "xsubpp -v".
Best regards,
Steffen
