Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

Hi, I am fully sorry but I failed to apply the patch, I have never done it before (or it was a REALLY long time ago).It is my understanding that I am supposed to patch the executable in the build directory, as inworkspace⁩/ooRexx-macOS1014-build⁩/oorexxBuild⁩/bin? This was the result. I have

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 04.01.2019 um 21:41 schrieb Rick McGuire : > > H, this debug information doesn't make sense for a couple of reasons. > First of all, if rexximage was hanging this way, then the build would never > complete...but it does

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

I have the germ of an idea on this. Could you try the attached patch to see if the problem goes away? Rick On Fri, Jan 4, 2019 at 3:41 PM Rick McGuire wrote: > H, this debug information doesn't make sense for a couple of reasons. > First of all, if rexximage was hanging this way, then the

Re: [Oorexx-devel] Building ooRexx with Debug

The build types as defined by CMAKE provide as a courtesy to the developer A set of predefined flags for the compiler and the linker CMAKE_C_FLAGS='' CMAKE_C_FLAGS_DEBUG='-g' CMAKE_C_FLAGS_MINSIZEREL='-Os -DNDEBUG' CMAKE_C_FLAGS_RELEASE='-O3 -DNDEBUG' CMAKE_C_FLAGS_RELWITHDEBINFO='-O2 -g

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

H, this debug information doesn't make sense for a couple of reasons. First of all, if rexximage was hanging this way, then the build would never complete...but it does complete, so something else strange has to be going on. Secondly, rexximage is completely single threaded, so it should never

Re: [Oorexx-devel] Building ooRexx with Debug

I think this is related to the question "Questions ad differences between "RELEASE", "DEBUG" and "RELWITHDEBUGINFO" on Windows?“ asked by Rony 4 Dec 2018, It would be most welcome to have this clarified on all platforms (what switches and where do they interact with the build process). I have

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

I have added further debug info in my dropbox https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0 I did a new run on a newly booted machine running (freshly installed) macOS Mojave so there should

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

Sorry, it seems tmpnam is not there any more in the code base? I see tempnam instead, but also that function is deprecated. -> forget about my remark. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 04.01.2019 um 18:47 schrieb P.O. Jonsson : > > No, it arrives for any kind of

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

No, it arrives for any kind of build, Erich saw it first on the Jenkins slave and it piled up also there before the upgrade to Mojave so not related to the OS specifically. I sent a feedback on that some time ago. The build continues to finish so I did not think about it any further. I am more

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

The symptom dump says; 2854 ClientMessage::send() (in librexxapi.5.0.0.dylib) + 18 [0x104b99f12] 2854 LocalAPIManager::getInstance() (in librexxapi.5.0.0.dylib) + 19 [0x104b9a093] 2854

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

I´m not sure how rexximage processes could be present without the build hanging. The only thing I can think of is that rexximage will launch rxapi, which involves a fork operation. But that process should then immediately become the rxapi process. Rick On Fri, Jan 4, 2019 at 11:59 AM Enrico

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

Very little to look at , Tempnam is on the road of being deprecated also by gcc On fedora 29 rexxutil.cpp:(.text+0x14e): warning: the use of `tempnam' is dangerous, better use `mkstemp' gcc --version gcc (GCC) 8.2.1 20181215 (Red Hat 8.2.1-6) The only problem with mkstemp is that it returns

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

Hi P.O., the compilation time warnings are unrelated to the rexximage issue. We will look into it and will let you know. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

This is on my own Mac running High Sierra, but the Jenkins machine running Mojave has the same problem. Not sure when it arrived but Erich told me he had seen it before as well. Grep below + I added a analysis of the process Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se Am 04.01.2019 um

Re: [Oorexx-devel] Lingering RexxImage process during make process on Mac

this is when rexximage runs: > > > [ 89%] Building CXX object > CMakeFiles/rexximage.dir/utilities/rexximage/rexximage.cpp.o > [ 89%] Linking CXX executable bin/rexximage > [ 89%] Built target rexximage the messages after that are very probably not relevant. Are these jenkins builds or

[Oorexx-devel] Lingering RexxImage process during make process on Mac

I now have a rexximage process left after in principle every build on macOS, both on High Sierra and on Mojave. This is where it happens in the „make“ process I think: Scanning dependencies of target rexximage [ 89%] Building CXX object

[Oorexx-devel] Building ooRexx with Debug

I have been writing a MAC version of the WIKI text found here and I am almost done. I have found what I think is a typo in the text for Windows and Ubuntu. In the sections CMake and

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

Dear P.O.: On 04.01.2019 14:26, P.O. Jonsson wrote: > What about this statement that I have seen in some installers, is it still > necessary/valid=? > > export NLSPATH=$REXXPATH/bin/rexx.cat:$NLSPATH No, this has been fixed in the meantime. ---rony

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

What about this statement that I have seen in some installers, is it still necessary/valid=? export NLSPATH=$REXXPATH/bin/rexx.cat:$NLSPATH REXXPATH is the path to the installation, i.e. ~/Applications/ooRexx5.0.0 Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 03.01.2019 um