From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/3] [gdb] Use --data-directory in gdb_buildall.sh
Date: Sun, 30 Aug 2026 20:12:47 +0200 [thread overview]
Message-ID: <20260830181249.1492948-2-tdevries@suse.de> (raw)
In-Reply-To: <20260830181249.1492948-1-tdevries@suse.de>
I tried to run gdb/gdb_buildall.sh, but ran into errors due to
gdb being used without --data-directory option.
Add this.
---
gdb/gdb_buildall.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/gdb_buildall.sh b/gdb/gdb_buildall.sh
index 1b82455ed0e..65935ae10b2 100644
--- a/gdb/gdb_buildall.sh
+++ b/gdb/gdb_buildall.sh
@@ -202,7 +202,7 @@ cat <<EOF > arch
set architecture
quit
EOF
-./gdb/gdb --batch -nx -x arch 2>&1 | cat > gdb_archs
+./gdb/gdb --data-directory gdb/data-directory --batch -nx -x arch 2>&1 | cat > gdb_archs
tail -n 1 gdb_archs | sed 's/auto./\n/g' | sed 's/,/\n/g' | sed 's/Requires an argument. Valid arguments are/\n/g' | sed '/^[ ]*$/d' > arch
mv arch gdb_archs
@@ -226,7 +226,7 @@ EOF
log_file=$target.log
log_file=${log_file//:/_}
echo -n "... ${target}"
- ./gdb/gdb -batch -nx -x x 2>&1 | cat > $log_file
+ ./gdb/gdb --data-directory gdb/data-directory -batch -nx -x x 2>&1 | cat > $log_file
# Check GDBs results
if test ! -s $log_file
then
--
2.51.0
next prev parent reply other threads:[~2026-08-30 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 18:12 [PATCH 0/3] [gdb] Three gdb_buildall.sh fixes Tom de Vries
2026-08-30 18:12 ` Tom de Vries [this message]
2026-08-30 18:12 ` [PATCH 2/3] [gdb] Fix warnings in gdb_buildall.sh Tom de Vries
2026-08-30 18:12 ` [PATCH 3/3] [gdb] Make gdb_buildall.sh shellcheck-clean Tom de Vries
2026-08-31 7:45 ` Tom de Vries
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=20260830181249.1492948-2-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