On Fri, 2006-11-17 at 20:22 +0100, Paolo Molaro wrote:
So the summary is that either using mono 1.2.1 or applying the patch to
earlier versions solves all the building issues for mono as well as the
packages which manifested themselves as a FileNotfound exception: the
bug was in the exception
On 11/16/06 Paolo Molaro wrote:
He has netwinders, cats, etc machines available. All of them are arm
v4l, which seemed to me to be the relevant thing here.
I have contacted Bdale already, I'll mail Vince shortly anyway:
having two boxes likely increases the chance to hit the bug if it's
Hi Paolo,
Thank you for your work investigating this.
On Fri, Nov 17, 2006 at 08:22:34PM +0100, Paolo Molaro wrote:
If I am given access to elara I can try to reproduce that, but it didn't
happen in jitted code and it didn't happen in the 6 builds I ran today
on other boxes: if it's a bug in
This one time, at band camp, Steve Langasek said:
On Wed, Nov 15, 2006 at 10:16:21PM +, Stephen Gran wrote:
This one time, at band camp, Paolo Molaro said:
I build regularly on my arm box (xscale v5l) on debian and run a few
tests.
There should be nothing major that would prevent
On Wed, 2006-11-15 at 15:33 +0100, Mirco Bauer wrote:
Also the failing happens not always at the same build position,
but its always the first few files that get compiled.
Ah, this is new information. If the behaviour is non-deterministic then
this also suggests that the problem is caused by
On Wed, 2006-11-15 at 12:44 +, Phil Blundell wrote:
I'm also concerned that, even on the CATS machines, it might be that
the build is only succeeding by chance and any real-world workload
would cause the same bug to resurface. So, overall, with our current
state of knowledge I kind of
On Wed, 2006-11-15 at 14:40 +, Phil Blundell wrote:
My experience (see my mail on Oct 30) was that the build failed on my
CATS too when I tried it there. I don't think we have enough evidence
to say with any certainty that the bug is really specific to netwinder.
thats true, it's only a
On Tue, Nov 14, 2006 at 01:57:48PM +, Wookey wrote:
So where does that leave us for etch? Does a mono that doesn't run on
netwinders and apparently not on smackdown either, but does run on other
cats systems, make the grade for release? If no one has time to investigate
the problem
On Wed, 2006-11-15 at 04:40 -0800, Steve Langasek wrote:
But does anyone understand yet *why* this bug affects the netwinders and not
the cats boxes?
Not really. My best guess is that it's a subtle timing issue of some
kind and shows up on the netwinders because they're slightly faster.
Or,
On 11/15/06 Phil Blundell wrote:
On Wed, 2006-11-15 at 04:40 -0800, Steve Langasek wrote:
But does anyone understand yet *why* this bug affects the netwinders and not
the cats boxes?
Not really. My best guess is that it's a subtle timing issue of some
kind and shows up on the netwinders
This one time, at band camp, Paolo Molaro said:
I build regularly on my arm box (xscale v5l) on debian and run a few tests.
There should be nothing major that would prevent running mono apps,
though of course bugs may and do exist as in any other software.
To debug what is the issue I'd need
On Wed, Nov 15, 2006 at 10:16:21PM +, Stephen Gran wrote:
This one time, at band camp, Paolo Molaro said:
I build regularly on my arm box (xscale v5l) on debian and run a few tests.
There should be nothing major that would prevent running mono apps,
though of course bugs may and do
On Wed, 2006-11-15 at 19:32 -0800, Steve Langasek wrote:
The
'netwinder' buildd is hosted by Bdale Garbee, though; maybe he could give
Paolo access to that one?
Sure. Paolo, send me details and we'll get you set up.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On 2006-11-10 16:21 -0800, Steve Langasek wrote:
Hi Phil,
At a first glance this looks more like a TLS emulation kind of problem
than an instruction set discrepancy. But it'd take a bit more detective
work to figure out what's really going wrong, and I guess there is no
guarantee that
Hi Phil,
At a first glance this looks more like a TLS emulation kind of problem
than an instruction set discrepancy. But it'd take a bit more detective
work to figure out what's really going wrong, and I guess there is no
guarantee that this is the same problem the netwinders are seeing in
Package: mono
Version: 1.1.18-3
Severity: serious
The latest mono package fails to build on arm with a SIGSEGV:
[...]
System.Xml.Serialization/XmlElementAttribute.cs(49,15): warning CS0169: The
private field `system.Xml.Serialization.XmlElementAttribute.order' is assigned
but its value is
16 matches
Mail list logo
