Re^7: DBD:Mysql compilation failed on windows

The OP's statement also puzzled me!!!

I am still on AS (ActiveState) 5.24 which is the last version with PPM. My version was built with 64 bit gcc. I have used the AS cpan module to install some stuff which was not available via PPM successfully - sometimes not! I have found that some make files can have fine differences between Unix and Windows.

I do not know anything more about what AS (ActiveState) is doing than when I last looked into this a year ago (May 2021) as per the previous link I posted.

I suppose that it is possible that AS has switched compliers? I don't know. The MS C compiler is now free for non-commercial use. I used to get that and MASM, etc via my .edu connections, but I don't need to do that anymore. Which is actually a bummer because I used to be able to get the O/S free also.

AFIK, the process I described to get a custom AS Perl build still exists no matter what compiler that AS is currently using. You wind up with an .MSI file and there aren't any "build errors".

I think the OP needs to clarify exactly how his/her build came to be installed!

If ActiveState is the desired "flavor" of Perl, then I think my post and referenced links are appropriate. If not, what the OP wants is a whole different "ball game".

Summary: I don't know exactly what the OP is talking about either!

As an update: AFIK, the MS C compiler puts a forensic "footprint" into the object code. Meaning that it is possible to determine whether or not a particular set of bits was generated by a "free" vs a "licensed" version of MS code - this not just one byte. Something to consider.

Comment on Re^7: DBD:Mysql compilation failed on windows

Replies are listed 'Best First'.
Re^8: DBD:Mysql compilation failed on windows by syphilis (Archbishop) on Mar 13, 2022 at 04:15 UTC
I suppose that it is possible that AS has switched compliers? In the beginning, they produced perls built using MSVC++ version 6.0. Later on, IIRC, even though their perls were still being built by a Microsoft Compiler, it became possible to `ppm install mingw`, which would install a mingw port of gcc. That gcc compiler could then be used to build perl extensions (XS modules), etc. This was facilitated by software that shipped with the AS perl distro and provided the same capability as provided by ExtUtils::FakeConfig. Later again, ActiveState started building their perls with a mingw port of gcc, but I'm not sure when that change actually happened. I, too, still have an AS build of perl 5.24 - specifically a 64-bit perl-5.24.1 built with gcc-4.6.3. I know it's an AS build because the `perl -V` output contains: `Locally applied patches: ActivePerl Build 2402 [401627]` [download] To me, it looks unlikely that ActiveState ever provided an MSVC-built perl-5.24.1 - but I don't really know. Cheers, Rob	[reply] [d/l] [select]
Re^9: DBD:Mysql compilation failed on windows by Marshall (Canon) on Mar 13, 2022 at 04:54 UTC
I also show something similar on my AS 5.24 Windows machine: `Locally applied patches: ActivePerl Build 2404 [404865]` [download] The claim by the OP that he is using "active Perl" has got us into quite a kerfuffle.. Something is wrong about the "story". I think the OP should "start over" with a new Perl installation. Going from "ground-zero" to working will be easier than going from "we don't know and not working" to working.	[reply] [d/l]
Re^10: DBD:Mysql compilation failed on windows by syphilis (Archbishop) on Mar 13, 2022 at 10:43 UTC
I think the OP should "start over" with a new Perl installation. Ummmm ... I've certainly no objection to the OP doing that. In fact I would probably recommend the same. However, I also think that the OP's current perl should be quite capable of accommodating DBI, DBD::MySQL and DBD::MariaDB. Cheers, Rob	[reply]


Just another Perl shrine
	PerlMonks