Hello,
I have just tried the following patch:

Index: rexxapi/server/platform/unix/APIService.cpp
===================================================================
--- rexxapi/server/platform/unix/APIService.cpp>(revision 3870)
+++ rexxapi/server/platform/unix/APIService.cpp>(working copy)
@@ -54,7 +54,11 @@
 #define RUN_AS_DAEMON
.
 #ifdef RUN_AS_DAEMON
+#ifdef __REXX64__
+#define OOREXX_PIDFILE "/var/run/ooRexx_64.pid"
+#else
 #define OOREXX_PIDFILE "/var/run/ooRexx.pid"
+#endif
 bool run_as_daemon = true;
 #else
 #define OOREXX_PIDFILE "/tmp/ooRexx.pid"
Index: rexxapi/common/ServiceMessage.hpp
===================================================================
--- rexxapi/common/ServiceMessage.hpp<->(revision 3870)
+++ rexxapi/common/ServiceMessage.hpp<->(working copy)
@@ -64,7 +64,11 @@
     return newString;
 }
.
+#ifdef __REXX64__
+#define REXX_API_PORT 43334
+#else
 #define REXX_API_PORT 43332
+#endif
.
 // a session identifier
 typedef uintptr_t SessionID;

With this patch I can run the 32 bit and 64 bit daemon in parallel.

Maybe we could also change SysLocalAPIManager.cpp

#ifdef __REXX64__
char apiExeName[] = "rxapi64";
#else
char apiExeName[] = "rxapi";
#endif

and rename the 64 bit rxapi to rxapi64. With this change we can be sure
that the correct rxapi is started.

This would also require a change to FileSystem.cpp

strcpy(fullname, ORX_CATDIR"/rexx.img");
->
#ifdef __REXX64__
strcpy(fullname, ORX_CATDIR"/rexx64.img");
#else
strcpy(fullname, ORX_CATDIR"/rexx.img");
#endif

and PlatformDefinitions.h.

#define BASEIMAGE     "rexx.img"
->
#ifdef __REXX64__
#define BASEIMAGE     "rexx64.img"
#else
#define BASEIMAGE     "rexx.img"
#endif

The *.cls files and the .cat are independent. This would only leave
rxsubcom / rxqueue / rxapi and rexxc. We could add a 64 to all of then.

Then we could provide a script switchmode which flips the links in /usr/bin.

Is this totally off or worth to look after ??

Bye
  Rainer

------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to