Re: the future of sparc in unstable

2014-04-30 Thread Patrick Baggett
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

Re: the future of sparc in unstable

2014-04-30 Thread Ivo De Decker
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

Re: Bug#745938: the future of sparc in unstable

2014-04-30 Thread Steven Chamberlain
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

Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-30 Thread Lennart Sorensen
On Wed, Apr 30, 2014 at 11:21:14AM -0400, Lennart Sorensen wrote: > On Wed, Apr 30, 2014 at 07:53:30AM -0400, Lennart Sorensen wrote: > > On Tue, Apr 29, 2014 at 04:47:26PM -0400, Lennart Sorensen wrote: > > > It looks to me as if the problem might be here: > > > > > > sub rWORD1, r010

Re: the future of sparc in unstable

2014-04-30 Thread Sébastien Bernard
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++

Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-30 Thread Lennart Sorensen
On Wed, Apr 30, 2014 at 07:53:30AM -0400, Lennart Sorensen wrote: > On Tue, Apr 29, 2014 at 04:47:26PM -0400, Lennart Sorensen wrote: > > It looks to me as if the problem might be here: > > > > sub rWORD1, r0101, rTMP2 > > No that's not it. Still haven't figured it out. Does this ac

Re: the future of sparc in unstable

2014-04-30 Thread Patrick Baggett
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

Re: the future of sparc in unstable

2014-04-30 Thread Sébastien Bernard
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,

Re: the future of sparc in unstable

2014-04-30 Thread Kieron Gillespie
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

Re: the future of sparc in unstable

2014-04-30 Thread Patrick Baggett
> > >> 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

Re: the future of sparc in unstable

2014-04-30 Thread Kieron Gillespie
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

Re: the future of sparc in unstable

2014-04-30 Thread Patrick Baggett
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

Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-30 Thread Lennart Sorensen
On Tue, Apr 29, 2014 at 04:47:26PM -0400, Lennart Sorensen wrote: > It looks to me as if the problem might be here: > > sub rWORD1, r0101, rTMP2 No that's not it. Still haven't figured it out. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with

Re: State of Haskell on sparc?

2014-04-30 Thread Colin Watson
On Wed, Apr 30, 2014 at 09:36:51AM +0200, Joachim Breitner wrote: > What is going on here? Do I have to rebuild ghc or is it a general > Problem? Is this on someone’s monitor? It's a general problem, perhaps most easily seen here: https://buildd.debian.org/status/package.php?pkg=gcc-4.9 https

Re: State of Haskell on sparc?

2014-04-30 Thread Sébastien Bernard
Le 30/04/2014 09:36, Joachim Breitner a écrit : Hi, Am Dienstag, den 29.04.2014, 16:27 +0200 schrieb Joachim Breitner: According to "dak rm -R -n haskell-tls-extra" this blocked by left over packages depending on it on sparc. The root of the cause is a failure of haskell-tls to build on sparc:

Re: State of Haskell on sparc?

2014-04-30 Thread Joachim Breitner
Hi, Am Dienstag, den 29.04.2014, 16:27 +0200 schrieb Joachim Breitner: > According to "dak rm -R -n haskell-tls-extra" this blocked by left over > packages depending on it on sparc. The root of the cause is a failure of > haskell-tls to build on sparc: > https://buildd.debian.org/status/logs.php?p

Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-30 Thread Ian Campbell
On Tue, 2014-04-29 at 19:34 -0400, Kieron Gillespie wrote: > https://wiki.debian.org/PortsSparc > > > Started a catagory of major bugs. Please place links and titles to the > bug report in this list so we can better track the status and > reference the problems quickly. You might find the BTS's