public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org, "Vineet Gupta" <vineetg@rivosinc.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Carlos O'Donell" <carlos@redhat.com>
Subject: [PATCH v2 0/3] Refactor binutils configure usage
Date: Tue,  6 Dec 2022 13:02:40 -0300	[thread overview]
Message-ID: <20221206160243.455627-1-adhemerval.zanella@linaro.org> (raw)

This patchset allows user to override all used binutils tools (ld, ar,
objcopy, gprof, nm, objdump, and readel), and remove unused options
for build-many-glibcs.py.

Adhemerval Zanella (3):
  configure: Allow user override LD, AR, OBJCOPY, and GPROF
  configure: Move nm, objdump, and readelf to LIBC_PROG_BINUTILS
  scripts/build-many-glibcs.py: Remove unused RANLIB and STRIP option

 aclocal.m4                   |  28 +++-
 configure                    | 311 +++--------------------------------
 configure.ac                 |   4 -
 scripts/build-many-glibcs.py |   8 -
 4 files changed, 51 insertions(+), 300 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-12-06 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 16:02 Adhemerval Zanella [this message]
2022-12-06 16:02 ` [PATCH v2 1/3] configure: Allow user override LD, AR, OBJCOPY, and GPROF Adhemerval Zanella
2023-01-11 20:25   ` Carlos O'Donell
2022-12-06 16:02 ` [PATCH v2 2/3] configure: Move nm, objdump, and readelf to LIBC_PROG_BINUTILS Adhemerval Zanella
2022-12-06 18:48   ` Adhemerval Zanella Netto
2023-01-11 20:30   ` Carlos O'Donell
2022-12-06 16:02 ` [PATCH v2 3/3] scripts/build-many-glibcs.py: Remove unused RANLIB and STRIP option Adhemerval Zanella
2023-01-11 20:28   ` Carlos O'Donell

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=20221206160243.455627-1-adhemerval.zanella@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=ludo@gnu.org \
    --cc=vineetg@rivosinc.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).