From: Adhemerval Zanella Netto via Gdb <gdb@sourceware.org>
To: Xi Ruoyao <xry111@xry111.site>, Andrew Pinski <pinskia@gmail.com>,
Carlos O'Donell <carlos@redhat.com>,
Gokhan <kadirgokhann@gmail.com>
Cc: Collin Funk <collin.funk1@gmail.com>,
glibc developers <libc-alpha@sourceware.org>,
gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Tue, 16 Jun 2026 11:59:47 -0300 [thread overview]
Message-ID: <62054d25-48a1-4abb-9bdf-06293d8c065b@linaro.org> (raw)
In-Reply-To: <2491ede013971af47c02258a79de15986c370c10.camel@xry111.site>
On 16/06/26 11:50, Xi Ruoyao wrote:
> On Mon, 2026-06-15 at 20:10 -0300, Adhemerval Zanella Netto wrote:
>> 6. Internal script cleanup
>>
>> This might be a more contentious one, but I think we can reduce our build
>> dependencies by at least rewriting the Perl script to either awk or Python.
>
> Hmm, it seems glibc can already build w/o Perl (if you don't care the
> info pages which need Texinfo). I happened to figure that out after
> forgetting the temporary Perl and Texinfo installations before building
> glibc when I performed a test build of Linux From Scratch manually
> several days ago.
We still install the mtrace, so to use all the glibc features one would
need to install perl. The scripts/test-installation.pl is already gated
through perl existence, but I think it is not a good design if we silent
disable testing due missing tools.
>
> Also reducing the Perl scripts won't help too much for distros as
> Texinfo is still in Perl and the distros will need the info pages
> anyway.
>
I think the main gain is for mtrace, the two other scripts
(test-installation.pl, summary.pl) are not essential. The summary.pl is
only required for manual generation and you put texinfo already brings it
anyway.
next prev parent reply other threads:[~2026-06-16 15:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 19:18 Carlos O'Donell via Gdb
2026-06-12 19:29 ` Andrew Pinski via Gdb
2026-06-12 21:18 ` Carlos O'Donell via Gdb
2026-06-12 21:21 ` Andrew Pinski via Gdb
2026-06-12 23:07 ` Adhemerval Zanella Netto via Gdb
2026-06-12 23:11 ` Andrew Pinski via Gdb
2026-06-15 11:39 ` Mark Wielaard
2026-06-15 21:11 ` Carlos O'Donell via Gdb
2026-06-16 11:03 ` Mark Wielaard
2026-06-16 13:53 ` Carlos O'Donell via Gdb
2026-06-17 16:28 ` Alexandre Oliva via Gdb
2026-06-18 5:27 ` Eli Zaretskii via Gdb
2026-06-18 6:59 ` Alexandre Oliva via Gdb
2026-06-18 7:41 ` Eli Zaretskii via Gdb
2026-06-18 13:43 ` Alexandre Oliva via Gdb
2026-06-18 14:11 ` Eli Zaretskii via Gdb
2026-06-18 14:44 ` Jeffrey Walton via Gdb
2026-06-18 17:11 ` Thomas Dineen via Gdb
2026-06-19 22:21 ` Andy Wang via Gdb
2026-06-16 16:03 ` Siddhesh Poyarekar
2026-06-20 0:09 ` Carlos O'Donell via Gdb
2026-06-15 17:25 ` Siddhesh Poyarekar
2026-06-12 23:46 ` Collin Funk via Gdb
2026-06-13 1:15 ` Sam James via Gdb
2026-06-15 21:17 ` Carlos O'Donell via Gdb
2026-06-15 21:35 ` Andrew Pinski via Gdb
2026-06-15 23:10 ` Adhemerval Zanella Netto via Gdb
2026-06-16 14:50 ` Xi Ruoyao via Gdb
2026-06-16 14:59 ` Adhemerval Zanella Netto via Gdb [this message]
2026-06-16 17:49 ` Carlos O'Donell via Gdb
2026-06-22 18:35 ` Gokhan via Gdb
2026-06-16 16:22 ` Joseph Myers via Gdb
2026-06-16 16:44 ` Collin Funk via Gdb
2026-06-12 23:12 ` Sam James via Gdb
2026-06-15 21:19 ` Carlos O'Donell via Gdb
2026-06-16 16:08 ` Siddhesh Poyarekar
2026-06-16 16:36 ` Joseph Myers via Gdb
2026-06-16 18:01 ` Carlos O'Donell via Gdb
2026-06-13 0:19 ` Alexandre Oliva via Gdb
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=62054d25-48a1-4abb-9bdf-06293d8c065b@linaro.org \
--to=gdb@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=collin.funk1@gmail.com \
--cc=kadirgokhann@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=pinskia@gmail.com \
--cc=xry111@xry111.site \
/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