Re: [Oorexx-devel] [oorexx:code-0] New commit [r11653] by bigrixx

2019-01-14 Thread Rony
Am 14.01.2019 um 18:51 schrieb Erich Steinböck : >> cleaning the build directory with "rm -rf *" > Rony, I never remove the build directory. If I want to run a clean CMake, I > use `rm CMakeCache.txt` Very interesting, thank you very much, Erich! —-rony _

Re: [Oorexx-devel] [oorexx:code-0] New commit [r11653] by bigrixx

2019-01-14 Thread Erich Steinböck
> > cleaning the build directory with "rm -rf *" Rony, I never remove the build directory. If I want to run a clean CMake, I use `rm CMakeCache.txt` ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/list

Re: [Oorexx-devel] [oorexx:code-0] New commit [r11653] by bigrixx

2019-01-14 Thread Erich Steinböck
> > Since you have access to the different build machines, can you make this > change? Does this remove the need for the Clang change? I just committed CMake changes for C++11. I've also removed the two CLANG-specific set lines as a test compile on macOS 10.14 runs fine without them.

Re: [Oorexx-devel] [oorexx:code-0] New commit [r11653] by bigrixx

2019-01-14 Thread Rony G. Flatscher
Just tested that: MacOS builds Linux gcc gets an error during compilation. ---rony P.S.: While cleaning the build directory with "rm -rf *" I mistakingly deleted my  home directory "~" so I will not be able to create builds for ooRexx or BSF4ooRexx for Linux 32- and 64-bit. :-( [As I alotted t