search for: _fortify_source

We routinely test the upstream code by running everything under valgrind, and in any case _FORTIFY_SOURCE is usually defined by downstream Linux distros and we can leave the optimization vs safety decision to them. See this bug: https://bugs.gentoo.org/640494 --- m4/guestfs-c.m4 | 6 ------ 1 file changed, 6 deletions(-) diff --git a/m4/guestfs-c.m4 b/m4/guestfs-c.m4 index 932b6de73..3e8642675 10064...

--- configure.ac | 23 ++------------------ m4/ax_add_fortify_source.m4 | 53 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 55 insertions(+), 21 deletions(-) create mode 100644 m4/ax_add_fortify_source.m4 diff --git a/configure.ac b/configure.ac index 8576cae5..c5b63370 100644 --- a/configure.ac +++ b/configure.ac @@ -393,9 +393,7 @@ fi dnl If de...

Just to keep others in loop. This issue has been fixed by following additions in Makefile: CPP.Flags += -U_FORTIFY_SOURCE CPP.Flags += -D_FORTIFY_SOURCE=0 Thanks, Ahmad From: ahmad.hassan at sap.com Sent: 07 January 2013 19:52 To: llvmdev at cs.uiuc.edu Subject: _FORTIFY_SOURCE warnings Hi All, I have modified the Makefile inside llvm/tools/clang and added the following flag: CPP.Flags += -D_FORTIFY_SOURCE=0 Bu...

SSIA Martin Kletzander (2): Don't redefine _FORTIFY_SOURCE Get rid of gnulib error bootstrap | 2 +- configure.ac | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) -- 1.8.3.2

Hi All, I have modified the Makefile inside llvm/tools/clang and added the following flag: CPP.Flags += -D_FORTIFY_SOURCE=0 But when I build clang using 'make' then I get lot of warnings like: <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default] <built-in>:0:0: note: this is the location of the previous definition Is this expected behaviour? Thanks Cheers, Ah...

Hi Erik, similar to what I did for libsndfile, this is to simplify the handling of adding -D_FORTIFY_SOURCE=2. Regards David

..., char *resolved_path) { > ^ > /usr/include/bits/stdlib.h:37:8: note: previous definition is here > __NTH (realpath (const char *__restrict __name, char *__restrict > __resolved)) > I've never seen this before. Looks like bits/stdlib.h gets pulled in only when _FORTIFY_SOURCE is enabled (which causes __USE_FORTIFY_LEVEL > 0). Do you have _FORTIFY_SOURCE set somewhere? Can you try with that not set? Teresa > > [...] > > libomp.so > duplicate symbol __kmp_get_reduce_method in version script > duplicate symbol __kmp_itt_fini_ittlib in version script &...

On Wed, Mar 07, 2007 at 11:45:13AM +0000, richard wrote: > * configure.ac: Add -D_FORTIFY_SOURCE to AM_CXXFLAGS for GCC > builds. According to glibc CVS support for this was added in > October 2004, but it doesn't seem to be documented very well, > other than in features.h. I'd not come across this before, so I had a quick poke around. It's hardly documented *well* in f...

...) { >> ^ >> /usr/include/bits/stdlib.h:37:8: note: previous definition is here >> __NTH (realpath (const char *__restrict __name, char *__restrict __resolved)) > > > I've never seen this before. Looks like bits/stdlib.h gets pulled in only > when _FORTIFY_SOURCE is enabled (which causes > __USE_FORTIFY_LEVEL > 0). Do you have _FORTIFY_SOURCE > set somewhere? I do, it's by default a part of hardening flags on most Linux distros, and I'm just following what the distro packages are built with. > Can you try with that not set? I can try,...

...gt; >> /usr/include/bits/stdlib.h:37:8: note: previous definition is here > >> __NTH (realpath (const char *__restrict __name, char *__restrict > __resolved)) > > > > > > I've never seen this before. Looks like bits/stdlib.h gets pulled in only > > when _FORTIFY_SOURCE is enabled (which causes > > __USE_FORTIFY_LEVEL > 0). Do you have _FORTIFY_SOURCE > > set somewhere? > > I do, it's by default a part of hardening flags on most Linux distros, > and I'm just following what the distro packages are built with. > > > Can you t...

..../../../src/lib-ssl-iostream -I../../../src/lib-http -I../../../src/lib-mail -I../../../src/lib-imap -I../../../src/lib-index -I../../../src/lib-storage -I../../../src/lib-storage/index -I../../../src/doveadm -std=gnu99 -O0 -g -pipe -march=native -mtune=native -ggdb -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -c -o fts-user.lo fts-user.c libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src/lib -I../../....

After figuring out the fault in the configuration step and rebuilding, and then rebuilding again by forcing it with `ninja -k 16`, I managed to build everything but 12 ninja targets. I have to sift through them before I can report more, and I don't don't know if it's small enough to post here, but some of the more interesting errors are:

...18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > I haven't been tracking dovecot-2.3 until now, but I've just given it a quick run, and there are a few things that may need some attention. > > /usr/include/features.h:376:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] > # warning _FORTIFY_SOURCE requires compiling with optimization (-O) Don't use -O0 or use configure --disable-hardening or just ignore it. > The build then fails entirely with this: > > DMODULEDIR=\""/usr/lib64/dovecot...

...dlib.h:37:8: note: previous definition is here >> >> __NTH (realpath (const char *__restrict __name, char *__restrict >> __resolved)) >> > >> > >> > I've never seen this before. Looks like bits/stdlib.h gets pulled in >> only >> > when _FORTIFY_SOURCE is enabled (which causes >> > __USE_FORTIFY_LEVEL > 0). Do you have _FORTIFY_SOURCE >> > set somewhere? >> >> I do, it's by default a part of hardening flags on most Linux distros, >> and I'm just following what the distro packages are built with. >...

...at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> wrote: >> >> I haven't been tracking dovecot-2.3 until now, but I've just given it a quick run, and there are a few things that may need some attention. >> >> /usr/include/features.h:376:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] >> # warning _FORTIFY_SOURCE requires compiling with optimization (-O) > > Don't use -O0 or use configure --disable-hardening or just ignore it. > >> The build then fails entirely with this: >> >> DMODULEDIR=\...

...t of the configure script (i.e., the user hasn't specified anything) and then proceed to set them to the defaults as before. This has been suggested before: https://lists.gnu.org/archive/html/autoconf/2006-04/msg00022.html In addition, I've added a small compile snippet to check whether _FORTIFY_SOURCE is defined, and if so, do not add it to CPPFLAGS. This is mainly due to the fact that Gentoo's GCC has _FORTIFY_SOURCE always enabled, which causes a ton of superfluous redefinition warnings when adding this flag to CPPFLAGS. Finally, I forgot to add one patch from our repo, namely that noinst...

...fails to build, but this seems to be an issue with 3.8.1 (which we're using to build 3.9): /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -Os -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -mtune=atom -march=i586 -fasynchronous-unwind-tables -march=i686 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmi...

...about the python shebangs that do not have a version (files contrib/script/ref*.py -> what is this used for??). When using the DONT_OPTMIZE flag the compiler warns for every single file saying, so it is quite annoying but does not to cause issues: /usr/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]. Anyway, these problems do not happen if you manually build with the simple configure and make commands. Cheers, Patrick Wakano On Fri, 18 Oct 2019 at 11:54, Carlos Chavez <cursor at telecomab.mx> wrote: > They only problem I have fo...

...several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: Bugs fixed in this release: ----------------------------------- * ASTERISK-24032 - Gentoo compilation emits warning: "_FORTIFY_SOURCE" redefined (Reported by Kilburn) * ASTERISK-24225 - Dial option z is broken (Reported by dimitripietro) * ASTERISK-24178 - [patch]fromdomainport used even if not set (Reported by Elazar Broad) * ASTERISK-24019 - When a Music On Hold stream starts it restarts at beginning o...

...several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: Bugs fixed in this release: ----------------------------------- * ASTERISK-24032 - Gentoo compilation emits warning: "_FORTIFY_SOURCE" redefined (Reported by Kilburn) * ASTERISK-24225 - Dial option z is broken (Reported by dimitripietro) * ASTERISK-24178 - [patch]fromdomainport used even if not set (Reported by Elazar Broad) * ASTERISK-22252 - res_musiconhold cleanup - REF_DEBUG reload warnings and ref l...