public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Fix PR gdb/23835: Don't redefine _FORTIFY_SOURCE if it's already defined Date: Wed, 31 Oct 2018 22:36:00 -0000 [thread overview] Message-ID: <656efb5e2691b2bd29573d9985d20206c47b6927@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 656efb5e2691b2bd29573d9985d20206c47b6927 *** Author: Sergio Durigan Junior <sergiodj@redhat.com> Branch: master Commit: 656efb5e2691b2bd29573d9985d20206c47b6927 Fix PR gdb/23835: Don't redefine _FORTIFY_SOURCE if it's already defined Gentoo has a local GCC patch which always defines _FORTIFY_SOURCE=2. This causes a build problem when building GDB there, because "common/common-defs.h" also defines _FORTIFY_SOURCE=2: CXX gdb.o In file included from ../../gdb/defs.h:28:0, from ../../gdb/gdb.c:19: ../../gdb/common/common-defs.h:71:0: error: "_FORTIFY_SOURCE" redefined [-Werror] #define _FORTIFY_SOURCE 2 <built-in>: note: this is the location of the previous definition cc1plus: all warnings being treated as errors make[2]: *** [Makefile:1619: gdb.o] Error 1 Even though it is questionable whether Gentoo's approach is the correct one: https://jira.mongodb.org/browse/SERVER-29982 https://bugs.gentoo.org/621036 it is still possible for GDB to be a bit more robust here and make sure it just defines _FORTIFY_SOURCE if it hasn't been defined already. This patch does that. Tested by rebuilding and making sure the macro was defined. gdb/ChangeLog: 2018-10-31 Sergio Durigan Junior <sergiodj@redhat.com> PR gdb/23835 * common/common-defs.h: Don't redefine _FORTIFY_SOURCE if it's already defined.
next reply other threads:[~2018-10-31 21:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-31 22:36 sergiodj+buildbot [this message] 2018-10-31 22:31 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-11-01 2:47 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-11-01 3:05 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-11-01 3:47 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-11-01 18:49 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-11-01 18:50 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-11-01 19:11 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot 2018-11-01 19:58 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-11-01 19:58 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-11-01 20:19 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-11-02 18:14 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-11-02 18:39 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " sergiodj+buildbot 2018-11-02 19:09 ` Failures on Ubuntu-Aarch64-m64, " sergiodj+buildbot
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=656efb5e2691b2bd29573d9985d20206c47b6927@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).