Re: An (flamebait ?) idea to preserve debian on sparc32...
dolbeaur@club-internet.fr (Romain Dolbeau) writes:
> Splitting the port between sparc32-v7, sparc32-v8 and sparc-v9 would
> permit multiple libc, with or without a kernel change, and with backward
> availability of packages if the kernel is similar enough.
Since there's already a v9 libc package, I assume there's no problem
in principle of providing a v7 one, which can surely be built.
However, the right one doesn't necessarily get picked up correctly. I
made a relevant bug report long ago, to which I had no response as far
as I remember. I don't recall the details, but it's basically that
the dynamic loader doesn't check the right capability (?) for whether
the relevant instructions are available.
> A question on the Debian dependency system: can it handle inter-archs
> dependency ? i.e. is it already feasible (in theory) to split an arch in
> two or more, and have dependency "fall back" from say v8 to v7 if a
> package is not in v8, like it does with unstable/testing/stable ?
There's a discussion document, at least:
<URL:http://raw.no/debian/amd64-multiarch-2>. The bit about using
`gcc -dumpmachine' seems to be wrong, though, for sparc and, I guess,
MIPS.
[I assume Linux could emulate the missing instructions in principle.]
Reply to: