Your message dated Tue, 26 Jun 2007 00:00:17 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Netwinder built fine
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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 never used
Compilation succeeded - 24 warning(s)
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Stacktrace:
Native stacktrace:
make[9]: *** [../../class/lib/basic/System.Xml.dll] Killed
make[9]: Leaving directory /build/buildd/mono-1.1.18/mcs/class/System.XML'
[...]
A full build log can be found at
<http://buildd.debian.org/fetch.cgi?pkg=mono&arch=arm&ver=1.1.18-3&stamp=1161343362>.
Not sure why the stacktraces are both empty?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
--- Begin Message ---
It seems the latest mono build mighty fine on a netwinder:
http://buildd.debian.org/fetch.cgi?pkg=mono;ver=1.2.4-4;arch=arm;stamp=1181823053
netwinders were found to be running an old hand-built kernel which was
causing problems for glibc2.5 as well. This was probably the problem
for mono as well.
--
"rm -rf" only sounds scary if you don't have backups
--- End Message ---
