[ Replying to the list this time ]
Joey wrote:
>-=-=-=-=-=-
>
>Steve McIntyre wrote:
>> Yeah - all 3 of the cats-based buildds I'm watching have 256MB.
>
>How much ram does toffee have? That's where gnuradio-core FTBFSed
>before.
256MB. Do you have a link to the log for the FTFBS?
--
Steve McIn
Joey Hess a écrit :
Aurelien Jarno wrote:
Joey Hess a écrit :
Steve Langasek wrote:
Here is the list of arm-only problems I know about that currently keep
arm
>from catching up / making headway against the list of unbuilt packages:
- sablevm-classlib: buildd timeout, needs timing info before
Steve McIntyre wrote:
> Yeah - all 3 of the cats-based buildds I'm watching have 256MB.
How much ram does toffee have? That's where gnuradio-core FTBFSed
before.
--
see shy jo
signature.asc
Description: Digital signature
Phil Blundell wrote:
>On Tue, 2006-09-26 at 16:52 -0400, Joey Hess wrote:
>> Steve Langasek wrote:
>> > - gnuradio-core: needs timing info
>>
>> 40 hours for 1 gcc run on a 64 mb arm machine. The problimatic gcc runs
>> were swapping, so it should take a _lot_ less time on a machine with > 64
>> m
On Tue, 2006-09-26 at 16:52 -0400, Joey Hess wrote:
> Steve Langasek wrote:
> > - gnuradio-core: needs timing info
>
> 40 hours for 1 gcc run on a 64 mb arm machine. The problimatic gcc runs
> were swapping, so it should take a _lot_ less time on a machine with > 64
> mb ram. If we can't get such
Joey Hess wrote:
> > - firefox: needs timing info
>
> Building now, I suppose this will take a while..
8 hours for the link was the worst bit, uploaded.
--
see shy jo
signature.asc
Description: Digital signature
Aurelien Jarno wrote:
> Joey Hess a écrit :
> >Steve Langasek wrote:
> >>Here is the list of arm-only problems I know about that currently keep
> >>arm
> >>from catching up / making headway against the list of unbuilt packages:
> >>
> >>- sablevm-classlib: buildd timeout, needs timing info before
Joey Hess a écrit :
Steve Langasek wrote:
Here is the list of arm-only problems I know about that currently keep arm
from catching up / making headway against the list of unbuilt packages:
- sablevm-classlib: buildd timeout, needs timing info before give-back
I don't know how long to wait,
Steve Langasek wrote:
> Here is the list of arm-only problems I know about that currently keep arm
> from catching up / making headway against the list of unbuilt packages:
>
> - sablevm-classlib: buildd timeout, needs timing info before give-back
Seems to hang when I try to build it on arm. Need
On Sat, Sep 09, 2006 at 11:21:52AM +0200, Andreas Barth wrote:
> * Andreas Barth ([EMAIL PROTECTED]) [060828 20:14]:
> > hppa and ia64 are only temporarily bad, but arm has shown these problems for
> > some time now. One of the most troublesome packages is xulrunner, as
> > quite a few packages (bu
Does anyone have a clue as to what is going on with python-qt3 on the
ARM platform? Another build was tried on September 13 and failed
again (this time it was a different failure than the one in August.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Steve Langasek wrote:
> Does anyone know what happened to make ld so much slower on arm all of
> a sudden?
I'm not sure about linking, since I can't build xulrunner yet, but on my
64 mb arm box (bitsyxb with a USB disk), I'm seeing some very slow (12
hours) gcc runs. It mostly seems to be due to g
Joey Hess wrote:
> > Another package which caught my attention is arts, please see
> > http://buildd.debian.org/fetch.php?&pkg=arts&ver=1.5.4-1&arch=arm&stamp=1156962832&file=log&as=raw
>
> Trying this now. Gotta love it when a >/dev/null 2>&1 line crashes a
> build..
Built and uploaded ok, must
Joey Hess writes:
> Andreas Barth wrote:
> > Unfortunatly, xulrunner is still not fixed yet.
>
> It can't be until gcj-4.1 has been bootstrapped to a current version on
> arm. Unfortunatly my try at this died strangely after 6 days. I
> understand that doko has a build running and I'm hoping his s
Andreas Barth wrote:
> Unfortunatly, xulrunner is still not fixed yet.
It can't be until gcj-4.1 has been bootstrapped to a current version on
arm. Unfortunatly my try at this died strangely after 6 days. I
understand that doko has a build running and I'm hoping his succeeds,
otherwise it will tak
* Andreas Barth ([EMAIL PROTECTED]) [060828 20:14]:
> hppa and ia64 are only temporarily bad, but arm has shown these problems for
> some time now. One of the most troublesome packages is xulrunner, as
> quite a few packages (build-)depend on it. It is yet unknown what the problem
> is, if e.g. a l
There are problems with builds of python-qt3 that are blocking other
builds, also
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Aug 28, 2006 at 10:15:41PM +0200, Mike Hommey wrote:
> On Mon, Aug 28, 2006 at 01:01:00PM -0700, Steve Langasek <[EMAIL PROTECTED]>
> 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 fo
On Mon, Aug 28, 2006 at 10:15:41PM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 28, 2006 at 01:01:00PM -0700, Steve Langasek <[EMAIL PROTECTED]>
> wrote:
> > Yes, it can be and is configured by source package. If you can get some
> > numbers to the buildd admin (James) about how lo
On Mon, Aug 28, 2006 at 01:01:00PM -0700, Steve Langasek <[EMAIL PROTECTED]>
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 t
On Mon, Aug 28, 2006 at 09:21:38PM +0200, Mike Hommey wrote:
> > Compiling Java interface classes
> > find _javagen -name "*.java" > java.files
> > /usr/lib/jvm/java-gcj/bin/javac -source 1.4 -classpath . -d . -sourcepath
> > _javagen @java.files
> > Exception in thread "main" java.lang.NoClassDef
On Mon, Aug 28, 2006 at 02:43:56PM -0400, Lennart Sorensen <[EMAIL PROTECTED]>
wrote:
> Well xulrunner seems to have an issue with javac based on this last part
> of the build log:
Waw, I must say I'm impressed that for once in a while it doesn't abort
ld because it takes too much time to do its
Lennart Sorensen writes:
> Well xulrunner seems to have an issue with javac based on this last part
> of the build log:
>
> Compiling Java interface classes
> find _javagen -name "*.java" > java.files
> /usr/lib/jvm/java-gcj/bin/javac -source 1.4 -classpath . -d . -sourcepath
> _javagen @java.fil
On Mon, Aug 28, 2006 at 08:13:06PM +0200, Andreas Barth wrote:
> we (the release team) noticed that arm has had some autobuilding and porting
> problems in the past few weeks. According to the most recent britney runs,
> the current numbers of uncompiled binaries are these:
> 110 mips
> 116
[ Cced all the people who are listed as arm porters on the release wiki ]
Hi,
we (the release team) noticed that arm has had some autobuilding and porting
problems in the past few weeks. According to the most recent britney runs,
the current numbers of uncompiled binaries are these:
110 mips
25 matches
Mail list logo
