Hello, Thanks for the update, it all seems to be on track!
Hopefully the availability of the glibc-hurd tarball allow the code to be simplified, and the Hurd-specific parts of the glibc recipes to be reduced. > I was thinking about following Mark's suggestion of having a generic > glibc package with all the common > configure flags and inputs, and the two others inheriting from it, > defining the specific sources and > inputs/flags. WDYT? In an ideal world, the only differences between the two libcs would be the source (and version) and the inputs. How far are we from that now? If we can achieve that, we’ll be able to keep a single glibc recipe. If there are other differences, we’ll see. > Ludovic I don't have anything to report on the binaries actually > running on hurd right now, > because I am hoping to test that with the actual bootstrap tarballs. No problem! Cheers, Ludo’.