From: trcrsired <oyzawqgcfc@gmail.com>
To: binutils@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: [PATCH 0/1] Support building binutils-gdb for an Android (bionic) host
Date: Thu, 29 Oct 2026 20:41:16 +0800 [thread overview]
Message-ID: <20261029124117.13519-1-oyzawqgcfc@gmail.com> (raw)
This patch makes binutils-gdb build with --host=aarch64-linux-android30
against bionic: PATH_MAX is taken from <linux/limits.h>, UINTPTR_WIDTH no
longer relies on __UINTPTR_WIDTH__, _FORTIFY_SOURCE is not enabled for
C++, gdbserver auto-detects the auxv types, and gprofng is skipped on
Android.
The two gnulib/import edits are direct modifications. If they must go
through update-gnulib.sh, I can rework them as a gnulib patch.
trcrsired (1):
Support building binutils-gdb for an Android (bionic) host
configure | 2 +-
configure.ac | 2 +-
gdbserver/configure | 17 +----------------
gdbserver/configure.ac | 23 ++++++-----------------
gdbsupport/common-defs.h | 2 +-
gnulib/import/pathmax.h | 8 ++++++++
gnulib/import/rawmemchr.c | 8 +++++++-
include/libiberty.h | 8 ++++++++
8 files changed, 33 insertions(+), 37 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-29 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 12:41 trcrsired [this message]
2026-10-29 12:41 ` [PATCH 1/1] " trcrsired
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=20261029124117.13519-1-oyzawqgcfc@gmail.com \
--to=oyzawqgcfc@gmail.com \
--cc=binutils@sourceware.org \
--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