Re: Using Perl's cc

[Eli Zaretskii]

> Date: Sat, 25 Jul 2015 22:33:23 +0100
> From: Gavin Smith <address@hidden>
> Cc: address@hidden
> 
> On 4 July 2015 at 19:48, Eli Zaretskii <address@hidden> wrote:
> >> Meanwhile I looked around, and it sounds like all that's needed is
> >> something like --with-perl-dir=/path/to/perl/installation/directory,
> >> and perhaps a small change to how fetch_conf.pl is invoked (it should
> >> no longer run "/usr/bin/env perl", but the one in the specified
> >> directory's bin/ subdirectory).  Moreover, it sounds like ActiveState
> >> Perl, which is what I have here, already supports MinGW automagically
> >> (it returned the correct file name for 'cc' config option, and I
> >> cannot see how it could do that without examining my system's PATH).
> 
> I think running "./configure PERL=/path/to/perl" could work.

I will try that when I have time.

> > Hmm... one slight complication:
> >
> >   $ /d/usr/Perl/bin/perl ./fetch_conf.pl archlibexp
> >   D:\usr\Perl\lib
> >
> > It outputs the directory with backslashes.  This cannot be put
> > verbatim into a Makefile, because Bash needs each backslash doubled.
> 
> In the latest, I turned two backslashes (output by Perl) into one. I
> would expect
> 
>     $ /d/usr/Perl/bin/perl -V:archlibexp
>     archlib='D:\\usr\\Perl\\lib'

I get here this instead:

  archlibexp='D:\usr\Perl\lib';

(note also the trailing semi-colon).  This is a native Windows Perl,
so I guess it doesn't expect to have to quote or escape the
backslashes.

> This can easily be tweaked as necessary, for example, leave double
> backslashes as they are.

I will see what this does.

Thanks.