----- Original Message -----
From: "Jan Dubois" <j...@activestate.com>
>> Is it acceptable to have those Config values specify the full path and
>> extension ?
>
> Acceptable by whom? :) The documentation doesn't really say one way or
> the
> other:
>
> | cc (cc.U):
> | This variable holds the name of a command to execute a C compiler which
> | can resolve multiple global references that happen to have the same
> | name. Usual values are 'cc' and 'gcc'.
> | Fervent ANSI compilers may be called 'c89'. AIX has xlc.
That's what I was wondering. If it's not prohibited, then it's permitted :-)
>> This prevents Inline::C from building as
>> C:/_32/ap1005/site/bin/gcc.exe.exe
>> (which, of course, doesn't exist) can't be found by the C/Makefile.PL.
> Would you mind filing a bug report for it?
Shall do - along with a patch.
>
> ExtUtils::MM_Win32 uses this mechanism:
>
> sub is_make_type {
> my($self, $type) = @_;
> return !! ($self->make =~ /\b$type(?:\.exe)?$/);
> }
I'll probably just do
if($Config{make} =~ /\bdmake/i) { ... }
(I think it's only 5 files in PDL that need the amendment.)
Thanks Jan.
Cheers,
Rob
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
