On Mon, Mar 23, 2020 at 7:21 PM Steve McIntyre steve@einval.com wrote:
On Wed, Mar 11, 2020 at 01:52:00PM +0100, Arnd Bergmann wrote:
- Adding a time64 armhf as a separate (incompatible) target in glibc
that defines __TIMESIZE==64 and a 64-bit __time_t would avoid most of the remaining ABI issues and put armhf-time64 in the same category as riscv32 and arc, but this idea was so far rejected by the glibc maintainers. Depending on how hard this turns out to be, it could be used to get to the point of self-hosting though, and help find time64 related bugs in the rest of the distro.
OK. I'm thinking it's probably not worth it?
This depends on the timeline of Lukasz' work. My feeling is that there is still quite a bit to be done before it's worth trying the Debian bootstrap again.
If you or someone else wants to continue where I stopped with the Debian rebuilding without waiting for the complete glibc port, adding a new armhf target to glibc on top of the current glibc-y2038 tree is probably a quicker way to get something that builds and boots. I don't know how much work exactly there would be for this approach, but my feeling is that it's not that much after looking at the kind of problems I ran into, and at the state of the riscv32 port that uses the same approach.
Arnd