[Pkg-utopia-maintainers] Re: ANNOUNCE: Mono goes arm
meebey at meebey.net
Sun Feb 5 17:51:07 UTC 2006
On Sat, 2006-02-04 at 13:25 -0800, Dave Beckett wrote:
> I doubt I'll ever do use 'any' since not all of those architectures are
CLI (as in Common Language Infrastructure) applications and libraries
are stable for any architecture that has a stable runtime, and that is
Mono, and that is controlled and decided by the Mono package
maintainers. Thus this not the problem of CLI applications/libraries
(specially not for the ones that are arch-all which is the normal case,
except the package contains glue/native libraries/binaries)
> plus the autobuilders still try to build on architectures that
> are not supported and the Not-For-Us lists are a joke.
I thought that's Packages-arch-specific for, no?
The standard CLI application/library should not need architecture
handling, thats what all this arch-indep bytecode is about.
> arm's no use to me right now as nant seg faults inside /usr/bin/mono on
so you found a bug in the runtime, good that we enabled arm, now it can
be reported and fixed!
> and that's used to build ikvm, nunit and probably others.
not that I know of (in debian at least).
Other arch-dep packages like gtk-sharp2 just build fine. When you look
at the rest of the arch-dep packages like muine or beagle you will
notice that they can't be build yet on arm since the libraries they need
are not all avialable for arm yet (but those have special packages too
since they are not just made for mono but for other languages/platforms
too, thus they can't use arch any)
> Here's a failure from ikvm on arm:
> nant -v clean
> Unhandled Exception: System.IO.FileNotFoundException:
> mscorlib.resources, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089 : mscorlib.resources,
> Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
> in <0x00000> <unknown method>
> in <0x00000> <unknown method>
> Although tangentally, the build state of ikvm is so bad, i'm considering
> making it i386 and amd64 only.
ikvm is a very special package, and should be handled like that, ikvm
includes all java, mono, gnu classpath problems in one package. That is
not what I meant when I said "If your package targets just Mono (Mono
based application/library) please use arch "any" instead of listing each
arch"... So making it i386 and amd64 only is just allright if other
architectures don't work with it... but that's not the fault of CLI but
integration between the different worlds.
It seems my previous announce mail didn't show the points I was trying
I just wanted to say that normal CLI application/libraries that are just
made for Mono, and are architecture-depenent should be "arch any" (like
muine, beagle, banshee, gtk-sharp2..), all other cases list the archs
Because I see the big problem that Mono is ported to more and more
architectures and getting all programs and libraries build for it will
become more and more pain when even simple applications are listing the
archs while it's unneeded.
dbus, gmime, ikvm and so on are special cases (they all mix different
languages/platforms) and those should not use arch any.
Hope it's now clear, sorry for the noise, if more discussion is needed,
please use pkg-mono-devel at lists.alioth.debian.org instead of CC war,
Mirco 'meebey' Bauer
-----BEGIN GEEK CODE BLOCK-----
GIT d s-:+ a-- C++ UL++++$ P L++$>+++$ E- W+++$ N o? K- w++>! O---- M-
PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r->++ y?
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 481 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20060205/97591f2a/attachment.pgp
More information about the Pkg-utopia-maintainers