Compiling ooRexx 3.1.2. on Windows Server 2003.
It fails compiling orxscrpt.cpp. The included file "security.inc" can not be found. This file does not exist
in the source distribution. Should the include statement
just be commented out?
Logged In: YES
No, it should not be commented out, it is needed.
The security.inc file is generated during the build process. If it is missing you don't have something set up correctly.
From the root of the source tree do:
E:\work.ooRexx\3.x\wc\interpreter>rd /q /s Win32Rel
Building Open Object REXX for Windows - Non-Debug Version
rxapi.exe (Process ID: 200) killed successfully
If the build fails, grab the Win32Rel.log file out of the Win32Rel directory and attach it to this bug.
You seem to have CSS turned off.
Please don't fill out this field.
Logged In: NO
The problem is that the PATH environment variable has not been changed to the include
the location of Rexx. I solved the problem by updating the PATH variable and then running
makeorx. It ran to completion with no errors.
Ah, I had forgotten about this.
You should not need an already existing ooRexx on your system in order to build ooRexx. This bug was previously discovered and is fixed in SVN. The bug was: [ 1768659 ] Windows build fails without a working ooRexx
Even though this turned out to be a duplicate, we appreciate your effor in reporting the bug. Thanks!
You can apply this patch yourself to fix the problem in your working copy:
--- platform/windows/buildorx.bat (revision 652)
+++ platform/windows/buildorx.bat (revision 651)
@@ -168,7 +168,8 @@
ECHO Generating security manager code for script engine
-REXX %OR_ORYXAXSCRIPT%\rexx2inc.rex %OR_ORYXAXSCRIPT%\security.rex %OR_ORYXAXSCRIPT%\security.inc szSecurityCode >> rexx2inc.log 2>&1
+REXX rexx2inc %OR_ORYXAXSCRIPT%\security.rex %OR_ORYXAXSCRIPT%\security.inc szSecurityCode >>..\rexx2inc.log 2>&1
@ECHO Building ORXSCRPT..
Sign up for the SourceForge newsletter: