The current git version of 8.0, but it has been this way for at least the past two months, works fine for me as long as I remove all *.o files from the installed version.
If I do not do that, it crashes right away with a segmentation fault. It does not matter if I compile it with gcc 6, 7 or 8. Same result.
Is that just on my system, or is this a generic .o file dumping problem in pike 8.0?
I regularly compile with: --with-cdebug --without-rtldebug --without-valgrind --with-double-precision --with-long-int --disable-noopty-retry --with-machine-code --without-portable-bytecode -g -O2
on an amd64 linux system (devel2, to be exact, from pikefarm).
Stephen R. van den Berg wrote:
I regularly compile with: --with-cdebug --without-rtldebug --without-valgrind --with-double-precision --with-long-int --disable-noopty-retry --with-machine-code --without-portable-bytecode -g -O2
Incidentally, on the very same system, I compile 8.1 with the exact same settings, and it compiles/runs without issues (without removing all precompiled .o files).
Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
I regularly compile with: --with-cdebug --without-rtldebug --without-valgrind --with-double-precision --with-long-int --disable-noopty-retry --with-machine-code --without-portable-bytecode -g -O2
Incidentally, on the very same system, I compile 8.1 with the exact same settings, and it compiles/runs without issues (without removing all precompiled .o files).
Am I the only one that experiences these precompiled file issues on 8.0? If yes, then how about another try at releasing a new Pike 8.0?
pike-devel@lists.lysator.liu.se
-
Stephen R. van den Berg