Bug#745938: the future of sparc in unstable

On 17:06, Bob Bib wrote: > AFAIK, the SPARC32 toolchain is no longer supported upstream, > while Debian 'sparc' port has only 32-bit userland, > with kernel 64 bit-only. A lot of people have repeated this like rumour, but were unable to point me to something official when asked. All I can find is

Bug#745938: the future of sparc in unstable

AFAIK, the SPARC32 toolchain is no longer supported upstream, while Debian 'sparc' port has only 32-bit userland, with kernel 64 bit-only. So from my point of view, the 'sparc' port should be finally DROPPED in favor of the 'sparc64' port which should be migrated from debian-ports into the officia

Bug#745938: the future of sparc in unstable

Just to let all know: Here are Sun Enterprise 880,480,280 and 450 running wheezy (and still squeeze) fine, there are only minor issues with those kernels (look at the linux sparc mailing list and in the debian BTS if you are interested - or ask) here. In the small timeslots left I even compiled som

Bug#745938: the future of sparc in unstable

I have SILO v1.4.14, but it has the git [1] patches from 2012-08-19, which includes quite a few fixes from the 2008-06-12 release. Particularly, it includes a number of ext2/ext4 boot fixes and some sun4v and sun4u boot fixes. The remaining patches after that are for "tilo" which is some kind of TF

Bug#745938: the future of sparc in unstable

Well it is a good start. =D There are still complaints, though haven't seen the bug reports, that modern kernel's are unstable on certain peices of hardware. Personally I can't reproduce any of these issues, I have rolled out the latest kernel for a while now on some of my sparc systems, my T2000

Bug#745938: the future of sparc in unstable

BTW, the sparc buildd looks like gcc 4-8.2-21 is successful and so is gcc-4.9.0-1. I've installed them from sid. Crisis averted? Patrick On Wed, Apr 30, 2014 at 4:04 PM, Sébastien Bernard wrote: > Le 30/04/2014 20:36, Patrick Baggett a écrit : > > > > > On Wed, Apr 30, 2014 at 1:13 PM, Ivo De

Bug#745938: the future of sparc in unstable

Le 30/04/2014 20:36, Patrick Baggett a écrit : On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker > wrote: Hi, On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote: > Indeed, the last good build seems to be gcc-4.8-4.8.2-19. > Look at t

Bug#745938: the future of sparc in unstable

On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker wrote: > Hi, > > On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote: > > Indeed, the last good build seems to be gcc-4.8-4.8.2-19. > > Look at the changelog for the -20 they seems to have done something on > the sparc > > that blocks th

Bug#745938: the future of sparc in unstable

Hi, On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote: > Indeed, the last good build seems to be gcc-4.8-4.8.2-19. > Look at the changelog for the -20 they seems to have done something on the > sparc > that blocks the generation of the libraries. A number of binaries are now buil

Bug#745938: the future of sparc in unstable

On 30/04/14 15:19, Patrick Baggett wrote: > On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard wrote: > Le 30/04/2014 15:39, Patrick Baggett a écrit : >> I tried to build the gcc-4.8-4.8.2-20 and the build is broken. >> libstdc++ and lib64stdc++ are not build, neither are build

Bug#745938: the future of sparc in unstable

Le 30/04/2014 16:19, Patrick Baggett a écrit : On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard > wrote: Le 30/04/2014 15:39, Patrick Baggett a écrit : I tried to build the gcc-4.8-4.8.2-20 and the build is broken. libstdc++ and lib64stdc++

Bug#745938: the future of sparc in unstable

On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard wrote: > Le 30/04/2014 15:39, Patrick Baggett a écrit : > > >>> I tried to build the gcc-4.8-4.8.2-20 and the build is broken. >> libstdc++ and lib64stdc++ are not build, neither are build libgcc1. >> The last good build (with the missing librar

Bug#745938: the future of sparc in unstable

What is also weird is you have the debug package for it. So I am sure it compiled I think there might be something wrong with the packaging for it. On Wed, Apr 30, 2014 at 9:39 AM, Patrick Baggett wrote: > >>> I tried to build the gcc-4.8-4.8.2-20 and the build is broken. >> libstdc++ and lib64

Bug#745938: the future of sparc in unstable

Le 30/04/2014 15:39, Patrick Baggett a écrit : I tried to build the gcc-4.8-4.8.2-20 and the build is broken. libstdc++ and lib64stdc++ are not build, neither are build libgcc1. The last good build (with the missing libraries) is 4.8.2-16. Something broken on -20 and -21. Oh,

Bug#745938: the future of sparc in unstable

> > >> I tried to build the gcc-4.8-4.8.2-20 and the build is broken. libstdc++ > and lib64stdc++ are not build, neither are build libgcc1. > The last good build (with the missing libraries) is 4.8.2-16. > Something broken on -20 and -21. > > Oh, I see what you're saying. I get lib64stdc++-dev / l

Bug#745938: the future of sparc in unstable

I have also been able to build the gcc 4.8.2-21 packages as well. I am not sure what is causing the build systems so much grief when it comes to building these packages. Cheers, Kieron On Wed, Apr 30, 2014 at 9:27 AM, Patrick Baggett wrote: > I kicked off a gcc build (gcc-4.8_4.8.2-21) last nig

Bug#745938: the future of sparc in unstable

I kicked off a gcc build (gcc-4.8_4.8.2-21) last night. It didn't have an errors for me. I now have a bunch of *.deb files: figgles@ghost:~/src$ ls -1 *.deb cpp-4.8_4.8.2-21_sparc.deb g++-4.8-multilib_4.8.2-21_sparc.deb g++-4.8_4.8.2-21_sparc.deb gcc-4.8-base_4.8.2-21_sparc.deb gcc-4.8-locales_4.8

Bug#745938: the future of sparc in unstable

Le 26/04/2014 21:33, Ralf Treinen a écrit : Hello, we currently have in unstable/main/sparc precisely 35491 packages, of a total of 40634 available packages, that cannot be installed in the current version of unstable: % dose-debcheck --fg Packages --deb-ignore-essential background-packages: 0

Bug#745938: the future of sparc in unstable

Hello, we currently have in unstable/main/sparc precisely 35491 packages, of a total of 40634 available packages, that cannot be installed in the current version of unstable: % dose-debcheck --fg Packages --deb-ignore-essential background-packages: 0 foreground-packages: 40634 total-packages: 406