Line 9 of Zlib.pm is indeed:
use Scalar::Util qw(dualvar);

The "is only avaliable with the XS version" error message is also in
S::U source code, which seems to reinforce your analysis Rob.

I am however confused. Prior to reinstalling Scalar::Util, I tested the
following script to check whether it was the culprit:

use Scalar::Util qw(dualvar);

print "$Scalar::Util::VERSION\n";
my $foo = dualvar 10, "Hello";
print "$foo\n";

And this is working fine, so dualvar seems to be available. Why doesn't
it complain about the XS version in this case? I have Scalar::Util 1.18.
Is it possible that another version is used when installing PAR::Packer?

Cheers,
Hoang-Anh

-----Original Message-----
From: Sisyphus
Sent: 16 October 2007 08:13
To: Hoang-Anh Phan; Steffen Mueller
Cc: [email protected]
Subject: Re: PAR and PAR::Packer CPAN installation errors

>
> Hi
>
> Thanks for that. I've tried to build PAR::Packer without the -j3
option,
> and now got this error:
>> make
> ./static -I"/home/phan/.cpan/build/PAR-Packer-0.976-2LBobZ/inc"
> -I[............]
> -I../myldr/.. -I../blib/lib -q -B -O../script/parl
> is only avaliable with the XS version at
> /usr/lib/perl5/site_perl/5.8.5/Compress/Zlib.pm line 9
>

Assuming that line 9 of Zlib.pm is:

use Scalar::Util qw(dualvar);

then the problem probably lies with Scalar::Util. The pure perl build of

Scalar::Util does not have the 'dualvar' function.

Try reinstalling Scalar::Util from source. That should (hopefully)
produce 
an XS build of that module, and 'dualvar' will become available.

Cheers,
Rob 


http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal 
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on 
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
                                        

Reply via email to