Re: Nominations for Anthropic’s Claude for Open So urce program
Gokhan <[email protected]> Mon, 22 Jun 2026 21:35:07 +0300
| Newsgroups | gmane.comp.lib.glibc.alpha,gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAFPohwBxDj6Xv5L4xxdpM10xUw0+YXj4TVXv5H4J4WExr36kwA@mail.gmail.com> |
--00000000000077a68c0654dbe752 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It seems that we have both been trying to find the right way to move this forward. I have been looking for ways to contribute, while you have been trying to identify a suitable task for me. I reviewed the areas you previously mentioned, but it seemed that I would need to spend a significant amount of time getting familiar with them first. For that reason, I postponed joining for a while. This time, however, it looks like there may be some opportunities where I can contribute more effectively. I will review the available options and get back to you after I have had some time to assess them. Please give me some time to look into this properly. Kolayl=C4=B1kla *Kadir G=C3=B6khan Sezer* On Tue, Jun 16, 2026 at 8:50=E2=80=AFPM Carlos O'Donell <[email protected]>= wrote: > On 6/16/26 10:59 AM, Adhemerval Zanella Netto wrote: > > > > > > 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 buildin= g > >> 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 silen= t > > disable testing due missing tools. > > (1) Dependencies. > > May we please start a new there for this? > > Particularly around "build", "test", and "runtime" dependencies. > > >> > >> 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 i= s > > only required for manual generation and you put texinfo already brings = it > > anyway. > > > > (2) Bootstrap. > > May we please start a new thread for this? > > This is another distinct discussion which has to do with reducing > toolchain bootstrap dependencies. I say "bootstrap" because you should > have a way to bootstrap (to do reproducible builds, or audit a minimal > bootstrap seed, or bringup hardware) that needs the fewest number of > things you can manage. This can include disabling features during the > bootstrap. > > -- > Cheers, > Carlos. > > --00000000000077a68c0654dbe752 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>It seems that we have both been trying to find the ri= ght way to move this forward. I have been looking for ways to contribute, w= hile you have been trying to identify a suitable task for me.<br>I reviewed= the areas you previously mentioned, but it seemed that I would need to spe= nd a significant amount of time getting familiar with them first. For that = reason, I postponed joining for a while.<br>This time, however, it looks li= ke there may be some opportunities where I can contribute more effectively.= I will review the available options and get back to you after I have had s= ome time to assess them.<br>Please give me some time to look into this prop= erly.</div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail= =3D"gmail_signature"><div dir=3D"ltr"><div><br></div><div><font face=3D"ari= al, sans-serif">Kolayl=C4=B1kla</font></div><font face=3D"arial, sans-serif= "><i>Kadir G=C3=B6khan Sezer</i></font></div></div></div><br></div><br><div= class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmai= l_attr">On Tue, Jun 16, 2026 at 8:50=E2=80=AFPM Carlos O'Donell <<a = href=3D"mailto:[email protected]">[email protected]</a>> wrote:<br></div= ><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border= -left:1px solid rgb(204,204,204);padding-left:1ex">On 6/16/26 10:59 AM, Adh= emerval Zanella Netto wrote:<br> > <br> > <br> > On 16/06/26 11:50, Xi Ruoyao wrote:<br> >> On Mon, 2026-06-15 at 20:10 -0300, Adhemerval Zanella Netto wrote:= <br> >>> 6. Internal script cleanup<br> >>><br> >>> This might be a more contentious one, but I think we can reduc= e our build<br> >>> dependencies by at least rewriting the Perl script to either a= wk or Python.<br> >><br> >> Hmm, it seems glibc can already build w/o Perl (if you don't c= are the<br> >> info pages which need Texinfo).=C2=A0 I happened to figure that ou= t after<br> >> forgetting the temporary Perl and Texinfo installations before bui= lding<br> >> glibc when I performed a test build of Linux From Scratch manually= <br> >> several days ago.<br> > <br> > We still install the mtrace, so to use all the glibc features one woul= d<br> > need to install perl. The scripts/<a href=3D"http://test-installation.= pl" rel=3D"noreferrer" target=3D"_blank">test-installation.pl</a> is alread= y gated<br> > through perl existence, but I think it is not a good design if we sile= nt<br> > disable testing due missing tools.<br> <br> (1) Dependencies.<br> <br> May we please start a new there for this?<br> <br> Particularly around "build", "test", and "runtime&= quot; dependencies.<br> <br> >><br> >> Also reducing the Perl scripts won't help too much for distros= as<br> >> Texinfo is still in Perl and the distros will need the info pages<= br> >> anyway.<br> >><br> > <br> > I think the main gain is for mtrace, the two other scripts<br> > (<a href=3D"http://test-installation.pl" rel=3D"noreferrer" target=3D"= _blank">test-installation.pl</a>, <a href=3D"http://summary.pl" rel=3D"nore= ferrer" target=3D"_blank">summary.pl</a>) are not essential.=C2=A0 The <a h= ref=3D"http://summary.pl" rel=3D"noreferrer" target=3D"_blank">summary.pl</= a> is<br> > only required for manual generation and you put texinfo already brings= it<br> > anyway.<br> > <br> <br> (2) Bootstrap.<br> <br> May we please start a new thread for this?<br> <br> This is another distinct discussion which has to do with reducing<br> toolchain bootstrap dependencies. I say "bootstrap" because you s= hould<br> have a way to bootstrap (to do reproducible builds, or audit a minimal<br> bootstrap seed, or bringup hardware) that needs the fewest number of<br> things you can manage. This can include disabling features during the<br> bootstrap.<br> <br> -- <br> Cheers,<br> Carlos.<br> <br> </blockquote></div> --00000000000077a68c0654dbe752--