Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/python] Fix check-include-guards check in python-limited-api-missing.h
Date: Fri, 15 May 2026 14:16:19 +0200	[thread overview]
Message-ID: <20260515121619.2499254-1-tdevries@suse.de> (raw)

The check-include-guards check fails for
gdb/python/python-limited-api-missing.h:
...
check-include-guards....................................................Failed
- hook id: check-include-guards
- exit code: 1

gdb/python/python-limited-api-missing.h:22: wrong symbol in ifndef
...

Fix this by using GDB_PYTHON_PYTHON_LIMITED_API_MISSING_H instead of
GDB_PYTHON_LIMITED_API_MISSING_H.
---
 gdb/python/python-limited-api-missing.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gdb/python/python-limited-api-missing.h b/gdb/python/python-limited-api-missing.h
index 07882ca1cf2..40359abf337 100644
--- a/gdb/python/python-limited-api-missing.h
+++ b/gdb/python/python-limited-api-missing.h
@@ -19,8 +19,8 @@
    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
 
-#ifndef GDB_PYTHON_LIMITED_API_MISSING_H
-#define GDB_PYTHON_LIMITED_API_MISSING_H
+#ifndef GDB_PYTHON_PYTHON_LIMITED_API_MISSING_H
+#define GDB_PYTHON_PYTHON_LIMITED_API_MISSING_H
 
 #ifdef Py_LIMITED_API
 extern "C"
@@ -59,4 +59,4 @@ PyAPI_FUNC(int) PyRun_InteractiveLoop (FILE *f, const char *p);
 }
 #endif /* Py_LIMITED_API */
 
-#endif /* GDB_PYTHON_LIMITED_API_MISSING_H */
+#endif /* GDB_PYTHON_PYTHON_LIMITED_API_MISSING_H */

base-commit: 8f65ab7b71f12def1934ed0c296eef441198b4fa
-- 
2.51.0


                 reply	other threads:[~2026-05-15 12:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260515121619.2499254-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@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: link
Be 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