Compile failure due to FORTIFY_SOURCE #61
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The unconditional use of -D_FORTIFY_SOURCE=2 can lead to compile failures on older systems. It is also unclear why this should be unconditionally turned on. I would recommend removing it from Makefile.in, if you want it you can always specify it via CFLAGS/CPPFLAGS.
Example output of a failed built on an Itanium machine:
-D_FORTIFY_SOURCE=2
is added for security reasons. On some libc's it uses substitute functions which are more secure. It shouldn't have this sort of effect.I know what you are trying to achieve. Still, underscore-capital letter names are reserved. Portable code must either not use them, or use autoconf tests to determine if the compiler (and libc in this case) supports them.
William Pitcock notifications@github.com wrote:
Sent from Kaiten Mail for Android. Please excuse my brevity.