From: Vineet Gupta <vineetg@rivosinc.com>
To: "Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, "Ludovic Courtès" <ludo@gnu.org>,
"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: [PATCH 0/6] Refactor binutils configure usage
Date: Thu, 5 Jan 2023 13:39:49 -0800 [thread overview]
Message-ID: <1932dd9f-afb1-88d0-8e3e-2f219d6d3802@rivosinc.com> (raw)
In-Reply-To: <759d56e4-486b-bd91-89a7-c0bbf448c280@linaro.org>
Hi Carlos,
On 12/22/22 04:54, Adhemerval Zanella Netto wrote:
>
> On 20/12/22 19:01, Vineet Gupta wrote:
>> Hi Adhemerval,
>>
>> On 12/2/22 11:00, Adhemerval Zanella wrote:
>>> This patchset fixes a long standing issue where some configure checks
>>> are no done with the target binutils, remove some old definitions not
>>> required anymore, remove the AS usage (since it is not used directly),
>>> and allow all binutils tools to be overriden at configure time.
>>>
>>> It should restore the previous behavious while setting OUTPUT_FORMAT
>>> for multilib toolchains. If the uses requires a different binutils
>>> tool as default, it can always override at configure time.
>> As of upstream today, cross builds are still broken for OUTPUT_FORMAT.
>>
>> Thx,
>> -Vineet
> Yeap, we still need someone to help review my v2 [1].
>
> [1] https://patchwork.sourceware.org/project/glibc/list/?series=14999
Can you please help review the patches.
Thx,
-Vineet
next prev parent reply other threads:[~2023-01-05 21:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 19:00 [PATCH 0/6] Refactor binutils configure usage Adhemerval Zanella via Libc-alpha
2022-12-02 19:00 ` [PATCH 1/6] configure: Move locale tools early Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-02 19:00 ` [PATCH 2/6] configure: Remove check if as is GNU Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-02 19:00 ` [PATCH 3/6] configure: Remove check if ld " Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-02 19:00 ` [PATCH 4/6] configure: Remove AS check Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-06 13:45 ` Andreas Schwab via Libc-alpha
2022-12-06 15:59 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-02 19:00 ` [PATCH 5/6] configure: Allow user override LD, AR, OBJCOPY, and GPROF Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-07 20:04 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-02 19:00 ` [PATCH 6/6] configure: Move nm, objdump, and readelf to LIBC_PROG_BINUTILS Adhemerval Zanella via Libc-alpha
2022-12-02 23:10 ` Rajalakshmi Srinivasaraghavan via Libc-alpha
2022-12-06 13:39 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-05 15:57 ` Carlos O'Donell via Libc-alpha
2022-12-20 22:01 ` [PATCH 0/6] Refactor binutils configure usage Vineet Gupta
2022-12-22 12:54 ` Adhemerval Zanella Netto via Libc-alpha
2023-01-05 21:39 ` Vineet Gupta [this message]
2023-01-05 21:54 ` Adhemerval Zanella Netto via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1932dd9f-afb1-88d0-8e3e-2f219d6d3802@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).