Skip Menu |

This queue is for tickets about the PAR CPAN distribution.

Report information
The Basics
Id: 12188
Status: resolved
Priority: 0/
Queue: PAR
People
Owner: smueller [...] cpan.org
Requestors: vince.usenet [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in:
  • 0.86
  • 0.87
Fixed in: (no value)

History Show all quoted text
  Thu Apr 07 12:55:59 2005 Guest - Ticket created
Subject: install problem (interaction with File::Path) for 0.86 and 0. 87 on Ubuntu/Debian
Show quoted text
> I'd like to report difficulty installing PAR 0.86 and 0.87 > (and the svn archive as of this moment) on an Ubuntu/Debian > system. PAR 0.85 installs fine.
The problem is that File::Path got patched in the latest Ubuntu/Debian packages for Perl. It now require's Cwd which it didn't do before. But deep down in par.pl, File::Path is require'd while local $INC{'Cwd.pm'} = __FILE__; is in effect. I.e. par.pl pretends Cwd is loaded while it really isn't. This causes `Bareword "getcwd" not allowed while "strict subs" in use' since getcwd is not declared anywhere. Comment out all (4) occurences of the above line in par.pl, this hasn't shown any negative effects for me so far. I dunno why this hack is there in the first place (and why it's disabled on Windows)? Cheers, Roderich source : http://permalink.gmane.org/gmane.comp.lang.perl.par/1401 I have been bitten by this one too. Roderich suggestion helped, but it's not enough : the same error then appears elsewhere. I gave up and felt back on 0.85. Ubuntu version : 5.04 (Hoary) Perl version : 5.8.4-6ubuntu1 -- Vince
  Sat May 20 08:43:43 2006 smueller [...] cpan.org - Correspondence added
RT-Send-CC: Roderich.Schupp.ext [...] BenQ.com
On Do. 07. Apr. 2005, 12:55:59, guest wrote: Show quoted text
> > I'd like to report difficulty installing PAR 0.86 and 0.87 > > (and the svn archive as of this moment) on an Ubuntu/Debian > > system. PAR 0.85 installs fine.
> > The problem is that File::Path got patched in the latest > Ubuntu/Debian packages for Perl. It now require's Cwd > which it didn't do before. But deep down in par.pl, File::Path > is require'd while > > local $INC{'Cwd.pm'} = __FILE__; > > is in effect. I.e. par.pl pretends Cwd is loaded while it really > isn't. > This causes `Bareword "getcwd" not allowed while "strict subs" in use' > since getcwd is not declared anywhere. > Comment out all (4) occurences of the above line in par.pl, > this hasn't shown any negative effects for me so far. > > I dunno why this hack is there in the first place (and why > it's disabled on Windows)? > > Cheers, Roderich > > source : http://permalink.gmane.org/gmane.comp.lang.perl.par/1401 > > I have been bitten by this one too. > Roderich suggestion helped, but it's not enough : the same error then > appears elsewhere. > I gave up and felt back on 0.85. > > Ubuntu version : 5.04 (Hoary) > Perl version : 5.8.4-6ubuntu1
The mandatory question since this ticket is over a year old: Does this still apply to PAR 0.93? If so, I will look into it. Thanks. Any help apprechiated. Steffen
  Sat May 20 08:43:45 2006 The RT System itself - Status changed from 'new' to 'open'
  Sat May 20 08:43:46 2006 smueller [...] cpan.org - Given to SMUELLER
  Mon May 22 05:30:34 2006 Roderich.Schupp.ext [...] BenQ.com - Correspondence added
Subject: RE: [rt.cpan.org #12188] install problem (interaction with File::Path) for 0.86 and 0. 87 on Ubuntu/Debian
Date: Mon, 22 May 2006 11:29:38 +0200
To: <bug-PAR [...] rt.cpan.org>
From: "Roderich Schupp \(ext\)" <Roderich.Schupp.ext [...] BenQ.com>
Show quoted text
> Does this still apply to PAR 0.93? If so, I will look into it. Thanks.
Any help PAR 0.93 should be OK, since all occurrences of local $INC{'Cwd.pm'} = ... have been commented out. I actually checked PAR 0.93 on Debian unstable and the problem isn't there (but see below). But Debian unstable uses perl 5.8.8 and its File/Path.pm doesn't require Cwd. FYI: The latest perl versions for Debian stable (sarge) and Ubuntu hoary and dapper still use a patched File/Path.pm that _does_ require Cwd. BTW: PAR 0.93 fails test #4 in t/30-current_exec.t with sh: make: command not found The command that failed was make > out.make 2>&1 The reason is simple: on line 50 $ENV{PATH} = $path; restricts PATH to just the test script directory, but then you try to execute a C Inline program; but Inline.pm underneath creates a Makefile, runs make, which will run the C compiler etc, so it requires a little more elaborate PATH... Possible fix attached. Cheers, Roderich

Message body is not shown because sender requested not to inline it.

  Tue May 23 09:05:13 2006 smueller [...] cpan.org - Status changed from 'open' to 'resolved'