Closed EeveeEuphoria closed 1 year ago
That SIGABRT signal issue occurs, if I compiled v2.1.12 pre-3 on my Gentoo, Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, so likely the issue is with the game's code that affects some Linux distributions. This needs to be reported to developers of SRB2. Not sure, if this is the same case when I got SIGABRT with SRB2 rphys, which I informed author of the build in SRB2 MB.
You can try to use one workaround with CFLAGS="-D_FORTIFY_SOURCE=0"
when entering this as compilation flag in srb2bld for the time being, but probably not recommended in the long run.
i see, i talked about this in the SRB2 discord, and when i'm not busy dealing with data recovery (oops), i'll spin up an ubuntu VM to recreate this and submit relevant logs
Just an update, RC1 is out and that seems to compile fine; katsy was able to fix up the issues from pre3 up to RC1!
I can confirm that it compiles and runs successfully with RC1 for Gentoo, Ubuntu 18.04 LTS and Ubuntu 20.04 LTS.
I'm wholly unsure why this doesn't compile, since it compiles just fine on opensuse, and someone else's machine (not with srb2bld), using the docker found in the commit https://github.com/Bijman/srb2bld/commit/6c34f0284a1452a8eded08d7bd02699e58aa9989
Here's a crash log: crash-log.txt And maybe some relevant compiler errors: message.txt