2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
because its major purpose this decade is running legacy 32-bit binaries,
a purpose that would no longer be possible if it broke ABI
- non-release architectures in the same category: hurd-i386 (I think)
Simon McVittie, le mer. 13 mars 2024 10:52:35 +0000, a ecrit:
2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
because its major purpose this decade is running legacy 32-bit binaries,
a purpose that would no longer be possible if it broke ABI
- non-release architectures in the same category: hurd-i386 (I think)
We asked hurd-i386 to be there indeed, because we plan to have
hurd-amd64 replace hurd-i386 way before 2038 :)
On Wed, Mar 13, 2024 at 12:34:55PM +0100, Samuel Thibault wrote:
Simon McVittie, le mer. 13 mars 2024 10:52:35 +0000, a ecrit:
2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
because its major purpose this decade is running legacy 32-bit binaries,
a purpose that would no longer be possible if it broke ABI
- non-release architectures in the same category: hurd-i386 (I think)
We asked hurd-i386 to be there indeed, because we plan to have
hurd-amd64 replace hurd-i386 way before 2038 :)
Wouldn't it make sense to migrate hurd-i386 to 64-bit time_t
regardless of the plans for hurd-amd64?
Contrary to linux-i386, it's not like there is a wealth of (possibly proprietary/binary-only) hurd-i386 software out there that we would
benefit from remaining compatible with.
On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
Hi!
Is anyone perhaps planning to fix cargo?
For example curl isn't building on armel/armhf now and numerous packages that depend of curl are not building on armel/armhf.
Thanks in advance to the person who steps up.
see the (linked) t64 transition bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884#197
Hi!
pe 15. maalisk. 2024 klo 6.56 Fabian Grünbichler <debian@fabian.gruenbichler.email> kirjoitti:
On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
Hi!
Is anyone perhaps planning to fix cargo?
For example curl isn't building on armel/armhf now and numerous packages that depend of curl are not building on armel/armhf.
Thanks in advance to the person who steps up.
see the (linked) t64 transition bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884#197
That link doesn't answer my question. The link is to bug report summarizing that cargo is broken and suggesting it needs to be re-bootstrapped.
Currently we haven't seen anybody step up to do it. I would be very
grateful if somebody with enough expertise would be available to do it and thus help resolve the whole chain of broken builds.
build gdb without libdebuginfo on the bootstrap archs for a while.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 360 |
Nodes: | 16 (2 / 14) |
Uptime: | 128:25:40 |
Calls: | 7,686 |
Files: | 12,828 |
Messages: | 5,711,088 |