Hi Erich, thanks ...
1. I understand the .ini problem, I will analyse this file
2. a question has been left:
why does this not work in my rexx-Program
address "" "rexxc" "MyRexxComp.rex" "MyRexxComp.cmp.rex" "-s"
I am really confused by a msg like this *"file MyRexxComp.rex not
found"*, why that?
the Linux-Terminal command* "*rexxc MyRexxComp.rex MyRexxComp.cmp.rex
-s" works,
and the PrimeV39 could be checked + compiled with my Rexx-pgm
LG Franz
Am Do., 18. Mai 2023 um 12:51 Uhr schrieb Erich Steinböck <
erich.steinbo...@gmail.com>:
> Hi Franz,
> rexxc is expected to work the same on Windows and Linux.
> A minor known difference is that on Windows rexxc will accept both /s and
> -s, on Unix only -s is accepted. For best portability always use -s if
> required.
>
> Your MyRexxComp.rex should work as long as the rexx filenames in
> MyRexxComp.ini are specified without any UTF-8 byte-order-mark (BOM, 'EF BB
> BF'x).
> The attached MyRexxComp.ini has a BOM in its first line.
> _______________________________________________
> 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
