Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread René Jansen
Just a note, for all committers, that all platforms will be built on http://build.netrexx.org within half an hour of the commit, so one can see if one inadvertently broke a build for another platform. René. > On 10 Jan 2019, at 09:41, Rick McGuire wrote: > > If the patch had been rejected, it

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rick McGuire
If the patch had been rejected, it would not be by silence. That just means no committer has had the chance to apply it and test it out on the all of the platforms. That's probably going to need to be Erich, since he has access to to more platforms than I do. Rick On Thu, Jan 10, 2019 at 8:37 AM

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rony G. Flatscher
On 10.01.2019 14:30, Rick McGuire wrote: > Why are you removing Enrico's RPATH changes? They seem like a good idea and I > NEVER advocated > against those. My discussion was totally about the appropriate location for > rexx.img. Oh, o.k. As the changes have not been applied to trunk I thought th

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rick McGuire
Why are you removing Enrico's RPATH changes? They seem like a good idea and I NEVER advocated against those. My discussion was totally about the appropriate location for rexx.img. Rick On Thu, Jan 10, 2019 at 8:28 AM Rony G. Flatscher wrote: > On 10.01.2019 12:56, Rick McGuire wrote: > > I have

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rony G. Flatscher
On 10.01.2019 12:56, Rick McGuire wrote: > I have tested exactly the situation on my Linux system, and everything works > fine. But I don't > have your setup, so there's probably something different.  > > I suggest adding a printf() to the SystemInterpreter::loadImage() method (the > second one w

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rick McGuire
I have tested exactly the situation on my Linux system, and everything works fine. But I don't have your setup, so there's probably something different. I suggest adding a printf() to the SystemInterpreter::loadImage() method (the second one with the longer signature) and print out the names it is

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rony G. Flatscher
On 09.01.2019 21:11, Rick McGuire wrote: > This is not an acceptable patch because it imposes a directory structure that > is not necessary and > is not necessarily what will be used on the other platforms. Just make the > simple one-line change > to the CMakeLists.txt file to install rexx.img in

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Rick McGuire
And I view rexx.img and rxapi as a form of "package-private" library rather than one of the main front binaries, which is why it is more appropriate to locate then with the libraries that use them. Rick On Thu, Jan 10, 2019 at 5:48 AM Moritz Hoffmann wrote: > I agree with Rick. The Linux loader

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Moritz Hoffmann
I agree with Rick. The Linux loader can load libs from the system directories and we shouldn't hard-code them using rpath. There is some explanation about other issues with rpath in [1]. Debian only allows rpath for package-private libraries but librexx doesn't really fall into this category. [1]

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-10 Thread Enrico Sorichetti via Oorexx-devel
> On 9 Jan 2019, at 21:11, Rick McGuire wrote: > > This is not an acceptable patch because it imposes a directory structure that > is not necessary and is not necessarily what will be used on the other > platforms. Are You implying that the few thousands packages of the unix like world who

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-09 Thread Rick McGuire
This is not an acceptable patch because it imposes a directory structure that is not necessary and is not necessarily what will be used on the other platforms. Just make the simple one-line change to the CMakeLists.txt file to install rexx.img in the same directory as librexxapi as it intended. Ri

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-09 Thread Rony G. Flatscher
On 08.01.2019 21:57, Rick McGuire wrote: > If you are splitting things up into separate bin and lib directories, then > rexx.img needs to be > co-located with librexxapi in order for the image file to be located without > it being on the path > or the current directory. After generating ooRexx f

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-08 Thread Rick McGuire
If you are splitting things up into separate bin and lib directories, then rexx.img needs to be co-located with librexxapi in order for the image file to be located without it being on the path or the current directory. Rick On Tue, Jan 8, 2019 at 1:21 PM Rony G. Flatscher wrote: > On 08.01.201

Re: [Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-08 Thread Rony G. Flatscher
On 08.01.2019 19:15, Rony G. Flatscher wrote: > > While testing the standalone version on Linux, everything works out fine if > issuing "rexx". > Should have also mentioned: if putting the directory where rexx resides on to the path everything works as well. ---rony > However, if invoking "rex

[Oorexx-devel] A crash (not finding rexx.iimg?) (Re: Experimental "standalone" ooRexx interpreters

2019-01-08 Thread Rony G. Flatscher
While testing the standalone version on Linux, everything works out fine if issuing "rexx". However, if invoking "rexx" with a fully qualified path like: ~/some/path/to-standalone/bin/rexx -e "parse version v; say v" an error "Logic error: no startup image" is raised and ooRexx gets aborted