Rebuilt ooRexx from trunk:
On 29.11.2018 18:29, Rick McGuire wrote:
> On Thu, Nov 29, 2018 at 12:17 PM Rony G. Flatscher <rony.flatsc...@wu.ac.at
> <mailto:rony.flatsc...@wu.ac.at>> wrote:
... cut ...
> Some remarks on the build process and running the interpreters initially:
>
> * both, the 32- and 64-bit build process will pause at the point where
> the img-file gets
> created; it is necessary to kill the rxapi-process (this despite the
> fact, that no rxapi
> was running when starting the compilation process so assuming that it
> is actually the
> rxapi that just got created)
>
> I just committed changes that should fix that problem.
Indeed!
> * the first time launching "rexxtry.rex" caused a hang on start-up;
> pressing ctl-c and then
> rerun "rexxtry.rex" succeeds;
> o the reason seems to be that the very first time "rxapi" gets started,
> but causes that
> input hang on "rexxtry.rex"; killing "rexxtry.rex" with ctl-c and
> running it immediately
> afterwards works ("rxapi" runs already in this case)
>
> Same issue.
Fixed!
---rony
P.S.: Have to leave so cannot test on Linux and MacOSX, next slot with enough
free time will be
Saturday.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
