Better CFLAGS and LDFLAGS about charybdis

[kaniini]

Macros which begin with an underscore are reserved specifiers. _FORTIFY_SOURCE is linux-specific, and is not available on all libcs, notably glibc/ia64 has incomplete support. Declaring _FORTIFY_SOURCE can cause link-time problems.

Thusly, NAK.

[cmouse]

So. You just refused all suggested CFLAGS and LDFLAGS because of _FORTIFY_SOURCE? Also, itthese can be detected using pretty simple autoconf macros, so that they won't be used if they cause problems. Having these when possible will increase code security.

[kaniini]

If you want these you can customize the build yourself. The goal of the build system we provide is to be portable to a number of operating systems. NAK stands.

[cmouse]

So you use configure, but don't know how to use it to test whether particular compiler/linker flag is accepted or not? Or you just don't want to do this, which is better reason than "portability" in any case. Those tests are not hard to write, and I see you actually have those. So your excuses here about portability are pretty funny, since your configure scripts could already test all except the read-only GOT tables. But thanks for the replies though.