[Oorexx-devel] USB Installation for macOS

For anyone interested in trying I have added a USB Installation of ooRexx for MAC to my dropbox, with instructions on how to use it. https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0 I have

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Unlike other systems where CMAKE is installed thru the system package manager On APPLE it has to be installed by the user and most likely the user will install the latest release I have been a bit conservative when I talked about 3.12 , I just checked and the download section of cmake

[Oorexx-devel] Fwd: Re: dynamic linking on macOS

Sorry, cannot get use to thunderbird vs web gmail with replies. cmake is at 3.12.4 for me on OpenIndiana On 01/03/19 03:16 PM, René Jansen wrote: Would there be any opposition if we upped the minimal cmake level to 3.12?

Re: [Oorexx-devel] Lingering rexximage process after multiple builds and increased memory usage of rxapi process after long processing times

50% is not a tiny little amount :-) but I hear what you say, I just wanted to be sure I am not sitting on something that needs investigation. What can I do to to help go after the rexximage hangs? Maybe it is not so critical (a reboot fixes it) unless such a build is somehow incomplete?

Re: [Oorexx-devel] Lingering rexximage process after multiple builds and increased memory usage of rxapi process after long processing times

Hi P.O., except for the rexximage hangs, the behaviour you report seems to be perfectly valid. Each test run creates a new rexx process, which uses quite some memory, and then ends. rxapi is being used by those tests and increases its memory footprint by a tiny little amount. rxapi is never

[Oorexx-devel] Lingering rexximage process after multiple builds and increased memory usage of rxapi process after long processing times

Dear developers,I have been building & testing ooRexx 5.0.0 multiple times as a kind of stress test in the last days. I have observed two things:1: occasionally I have observed a process rexximage staying behind after multiple runs. I think after a build (not a test). I have attached an analysis

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Yes, there you might have a point, but the plan is to have the rpath set correctly and relative to load_path. I’ll be back when I have Enrico’s changes and a new cmake. What is your cmake level? That should explain a lot. best regards, René. > On 3 Jan 2019, at 13:21, P.O. Jonsson wrote: >

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

ah good, that is a rather important result. I am (was) running cmake 3.9.4. I’ll try to build 3.12 and/or patch the libraries; it might even fix the librexxutil problem. I prefer this email, rvjan...@xs4all.nl Molto grazie Enrico, René. > On 3 Jan 2019, at 13:20,

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Dear René, It is exactly to avoid the problem with changes you have forgotten that I completely ERASED the disk before installing a pristine version of macOS Mojave; there are several directories that are simply not there (/opt and ~/Applications are two of them) when the installation is

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Oops my bad, I forgot to tell that I changed all my CMakeLists to use cmake_minimum_required( VERSION 3.12 ) And with that CMAKE provides the proper RPATH handling Without specifying anything , I just run otool -l rexx And all the rexx libraries are prefixed with the @rpath construct

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

I built with: cmake -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=/opt/ooRexx5.0.0 and had to install with sudo make install. otool -l (small el) gives all the libraries that need to be loaded, and the @rpath: ➜ bin otool -l rexx rexx: Mach header magic cputype cpusubtype caps

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Enrico, are all your cmake changes checked in to 11657, trunk? René > On 3 Jan 2019, at 12:23, Enrico Sorichetti via Oorexx-devel > wrote: > > I does not make any difference … > As long as the RPATH is properly defined > > As an absolute path pointing to the directory > > Or as a

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

I does not make any difference … As long as the RPATH is properly defined As an absolute path pointing to the directory Or as a relative path, specified as @executable_path/../lib ( my preferred way ) I just ran the test suite rexx testOORexx.rex -s -X native_API Tests ran:

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

yes, true. The only thing in it was ooRexx, so the sudo make install must have done that. Thanks. René. > On 3 Jan 2019, at 12:21, Enrico Sorichetti via Oorexx-devel > wrote: > > Seems strange … > ~/Applications is not provided by APPLE > So it carries the privileges You had when You

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Seems strange … ~/Applications is not provided by APPLE So it carries the privileges You had when You created it, Pretty easy to chown and chmod E > On 3 Jan 2019, at 17:18, René Jansen wrote: > > And one update: to my great astonishment, I cannot make a directory in > ~/Applications either

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

> On 3 Jan 2019, at 12:07, René Jansen wrote: > > 3) echo LD_LIBRARY_PATH 3) echo $LD_LIBRARY_PATH And one update: to my great astonishment, I cannot make a directory in ~/Applications either (without sudo) - when I assumed that everything in my home directory belongs to my userid.

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

I think we all say the same - we want it to work. So to make sure that it works (it is so easy to be fooled by older versions or settings you have forgotten) can we do this: 1) echo $PATH 2) echo $DYLD_LIBRARY_PATH 3) echo LD_LIBRARY_PATH 4) run otool -L on the rexx executable and all