|
Hello Josh,
Yes, if you build either with -D fortify-source=2 or link with -Bsymbolic-functions, Bacula will
fail. It is best
to stick with the Bacula recommended build options, which is
what you are using.
Also if you have a Bacula version less that 7.4.3 and you build
with GNU C++ 6.0 or greater,
Bacula will not work. This problem is fixed in 7.4.3 and
greater, but the guys committing to
C++ have lost all common sense of the basic function of the C++
compiler that is to correctly
compile the source code written by the author. On multiple
occasions, they now simply elide (drop
or delete) your source code. Consequently, it is likely that
with new C++ compiler we will
run into additional problems, unless we can find a C++ compiler
that respects what the programmer
writes. It is the user's responsibility (or problem) if he/she
adds options that the project
does not use (and often warns against), but when you have rogue
C++ compiler writers, life
gets much more complicated.
Best regards,
Kern
On 10/01/2016 02:11 PM, Josh Fisher wrote:
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
|
------------------------------------------------------------------------------
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
