ooRexx from the ooRexx-4.2.0-source.tar.gz file fails to compile on Mac OS X 10.6.8 (Intel 32bit)for the following reason:
make[2]: No rule to make target rexxapi/server/platform/unix/mac/APIService.cpp', needed by
rxapi-APIService.o'. Stop.
make[1]: [all-recursive] Error 1
make: *** [all] Error 2
No such file: rexxapi/server/platform/unix/mac/APIService.cpp
No such directory rexxapi/server/platform/unix/mac
Anonymous
Thanks for the pointer. Done. [#1523]
Related
Bugs:
#1523Dear Alexander,
My first mail bounced, I hope you get this one.
I guess you got stuck somewhere on this matter? Maybe I have what you need to get forward.
As you have seen there is no official installer for Mac since 4.1.2, some five years old, and that version is not even running on a Mac from El Capitan (10.11) onwards, We are now at High Sierra, 10.13.
I have tried for a week (and failed :-() to make an installer the official way so I did something else.
Since some time I can reliably build ooRexx in any flavor from source. I am using another CMakeLists.txt than you do but basically it uses the same means to redirect the output. What I have done is to reverse engineer such a working installation and provide symbolic links to all the right places. This makes away with the need to change the path or any other system settings, the installation is completely autonom. Tedious but once I had done the ground work the rest was a walk in the park. I have written a Rexx script that can create a line based installer for any place on the machine. So far I have done installers for 4.1.2, 4.2 and 5.0.0, the last one for various places, even for a USB stick!
Now, since I have done an installer for ooRexx to reside in, say, /usr/local/ooRexx5.0.0 (in parallel to where Homebrew installation resides) it would not be any problem for me to provide an installation that resides in, say /usr/local/cellar/ooRexx5.0.0, would that be useable for you? There is one installer shell script and another uninstaller shell script for the installation, a single command to run, that´s all.
Until now I have only done 64-bit builds, do you need 32 bit builds?
Is it ok for you to get the build in a dmg (compressed image) file or should I make it a tarball?
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oorexx@jonases.se
Related
Bugs:
#1319The code for 5.0.0 builds fine for the Mac, which is the only place this is likely to be fixed.