On Sunday 15 January 2006 5:50 pm, viq wrote:
Yes, apparently. Any idea what could this be? I'll run now several
kernel builds on the linux host to verify the hardware is not causing
problems.
Don't bother - its not a hardware problem. Anyone using the recent snaps
will see it. When a
On Monday 16 January 2006 16:55, Kurt Miller wrote:
On Sunday 15 January 2006 5:50 pm, viq wrote:
Yes, apparently. Any idea what could this be? I'll run now several
kernel builds on the linux host to verify the hardware is not causing
problems.
Don't bother - its not a hardware problem.
On Sunday 15 January 2006 04:52, Kurt Miller wrote:
On Saturday 14 January 2006 14:12, you wrote:
On Saturday 14 January 2006 14:13, knitti wrote:
On 1/14/06, viq [EMAIL PROTECTED] wrote:
Any ideas/pointers what to do with this?
i386 (in vmware), snapshot from jan 9
did it
Well, it's still building, so I can't really tell, but I have a suspect -
from some messages java left it seems it wants to have at least 1.6GB free
diskspace where it's building.
...or I'm totally wrong. Shall see in a couple of hours ;)
Wrong. Didn't help.
--
viq
On Sunday 15 January 2006 05:20, Tobias Ulmer wrote:
On Sat, Jan 14, 2006 at 10:52:10PM -0500, Kurt Miller wrote:
That should be enough memory for the build.
I'm looking into a similar problem in 1.4 right now. The segfault is
random and the few times I caught it in gdb, I didn't get a
On Sunday 15 January 2006 3:28 am, viq wrote:
On Sunday 15 January 2006 05:20, Tobias Ulmer wrote:
On Sat, Jan 14, 2006 at 10:52:10PM -0500, Kurt Miller wrote:
That should be enough memory for the build.
I'm looking into a similar problem in 1.4 right now. The segfault
is random and
Did anyone succeed in building Java 1.5? Mine was bombing out for a few days
on cairo (dunno why, maybe bad ports tree, after one of updates and
remove-cvs it back up it worked), but now the java build itself bombs out
with the following message:
Unexpected Signal : 11 occurred at
On 1/14/06, viq [EMAIL PROTECTED] wrote:
Any ideas/pointers what to do with this?
i386 (in vmware), snapshot from jan 9
did it build for you in an earlier occasion? building java needs a
metric assload of memory, as it seems. last time I built it (-stable,
pre x-mas) the whole mem usage
On Saturday 14 January 2006 14:13, knitti wrote:
On 1/14/06, viq [EMAIL PROTECTED] wrote:
Any ideas/pointers what to do with this?
i386 (in vmware), snapshot from jan 9
did it build for you in an earlier occasion?
That's the first time I'm trying, thus the question about success stories.
On Saturday 14 January 2006 14:12, you wrote:
On Saturday 14 January 2006 14:13, knitti wrote:
On 1/14/06, viq [EMAIL PROTECTED] wrote:
Any ideas/pointers what to do with this?
i386 (in vmware), snapshot from jan 9
did it build for you in an earlier occasion?
That's the first time
On Sat, Jan 14, 2006 at 10:52:10PM -0500, Kurt Miller wrote:
That should be enough memory for the build.
I'm looking into a similar problem in 1.4 right now. The segfault is
random and the few times I caught it in gdb, I didn't get a backtrace
that led me to the problem.
The breakage
11 matches
Mail list logo
