From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [gdb/build] Fix building gdb.pot
Date: Sun, 7 Jun 2026 09:23:26 +0200 [thread overview]
Message-ID: <20260607072326.484320-1-tdevries@suse.de> (raw)
Since commit 8708a20e2bb ("gdb: store gdbtk object files into their sources
directory"), building gdb.pot is broken.
The commit added gdbtk/generic to CONFIG_SRC_SUBDIR, and building gdb.pot
breaks because the directory doesn't exist.
Fix this by ignoring the dir while building gdb.pot.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34212
---
gdb/Makefile.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index b2b7ef3d606..2349ef7fbdf 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -2697,7 +2697,7 @@ po/$(PACKAGE).pot: force
-test -d po || mkdir po
sh -e $(srcdir)/po/gdbtext $(XGETTEXT) $(PACKAGE) . $(srcdir) \
$(srcdir)/../gdbsupport $(srcdir)/../gdbserver \
- $(addprefix $(srcdir)/,$(CONFIG_SRC_SUBDIR))
+ $(addprefix $(srcdir)/,$(filter-out gdbtk/generic, $(CONFIG_SRC_SUBDIR)))
#
base-commit: 4562eab73d375e57f3c5a67f62d2678d7730d7ab
--
2.51.0
next reply other threads:[~2026-06-07 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 7:23 Tom de Vries [this message]
2026-06-09 16:49 ` Tom Tromey
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=20260607072326.484320-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