On Sun, Jan 4, 2026 at 11:03 AM Jeffrey Law <[email protected]> wrote: > > > > On 1/3/2026 9:03 AM, Keith Packard wrote: > > At least it has aged well -- the new patch has a very light impact for > non-picolibc builds, and has been well tested as a part of Zephyr SDK > 1.0 development where it now gets built into 35 toolchains which are > run through both the picolibc and Zephyr test suites. > > Yea, I would expect light impact outside picolibc. It's nice and isolated. > > > I suspect your Hexagon colleagues might also be pleased to be able to > build picolibc-based toolchains; they've been contributing patches to > picolibc for quite a while now, so it's even vaguely work-related? > > It's not really work related as I'm nowhere near the Hexagon stuff. In fact, > contributing Hexagon stuff requires some additional sign-offs, so I try to > stay away from it even more than I would otherwise :-) > > In any case, thanks for keeping it on your to-do list; I'd love to stop > carrying this patch for all of the toolchains I work on. I've delayed > adding it to the Debian embedded toolchains until it lands upstream. > > You don't need to carry it anymore. I regenerated configure and pushed the > patch to the trunk.
And I pushed the following which regenerates configure with the unmodified upstream version of autoconf (to make the buildbot happy). Thanks, Andrew > > > jeff > > ps. I've still got the -Os thing in my queue too :-)
0001-Regenerate-gcc-configure-with-the-correct-version-of.patch
Description: Binary data
