[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: arm release issues

On Mon, Aug 28, 2006 at 10:15:41PM +0200, Mike Hommey <mh@glandium.org> wrote:
> On Mon, Aug 28, 2006 at 01:01:00PM -0700, Steve Langasek <vorlon@debian.org> wrote:
> > Yes, it can be and is configured by source package.  If you can get some
> > numbers to the buildd admin (James) about how long it should take for these
> > packages to build, it should be straightforward to fix up that config AFAIK.
> Unfortunately, not being on owner of an arm, I don't have any numbers.
> > Does anyone know what happened to make ld so much slower on arm all of a
> > sudden?
> Probably the switch to providing debugging symbols, but i'm somehow
> surprised the same doesn't happen seem to happen with firefox, though
> the build is not done the exact same way. The main big part of firefox
> is built as a static binary while in xulrunner it is a big dynamic
> library. Maybe that makes some kind of difference.
> Anyways, on my x86, it already takes quite some time to build this
> library, though again, I don't have timings. But it doesn't take more
> than a few minutes. The main thing is that it takes a huge amount of
> memory. It takes more than 500MB on my build machine. Which means on
> slow machines, with few amounts of memory (arm buildd have 64MB, i
> think), it can take long time, and depending on how ld plays with
> its memory, it can be even worse.

Woooo bad talking, it's 128MB.

I asked quite some long time ago if it was worth having these debugging
symbols packages on all arches, it seems obvious it's particularly
a PITA on arm.


Reply to: