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 <rony.flatsc...@wu.ac.at>
wrote:

> 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 "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
> with a core dump. The libraries seem to be found.
>
> This is with r11665.
>
> ---rony
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to