On Mon, 01 Apr 2002 02:52:20 GMT, [EMAIL PROTECTED] (Stephen Zander)
wrote in news:87hemwyvtn.fsf;pobox.com:
[...] looking to invoke perl as part of his test scripts and given
that the test suite will usually be invoked using FULLPERL, it makes
sense to me to use that for any additional perl
Regarding:
Subject: Re: name of perl in MakeMaker
Date: 7 Nov 2002 19:35:21 -
From: [EMAIL PROTECTED] (Soren A)
Newsgroups: perl.module-authors
Boy did I screw up. I am holding my nose as I type this, because of that
stanky code I posted. I am going to try to cancel the posting
Stephen Zander [EMAIL PROTECTED] wrote:
Sam Hi all, How do you return the name of perl in your module's
Sam Makefile.PL?
If you're generating rules for the Makfile that will be produced,
don't try to hardcode perl at all. Rather use the PERL Makefile
variable that MakeMaker has
On Monday, April 1, 2002, at 09:39 AM, Stephen Zander wrote:
Sam == Sam Vilain [EMAIL PROTECTED] writes:
Sam Hi all, How do you return the name of perl in your module's
Sam Makefile.PL?
If you're generating rules for the Makfile that will be produced,
don't try to hardcode perl at
On Mon, Mar 25, 2002 at 09:04:43PM +1100, Ken Williams wrote:
use Config;
$perl = $Config{perlpath};
This is very wrong. This is what libwww is using; as a result, you
cannot test libwww with uninstalled Perl.
*At* least use
(-x $^X) ? $^X : $Config{perlpath};
I agree
On Thu, Mar 14, 2002 at 11:38:38AM +0100, Wim Verhaegen wrote:
How do you return the name of perl in your module's Makefile.PL?
use Config;
$perl = $Config{perlpath};
This is very wrong. This is what libwww is using; as a result, you
cannot test libwww with uninstalled Perl.
*At*
