From: Sam James <sam@gentoo.org>
Date: Sun, 13 Oct 2024 22:22:02 +0000 (+0100)
Subject: libstdc++: testsuite: adjust name_fortify test for pre-defined _FORTIFY_SOURCE
X-Git-Tag: basepoints/gcc-16~5249
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=90a4851b08270678352f4f53f86d94af78647499;p=thirdparty%2Fgcc.git

libstdc++: testsuite: adjust name_fortify test for pre-defined _FORTIFY_SOURCE

Otherwise we get failures with toolchains that have _FORTIFY_SOURCE
defined already to a different value like 3.

libstdc++-v3/ChangeLog:

	* testsuite/17_intro/names_fortify.cc: Undefine _FORTIFY_SOURCE.
---

diff --git a/libstdc++-v3/testsuite/17_intro/names_fortify.cc b/libstdc++-v3/testsuite/17_intro/names_fortify.cc
index c975412074b..f24af21f8a7 100644
--- a/libstdc++-v3/testsuite/17_intro/names_fortify.cc
+++ b/libstdc++-v3/testsuite/17_intro/names_fortify.cc
@@ -1,6 +1,7 @@
 // { dg-do compile { target *-*-linux* } }
 // { dg-add-options no_pch }
 
+#undef _FORTIFY_SOURCE
 #define _FORTIFY_SOURCE 2
 // Now we can define the macros to poison uses of non-reserved names:
 #include "names.cc"