On 19.02.2021 15:28, rvjan...@xs4all.nl wrote:
> Ok, will add it to the path like P.O. suggested and hope that it works. Or
> will copy it after the build. I think it tests the install process and not
> the working of the interpreter.
You can test the existence of rexxtry.rex next to rexx[.exe] by something like
e.g.
self~assertTrue(SysFileExists(filespec("location",.rexxinfo~executable)||"rexxtry.rex"))
---rony
>> On 19 Feb 2021, at 14:55, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote:
>>
>> On 18.02.2021 15:49, René Jansen wrote:
>>> There is currently only one test case failing on the Linux on Z Rockhopper,
>>> which is the test for the reachability of RexxTry. This is because this is
>>> the uninstalled version of ooRexx - the so-called USB version. I expect
>>> this to fail on other machines where we do not do an install, because
>>> RexxTry has not been copied from samples to the $PATH.
>>>
>>> I want to remove this test, does anyone oppose?
>> hmm, as "rexxtry.rex" has *always* been put into the location where the
>> executable rexx[.exe]
>> resided I would regard this a bug in the USB version you used which should
>> place "rexxtry.rex" next
>> to rexx[.exe]. As such the test unveiled this error and I would keep it! :)
>>
>> ---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
