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.
|