If that is true, then why are you trying to "swim up a waterfall"?
I suspect that "going with the flow" will much easier!
I can think of some reasons why you might want to do what you are doing, but I'd like to hear your reasons "from the horse's mouth".
Your default should be to use the new AS tools to construct your build which will include the Maria DB.
When the PPM (Perl Package Manager) went away, AS (Active State) created a whole new ecosystem on their website. Basically you fork a branch off of one of their standard builds, then add what you want (like the Maria DB), then AS creates a complete .exe or .MSI file for you. This complete customized Perl version then comes to you already built. AS will allow you to re-distribute that installation file to anybody you want - that solves one licensing issue that previously existed.
In a classic, "do as I say, not as I do", I am still using an old AS Perl version because right now, I don't need anything more advanced. And there is some hassle in getting an AS version equivalent to what I have arrived at now with PPM. However, I have in the past built custom Perl versions for other Monks that they have successfully loaded on their machines. So the process does work. AS has sped the compile/build time up considerably - used to take about 20 min - but its a lot faster now.
When you make your build, you should include the cpan module. This includes (like it always has, a complier that is compatible with the rest of the build). Do not try to mix compliers. Including cpan will allow small stuff to be added directly from CPAN without having to go through the entire build process. But it sounds like this DB has enough dependencies etc that you are better off having AS do the build. If the AS GUI allows you to add this package to your new branch, it will build successfully.
As an update: As I remember the first time I used the new tools, it took several hours to arrive at a result. There was a bit of screwing up and redoing things... Also, this new process is still a "work in progress" and AS does make changes to the process. Were I to do it again, it would probably take several hours to figure out exactly what their tool currently does. However, I suspect that you've already spent more than that amount of time already being frustrated! Spend a morning or afternoon and see how it goes...
Updating again to be clear: Instead of just downloading the current AS "default build". Create a user account (its free). Fork a branch, add Maria DB, cpan, and other modules that you want. Have AS build it for you - if I remember right, you get an email when it is ready. I don't know whether your installation was pre or post installation program enhancements. It used to be that you could not just slam a new MSI onto an old installation - in theory you can do that now. But I recommend against that. Uninstall your Perl. Then run your downloaded new MSI containing Maria.
AS (Active State) cpan module comes with the gcc compiler. I suspect that trying to use any other will cause big problems. I actually have the gcc 32 bit C compiler for other reasons and sometimes it and the 64 bit version "fight". That is hassle enough! "Fighting" between VCC and gnu C sounds like even more trouble!
Update again: Ok, I found the last long thread about this from ~1 year ago: Perl5.26 installing Tk module manually. The URL for the build that I made probably doesn't work anymore, but the OP was able to install this thing when the URL was current and it appears to have been successful.
In reply to Re^5: DBD:Mysql compilation failed on windows
by Marshall
in thread DBD:Mysql compilation failed on windows
by pesubbia
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |