AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Activeperl vs strawberry perl3/18/2023 ActivePerl 5.28 and 5.26 do build, but are missing a required MySQL client library.ActivePerl 5.32 and ActivePerl 5.34 fail to correctly build at this time, so can’t be used for MIDAS.However, in August 2021, as things stand at the moment, we can no longer recommend ActivePerl (we’ve even now removed this recommendation from our website). Last year we changed to recommending either ActivePerl or Strawberry Perl. We’re really saddened by the recent direction that ActiveState have moved in with ActivePerl, and their apparent lack of enthusiasm for and commitment to ensuring that it actually works with popular databases!įor over a decade, we used to exclusively recommend ActivePerl to our Windows-based customers. Why would anyone want to do this? – it would just be easier to install and use Strawberry Perl and not even bother with ActivePerl! Conclusions But just to be clear – right now… In order for ActivePerl to work with MySQL / MariaDB databases you need to install Strawberry Perl! So we tried this, and it did indeed resolve the issue. Their best solution… install Strawberry Perl, grab the required “libmysql_.dll” file that gets installed with that, and copy the file over to your ActivePerl install! dll file that doesn’t get included with builds of ActivePerl. The issue appears to be related to a missing MySQL “client library”. A number of people have posted with similar issues in ActiveState’s forums (like in this thread, and this thread). It seems like we’re not the only ones having issues using recent builds of ActivePerl built on the ActiveState platform with MySQL / MariaDB packages included. We looked a little deeper into our test server’s error logs and discovered that a key component needed by the MySQL and MaraDB drivers was actually missing and hadn’t been included within the distribution. The 5.34.0 build just failed to build (just like the original 5.32.0 build). The 5.26.3 build produced the same results as the 5.28.3 build. We also then spent time and built identical packages on the ActiveState platform under both Perl 5.26.3 and also Perl 5.34.0. msi installer, we completely uninstalled Perl and tried again with the. Wondering if it may have been an issue with the. Running our Server Readiness Tool under our custom ActivePerl 5.28.3 distribution indicates problems with DBD::mysql and DBD::MariaDB Trying other versions That is unless you have a GitHub account (which let’s face it, most of our customers likely won’t have) in which case you can just sign-in. Signing up for an ActiveState account is required if you wish to “custom build” ActivePerl with the specific modules/packages you require. Here’s how we got on… Signing up for an ActiveState account This was a far less user-friendly to install Perl modules than it was to use PPM, where modules could be installed at any time with just a couple of clicks.Īnyway, we thought we’d try using ActiveState’s platform to generate a custom-build of Perl containing all the additional modules/packages which MIDAS requires. They could then “build” their own custom-build of ActivePerl containing the additional packages/modules they require. This unique feature of ActivePerl was sadly retired by the vendor (ActiveState) by ActivePerl 5.28.įrom ActivePerl 5.28 onwards, if users wanted to install additional Perl modules they were encouraged to instead sign up for an ActiveState account. We originally loved ActivePerl as it made it really easy for our customers (and us!) to install these modules via the “Perl Package Manager” tool (or PPM) for short. Our MIDAS software requires a handful of these additional modules in order to function. If installing Perl distribution XY is not enough to get xindy work, it would be nice to know.There are over 100,000 additional Perl “modules” (or “packages”) available to enhance the “core” functionality of Perl. I would prefer a Perl distribution which is easy to install (if there is a difference between the distributions). I don't care about doing anything (else) with Perl. There are three different interpreters to choose from at Ĭould somebody, please, give a new answer to that question instead of just linking to How to use Xindy with MiKTeX? which is usally done. I searched the MiKTeX documentation and also the Web, but I did not found an answer to my question, which Perl interpreter to install for Windows. So, hopefully, the only missing thing is a Perl interpreter to run xindy. At least on my system, I still get the error message: xindy: The Perl interpreter could not be found Unfortunately, this does not mean that you can use xindy out of the box. Since June 2015, xindy is finally included in the MiKTeX distribution for Windows. Please, read the question before marking it as duplicate.
0 Comments
Read More
Leave a Reply. |