Re: toolchain problems

Well the version number is cvs20080103-4, which makes me think it's not recent enough for the patch to already be there. I would think the patch itself would just work, but I haven't built and tested it (yet). Are you working on it, or should I give it a go? Please give it a go. I'm still work

Re: toolchain problems

On Thu, May 01, 2008 at 02:54:02AM +0200, Michael Schmitz wrote: >>> python2.5: hangs forever on test_bsddb3. >> Hm. Elgar (our most memory constrained build) managed to build it! > Something unusual with that buildd's setup (additiona packages or config > files in the chroot that we don't u

Re: toolchain problems

On Thu, May 01, 2008 at 02:54:02AM +0200, Michael Schmitz wrote: > Which one is installed - my -2 or someone else's 2.1? I've got 2.1 ready > to be uploaded now. 1.0.1-2 >> Hm. Elgar (our most memory constrained build) managed to build it! > > Something unusual with that buildd's setup (ad

Re: toolchain problems

Is somebody taking on the ilmbase binNMU? Already installed, openexr is now built, so imagemagick is in the queue (it has about 64 deps). Which one is installed - my -2 or someone else's 2.1? I've got 2.1 ready to be uploaded now. * pie: we've got a number of packages that fail to buil

Re: toolchain problems

On Wed, Apr 30, 2008 at 08:01:12AM -0500, Stephen R Marenka wrote: > > python2.5: hangs forever on test_bsddb3. > Hm. Elgar (our most memory constrained build) managed to build it! To cite an old slogan: "Only Amiga makes it possible!" SCNR ;) -- Ciao...//Fon: 0381-

Re: toolchain problems

And we're over 80% built. You've got to like the velocity on . On Tue, Apr 29, 2008 at 10:57:29AM -0500, Stephen R Marenka wrote: > Is somebody taking on the ilmbase binNMU? Already installed, openexr is now built, so imagemagick is in the qu

Re: toolchain problems

On Wed, Apr 30, 2008 at 01:56:29AM +0200, Michael Schmitz wrote: > Hi, > >>> What's the problem with integrating that patch into our current version >>> of binutils? >> >> Well the version number is cvs20080103-4, which makes me think it's not >> recent enough for the patch to already be there. I w

Re: toolchain problems

Hi, What's the problem with integrating that patch into our current version of binutils? Well the version number is cvs20080103-4, which makes me think it's not recent enough for the patch to already be there. I would think the patch itself would just work, but I haven't built and tested it (y

Re: toolchain problems

On Tue, Apr 29, 2008 at 11:21:14PM +0200, Michael Schmitz wrote: >> On Tue, Apr 29, 2008 at 04:52:40PM +, Joseph S. Myers wrote: >>> On Tue, 29 Apr 2008, Stephen R Marenka wrote: >>> * pie: we've got a number of packages that fail to build because -pie gives a nonrepresentat

Re: toolchain problems

On Tue, Apr 29, 2008 at 04:52:40PM +, Joseph S. Myers wrote: On Tue, 29 Apr 2008, Stephen R Marenka wrote: * pie: we've got a number of packages that fail to build because -pie gives a nonrepresentational output. Can that option be a no-op or something on m68k so at least st

Re: toolchain problems

Hi, Is somebody taking on the ilmbase binNMU? Done, and uploaded. I'm thinking about building mesa with gcc-4.2 once we get below 150 needs-build. If that succeeds, it'll add several hundred to needs-build. Any thoughts? gcc * courier_0.59.0-1 error: insn does not satisfy its constraints

Re: toolchain problems

On Tue, Apr 29, 2008 at 04:52:40PM +, Joseph S. Myers wrote: > On Tue, 29 Apr 2008, Stephen R Marenka wrote: > > > * pie: we've got a number of packages that fail to build because -pie > > gives a nonrepresentational output. Can that option be a no-op or > > something on m68k

Re: toolchain problems

On Tue, 29 Apr 2008, Stephen R Marenka wrote: > * pie: we've got a number of packages that fail to build because -pie > gives a nonrepresentational output. Can that option be a no-op or > something on m68k so at least stuff builds without m68k-specific > workarounds? You d

toolchain problems

As we finally creep towards the 80% built mark with 220 needs-build and "only" 915 dep-wait, I started looking at some of the toolchain bugs that have been bothering me. I'm a bit concerned that the timeouts are related. Anyway, all of this is beyond me, so grab something and fix it. :) Is someb