3/30/2023 0 Comments Activeperl windows vistaYes, there are some situations where IIS will respond very badly when running Perl if there is any sort of loading. There’s a lot of difference between how a Perl that is designed for use with Apache will run, when compared with how a Perl that is not customized for use with IIS will run. Are you still using Apache on the new systems, or are you running the IIS that can be installed on Windows Server 2019 instead? XAMPP also usually means Apache is the webserver, and Apache is much less common on Server 2019 than it was on 2003 or 2008. In order to use, many of them would have to be recompiled from the original source code for Apache and the plugin. Among other issues, the Apache plugins provided by XAMPP are not compiled against ActivePerl. It’s not so easy to inject ActivePerl into the XAMPP mix. If you were running XAMPP, the odds are that you were using the built in Perl supplied by XAMPP. XAMPP supplies it’s own Perl, and it’s not ActivePerl. However, are you sure you were using ActivePerl in the past? There are no versions of ActivePerl from 2014 that are compatible with Server 2016 or Server 2019. If doing so in a fresh command prompt, remember to run the devel64-in32mode.bat setup.bat script in local before running makegs2圆4.bat.Versions could be important, particularly if you’re trying to use the same ActivePerl you would have had running on Server 2008. If that fails, run makegs2圆4.bat and select the clean command (option 6) and then re-run makegs2圆4.bat to re-compile from scratch. If the 'error' folder or apache-httpd folder did not exist and therefore can't be deleted, then just re-run makegs2圆4.bat again. In that case, try deleting the apache-httpd\windows\error folder if it has been generated, or all of the apache-httpd folder and run makegs2圆4.bat again, choosing the same options as before. In GS2 SVN checkouts from before changeset 31428, compilation on 64 bit Windows could still fail with error messages as described here, which indicates that the race condition has struck. (Type "6" to clean compiled files before recompilation if you want to recompile from scratch). Type "Y" to Extract All, then when the DOS prompt display asks what you want to compile up, type "4" to compile all without debugging, or type "5" to compile everything with debugging on. Therefore, when compilation is finished, open a fresh DOS prompt to run GLI from.įinally, still from your top level GS2 folder, run makegs2圆4.bat Note: after compiling with the above steps, your terminal would be left in a state where running GLI would not be able to locate the Greenstone building scripts like. ![]() Open a new terminal, go back to into the SVN Greenstone 3 checkout directory and run the devel script again before running the actual compile command: Move iconv-winVS14-VS2015-plus.zip iconv.zip Pushd gs2build\common-src\indexers\packages\windows\iconv ![]() (For details on which libiconv this uses and how it was modified to get it to work with VS14, refer to this.) Visual Studio 2015 seems to also work with VS15/VS2017), then before proceeding, backup your windows iconv.zip and rename iconv-winVS14-VS2015-plus.zip as the new iconv.zip, as below. If you're using Visual Studio 14 ( a.k.a. (The gs3-devel.bat will print a file not found error on Windows, since gs3-devel.bat runs gs3-setup.bat which refers to some files that the ant prepare step has yet to checkout.) Then you're ready to proceed by running the toplevel gs3-devel.bat: We found that 32 bit MS VS 9.0 and 12.0 works in our case, if we set gs3-devel.bat to point to C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC so that the script can then issue call vsvarsall.bat amd64 to get it working for 64 bit machines. Use a text editor to edit local/gs3-setup.bat and local/gs3-devel.bat to contain the paths to Java, Perl, Ant, Visual Studio's VC folder on your system. Then run the gs3-devel.bat in your toplevel GS3 folder before trying to run any of the ant compilation commands:įor the OS-bitness folder, you can at present choose from "darwin-64bit", "linux-32bit", "linux-64bit", "windows-64bit". Then edit the gs3-setup and gs3-devel scripts in local to point to wherever you have JAVA, PERL, (ANT) installed (and, on Windows, the location of your Visual Studio's VC directory). The local subfolder will also provide you with ant. The process is to checkout greenstone3 from SVN, then checkout the appropriate subfolder for your OS and bit architecture from into your greenstone3, and name that subfolder local. If you want to compile GS2 or GS3 with debugging on, you will also need Microsoft SDKĪpache Ant is included in the following instructions, since it too is needed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |