On Thu, 2003-02-27 at 06:18, Ken Williams wrote:
>
> On Wednesday, February 26, 2003, at 09:59 AM, Nicholas Clark wrote to
> the Inline list:
>
> > As promised, er, a few months ago, here is a patch that makes Inline
> > work reliably when there is more than one perl installed, and all
> > *think*
> > that they are (say) /usr/local/bin/perl
>
> You mean that all of them have /usr/local/bin/perl as
> $Config{perlpath}, or that somehow symlinks or shebang paths are giving
> them that impression?
>
>
> > With this Inline will "believe" $^X in preference to $Config{perlpath}
> > if $^X is an absolute path, so that Inline will get the same perl as is
> > running the script, despite the sysadmin's best efforts to confuse
> > things
> > by installing more perl versions.
>
> I'm interested in getting this right for Module::Build too. This seems
> like a reasonable approach to take. I think the big problem with $^X
> is that it can sometimes be set to just "perl" or something in shebang
> scripts, so checking for an absolute path seems like a good way to go.
> Thanks.Or even potentially worst, if running in a C programm that embeds a Perl interpreter (read mod_perl), the value $^X will be that program (read httpd), most certainly not always what one wants ;-( > -Ken > > -- -------------------------------------------------------------------------------- Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 (122FF51B/C634E37B) http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3 A5A5 Q: It is impossible to make anything foolproof because fools are so ingenious. perl -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}'
signature.asc
Description: This is a digitally signed message part
