Make ActivePerl use existing compiler

testuser448 has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Make ActivePerl use existing compiler by syphilis (Archbishop) on Aug 24, 2015 at 07:34 UTC
I do* have MinGW (gcc-4.8.1) installed in C:\MinGW with c:\MinGW\bin in my PATH* Yes, I would have thought that would be sufficient. Do you also have 'dmake' installed and in your path ? (I'm merely wondering whether ActivePerl might be mistakenly equating the absence of 'dmake' with the absence of a compiler.) Cheers, Rob	[reply]
Re^2: Make ActivePerl use existing compiler by testuser448 (Initiate) on Aug 25, 2015 at 01:22 UTC
I don't have dmake.	[reply]
Re^3: Make ActivePerl use existing compiler by syphilis (Archbishop) on Aug 25, 2015 at 08:49 UTC
I don't have dmake I speculate that if you install 'dmake' and add it to your path, then cpan installs will happily use your gcc-4.8.1 (assuming, of course, that gcc-4.8.1 is also still in your path). I could be wrong, of course. Cheers, Rob	[reply]
Re^3: Make ActivePerl use existing compiler by Anonymous Monk on Aug 25, 2015 at 06:30 UTC
Well :) if you decide to try activeperl again, you could get dmake from https://metacpan.org/release/dmake or http://code.activestate.com/ppm/dmake/	[reply]
Re^4: Make ActivePerl use existing compiler by testuser448 (Initiate) on Aug 27, 2015 at 07:03 UTC
Re: Make ActivePerl use existing compiler by davies (Monsignor) on Aug 24, 2015 at 10:48 UTC
There may not be a way round. See BrowserUK's reasons (Re^3: Installing Template::Toolkit on Windows) for avoiding CPAN and its near relatives. Regards, John Davies	[reply]
Re: Make ActivePerl use existing compiler by RonW (Parson) on Aug 24, 2015 at 17:13 UTC
You said you have MinGW 4.8.1 installed and that the `cpan` command tried to install MinGW 4.6.3 The `cpan` command maybe actually meant you have a compiler different from the one that Perl was built with. In general, it is better to compile XS modules with the same compiler, version and options as Perl itself. It may well be that an executable built with 4.6.3 can load modules built with 4.8.1 with no problems, but the `cpan` command may still be being conservative. FWIW, one of the reasons I like the Strawberry Perl distribution (when I have to run Perl on MS Windows) is that it includes a copy of the compiler tool chain used to build the distribution.	[reply] [d/l] [select]
Re^2: Make ActivePerl use existing compiler by testuser448 (Initiate) on Aug 25, 2015 at 01:29 UTC
I downloaded the Strawberry Perl portable version. It includes the MinGW compiler, but nothing is installed so it definitely would not mess up my existing MinGW installation, which was my fear when I saw "Downloading MinGW 4.6.3 ...". Thanks.	[reply]
Re: Make ActivePerl use existing compiler (cpan?) by Anonymous Monk on Aug 24, 2015 at 07:40 UTC
That is not usually a message any "perl" would give The "cpan" program might do that , I can't exactly recall, so what program are you calling when you encounter said message?	[reply]
Re^2: Make ActivePerl use existing compiler (cpan?) by GrandFather (Saint) on Aug 24, 2015 at 08:25 UTC
Perhaps the first four words of the OP's post gives you a clue: "When I run cpan ...". Premature optimization is the root of all job security	[reply]
Re^3: Make ActivePerl use existing compiler (cpan?) by Anonymous Monk on Aug 24, 2015 at 08:59 UTC
Perhaps the first four words of the OP's post gives you a clue: "When I run cpan ...". Very interesting, no hits http://search.cpan.org/grep?cpanid=ANDK&release=CPAN-2.10&string=looks&i=1&n=1&C=0 no hits http://search.cpan.org/grep?cpanid=ANDK&release=CPAN-2.10&string=compiler&i=1&n=1&C=0 PERL cannot find the C Compiler says message comes from ppm ... because cpan isn't configured yet, so configure cpan	[reply]
Re^4: Make ActivePerl use existing compiler (cpan?) by testuser448 (Initiate) on Aug 25, 2015 at 01:31 UTC