[Oorexx-devel] Time for the *ix users to pitch in.

I think the *ix version of this code rework is ready for somebody to try compiling it (I expect there probably will be a few errors). The code is located at: https://svn.code.sf.net/p/oorexx/code-0/sandbox/rick/rxapi I also took a crack at removing the rxapi daemon installation from the deb and r

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> On 28 Nov 2018, at 13:23, Rick McGuire wrote: > > https://svn.code.sf.net/p/oorexx/code-0/sandbox/rick/rxapi > Just tried it , got [ 6%] Building CXX object CMakeFiles/rexxapi.dir/rexxapi/client/platform/unix/SysLocalAPIManage

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Thanks, fixes checked in. Rick On Wed, Nov 28, 2018 at 7:32 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > > > On 28 Nov 2018, at 13:23, Rick McGuire wrote: > > https://svn.code.sf.net/p/oorexx/code-0/sandbox/rick/rxapi > > > > Just tried it , got > > [ 6%

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> On 28 Nov 2018, at 13:42, Rick McGuire wrote: > > Thanks, fixes checked in. > > Rick > > On Wed, Nov 28, 2018 at 7:32 AM Enrico Sorichetti via Oorexx-devel > > wrote: SysCSSStream.cpp and CSSStream naming mismatch Used the right name but got m

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> > I don't have access to any linux systems now > Rick, if you'd like so, I can give you access to an Ubuntu VM that is used for ooRexx Jenkins builds, It's already fully set up for building. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.n

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Nope, I don't do remote access for debugging. Rick On Wed, Nov 28, 2018 at 8:47 AM Erich Steinböck wrote: > I don't have access to any linux systems now >> > Rick, if you'd like so, I can give you access to an Ubuntu VM that is used > for ooRexx Jenkins builds, > It's already fully set up for b

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Hmmm, I was able to fix a couple of the errors here, but the bulk of them are quite puzzling. The types in question are all defined in SysCSStream.hpp, which is included in the .cpp file. Even more puzzling, there are references to types defined in CSStream.hpp, which is NOT included in the .cpp so

Re: [Oorexx-devel] Time for the *ix users to pitch in.

closesocket -> close [ 0%] Generating rxsubcom.1.gz [ 0%] Built target rxsubcom_man [ 0%] Building CXX object CMakeFiles/rexxapi.dir/rexxapi/common/platform/unix/SysCSStream.cpp.o /home/moritz/dev/repos/oorexx/rxapi/rexxapi/common/platform/unix/SysCSStream.cpp: In member function ‘virtual bool

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Thanks, most of these should be fixed but a couple of the errors puzzled me. Let's see if they go away. Rick ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Here from Ubuntu, rev 11534: [ 0%] Generating rxsubcom.1.gz [ 0%] Built target rxsubcom_man [ 0%] Building CXX object CMakeFiles/rexxapi.dir/rexxapi/common/platform/unix/SysCSStream.cpp.o /home/rony/dev/oorexx-code-0/sandbox/rick/rxapi/rexxapi/common/platform/unix/SysCSStream.

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Another alternative would be a Docker image on your local windows box; I can set up a development image for your sandbox in half an hour or so. René. > On 28 Nov 2018, at 09:48, Rick McGuire wrote: > > Nope, I don't do remote access for debugging. > > Rick > > On Wed, Nov 28, 2018 at 8:47 A

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Also not going to happen. I'm not a Linux user, I don't like the tooling on the system (editors, debuggers, etc.) If this is going to be done, it will be because the community of people who do run on those systems help to make it happen, not because I am expected to do all of the work. Rick On We

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Revision 11535l, Ubuntu: [ 0%] Generating rxsubcom.1.gz [ 0%] Built target rxsubcom_man [ 0%] Building CXX object CMakeFiles/rexxapi.dir/rexxapi/common/platform/unix/SysCSStream.cpp.o /home/rony/dev/oorexx-code-0/sandbox/rick/rxapi/rexxapi/common/platform/unix/SysCSStream.cpp:

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> On 28 Nov 2018, at 16:32, Rick McGuire wrote: > > Also not going to happen. I'm not a Linux user, I don't like the tooling on > the system (editors, debuggers, etc.) If this is going to be done, it will be > because the community of people who do run on those systems help to make it > happ

Re: [Oorexx-devel] Time for the *ix users to pitch in.

On Wed, Nov 28, 2018 at 10:48 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > > > On 28 Nov 2018, at 16:32, Rick McGuire wrote: > > Also not going to happen. I'm not a Linux user, I don't like the tooling > on the system (editors, debuggers, etc.) If this is g

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Hi Enrico, thanks, I did not know that. Before I attempt it, I will setup a job on our build Jenkins that builds the sandbox. best regards, René. > On 28 Nov 2018, at 11:47, Enrico Sorichetti via Oorexx-devel > wrote: > > > >> On 28 Nov 2018, at 16:32, Rick McGuire >

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Great! Looking at the changes I noticed the socket is created in $HOME. I think we should use HOME only as a fall-back if the proper location is not available. The proper location is specified by the XDG spec [1] to be $XDG_RUNTIME_DIR. That way the socket cannot leak to other users because permiss

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Should compile without error with latest commit. There's still a link error that needs to be resolved. I checked the rexxapi libray definition in CMakeLists.txt, but couldn't figure out what's wrong. ~~~ bin/librexxapi.so.5.0.0: undefined reference to `SysServerLocalSocketConnectionManager::userSe

Re: [Oorexx-devel] Time for the *ix users to pitch in.

rev 11537, Ubuntu: [ 0%] Generating rxsubcom.1.gz [ 0%] Built target rxsubcom_man [ 7%] Built target rexxapi [ 71%] Built target rexx [ 72%] Building CXX object CMakeFiles/rxapi.dir/rexxapi/server/platform/unix/linux/APIService.cpp.o /home/rony/dev/oorexx-code-0/sandbo

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Same on apple High Sierra > On 28 Nov 2018, at 18:35, Erich Steinböck wrote: > > Should compile without error with latest commit. > There's still a link error that needs to be resolved. I checked the rexxapi > libray definition in CMakeLists.txt, but couldn't figure out what's wrong. > ~~~ >

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Forgot to mention: I always wipe out the working directory such that no old artefacts remain and such that the CMake files get created from scratch. ---rony On 28.11.2018 18:48, Rony G. Flatscher wrote: > > rev 11537, Ubuntu: > > [ 0%] Generating rxsubcom.1.gz > [ 0%] Built target rxs

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Further down it specifies that "it is mandatory that the directory continues to exist from his first login to his last logout on the system, and not removed in between." I would argue that as long as the daemon is running in the background the user is not fully logged out. At least this is how scre

Re: [Oorexx-devel] Time for the *ix users to pitch in.

The link error and Rony's compile errors should be resolved now. Rick On Wed, Nov 28, 2018 at 12:36 PM Erich Steinböck wrote: > Should compile without error with latest commit. > There's still a link error that needs to be resolved. I checked the > rexxapi libray definition in CMakeLists.txt,

Re: [Oorexx-devel] Time for the *ix users to pitch in.

I'm hoping all of those MUST items are the responsibility of the OS and not the application using that directory. Am I correct in understanding that $XDG_RUNTIME_DIR is the user-specific directory, so all I need to do is place the socket file there? Rick On Wed, Nov 28, 2018 at 1:20 PM Moritz Hof

Re: [Oorexx-devel] Time for the *ix users to pitch in.

I checked it on my machine and it does indeed point to a user-specific directory where the user id is one segment of the path. Moritz On Wed, Nov 28, 2018 at 9:31 PM Rick McGuire wrote: > > I'm hoping all of those MUST items are the responsibility of the OS and not > the application using that di

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> > The link error and Rony's compile errors should be resolved now. > With the latest commit, this builds without error and successfully runs all tests on Ubuntu 16.04 ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourcef

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> > I checked it on my machine and it does indeed point to a user-specific > directory where the user id is one segment of the path. Same here on Ubuntu. $XDG_RUNTIME_DIR resolves to /run/user/1000 which is a directory with the required 0700 access permission. _

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Wow, really? I have to admit that was somewhat unexpected! One thing that needs to be checked out is what happens if a second version of rxapi gets launched. You can test this by just issuing the rxapi command and checking the return code. I was a little uncertain on what the expected result would

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Apple High Sierra The build was successful Started the test suite , but [enrico@enrico-imac ooRexx.tests.svn]$rexx testOORexx.rex -s -X native_api Searching for test containers... Executing automated test suite Executing tests from .../enrico/ooRexx.tests.svn/ooRexx/SimpleTests.testGroup Execut

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Well, I'm not familiar with the debuggers on a Mac, but use one to find out the location of the exception and get a stack trace would be a good starting point. Rick On Wed, Nov 28, 2018 at 4:06 PM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > Apple High Sierra

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Dear Enrico, You could try to make a debug build and then use Valgrind I think you can get it via Homebrew. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 28.11.2018 um 22:10 schrieb Rick McGuire : > > Well, I'm not familiar with the debuggers on a

Re: [Oorexx-devel] Time for the *ix users to pitch in.

First attempt with a script I wrote [enrico@enrico-imac zz]$lldb -- rexx unxmit FILE206.xmi (lldb) target create "rexx" Current executable set to 'rexx' (x86_64). (lldb) settings set -- target.run-args "unxmit" "FILE206.xmi" (lldb) run Process 4488 launched: '/Users/enrico/rxapi/bin/rexx' (x86_

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Me, no...but perhaps someone else does. Rick On Wed, Nov 28, 2018 at 5:23 PM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > First attempt with a script I wrote > > > [enrico@enrico-imac zz]$lldb -- rexx unxmit FILE206.xmi > (lldb) target create "rexx" > Current

Re: [Oorexx-devel] Time for the *ix users to pitch in.

And here is the backtrace for the same situations My script [enrico@enrico-imac zz]$lldb -- rexx unxmit file206.xmi (lldb) target create "rexx" Current executable set to 'rexx' (x86_64). (lldb) settings set -- target.run-args "unxmit" "file206.xmi" (lldb) r Process 4908 launched: '/Users/enri