Hi Erich, I did not expect any problems from the ooRexx side ;-) this was only the first run of the complete toolchain.
I will go after emxomfld.exe and spawnvp then and see where they are used. I can see that the OS is detected as i386 whereas I have some of the tools as i686 (newer hardware as it is branded) I will let you know if I have further progress. This might not be the right place to post but my hunch was that there are a lot of OS/2 foxes monitoring this list so… The initial lines of CMakeOutput.log looks promising though: The system is: OS2 - - i386 Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded. Compiler: C:/USR/BIN/cc.exe Build flags: Id flags: -c The output was: 0 Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "CMakeCCompilerId.o" The C compiler identification is GNU, found in "C:/workspace/oorexxbuild/CMakeFiles/3.15.3/CompilerIdC/CMakeCCompilerId.o" Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded. Compiler: C:/USR/BIN/c++.exe Build flags: Id flags: -c The output was: 0 Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 30.10.2020 um 11:10 schrieb Erich Steinböck <erich.steinbo...@gmail.com>: > > Hi P.O., > cc.exe: schwerwiegender Fehler: Øemxomfld.exeÆ kann nicht ausgefÅhrt > werden: spawnvp: No such file or directory > to me ths clearly looks like an OS/2 tool chain issue and not something that > can be fixed from ooRexx's side. > > > > _______________________________________________ > 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
