> On Nov 27, 2016, at 2:14 PM, Matthias Klose <d...@debian.org> wrote: > > The patches to configure --with-cpu-32= and --with-cpu-64= are availabe in GCC > 6, so we should use them and ensure that the defaults for the sparc/64 and > sparc64, and sparc and sparc64/32 targets match. Just forcing ultrasparc for > all multilib variants seems to be questionable.
Right. I completely forgot about the approach to just with --with-cpu32=ultrasparc. Definitely makes sense. But it might break again if the default target for gcc for 64-bit is moved to anything newer than ultrasparc. > Btw, is there any business with the Debian sparc port, or is this just some > exercise? I want to have this small patch in to help Helmut Grohne with his rebootstrap project. We are currently not planning to bring "sparc" back into Debian. However, there are many end users who stilm prefer a 32-bit userland over a 64-bit userland, including David Miller (the main person behind the Linux port for SPARC), and keeping "sparc" bootstrappable in "rebootstrap" means that a) Helmut has more targets for testing (and finding bugs) and b) those who wish to use a 32-bit userland will always be able to bootstrap it themselves. I actually expect that thanks to Helmut's rebootstrap project, we might have a tool in Debian in the future which allows us to cross-bootstrap Debian for any architecture/toolchain/libc combination supported by the toolchain. Given how small and self-containing this minor change to the debian/rules2 file is, I think it's definitely a very good idea to apply it given the previously mentioned motivations. Thanks, Adrian
