10-18-2017, 05:22 PM
Hello, welcome to the forum.
I don't think Cuberite itself sets that flag, it seems it's coming from your OS / compiler by default. From what I've read, you could simply override it with `-fstack-protector-none` or `-fstack-protector-all`.
Do an `echo $CFLAGS` and `echo $CXXFLAGS` on your command line, inspect if the bad flag is listed; if so, have a look where it could be set - usually in ~/.profile, ~/.bashrc or similar. Remove it from there, log in in a new session and try again.
Alternatively, it should be possible to do something like `CFLAGS="$CFLAGS -fstack-protector-none" CXXFLAGS="$CXXFLAGS -fstack-protector-none" cmake <cuberitedir>` when configuring Cuberite for the first time.
Note that I'm not too familiar with Linuxes, so the commands I gave you might need some tweaking.
I don't think Cuberite itself sets that flag, it seems it's coming from your OS / compiler by default. From what I've read, you could simply override it with `-fstack-protector-none` or `-fstack-protector-all`.
Do an `echo $CFLAGS` and `echo $CXXFLAGS` on your command line, inspect if the bad flag is listed; if so, have a look where it could be set - usually in ~/.profile, ~/.bashrc or similar. Remove it from there, log in in a new session and try again.
Alternatively, it should be possible to do something like `CFLAGS="$CFLAGS -fstack-protector-none" CXXFLAGS="$CXXFLAGS -fstack-protector-none" cmake <cuberitedir>` when configuring Cuberite for the first time.
Note that I'm not too familiar with Linuxes, so the commands I gave you might need some tweaking.