On 10/1/2016 2:44 AM, Hankins, Jonathan wrote:
So I've narrowed it down. If I build from Debian's patched source, but
run ./configure myself, my flags in config.out look like:
Compiler flags: -g -O2 -Wall -fno-strict-aliasing
-fno-exceptions -fno-rtti
Linker flags:
However, if I build using debian's rules file, my flags in config.out
look like:
Compiler flags: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -fno-strict-aliasing -fno-exceptions -fno-rtti
-fno-strict-aliasing -fno-exceptions -fno-rtti
Linker flags: -Wl,-Bsymbolic-functions -Wl,-z,relro
Years ago I ran into a situation with building Bacula RPMS when RedHat
started adding -D fortify-source to CFLAGS by default. This would cause
'buffer overflow detected' errors even though what Bacula was doing in
the code was perfectly safe. It just didn't match what GCC's detection
code expected. The answer was to override RedHat's RPM macro additions
with user-defined macros and build using the CLFAGS that Bacula's
configure creates. I'm not so familiar with Debian packaging, but I'm
sure there must be a way to override the default rules so that Bacula
can be built with a proper CFLAGS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users