/usr/share/doc/mono-runtime-common/README.Debian is in mono-runtime-common 4.2.1.102+dfsg2-7ubuntu4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 | Mono for Debian
---------------
1. Documentation can be found in the separated monodoc packages.
2. Supported Processor Architectures for Mono 1.1.x (current)
JIT:
Linux/x86
Linux/AMD64
Linux/PPC
Linux/S390 (not functional)
Linux/ARM
Solaris/SPARC
Interpreter (deprecated/unmaintained):
-
Supported Processor Architectures for Mono 1.0.x (old)
JIT:
Linux/x86
Linux/PPC
MacOS/PPC
Interpreter (deprecated/unmaintained):
Linux/x86
Linux/PPC
HP-UX/HPPA
S390
StrongARM
Solaris/SPARC
Solaris/SPARC v9
3. Typical problems:
3a. Purge your ~/.wapi directory if you see messages like:
** (/tmp/hello.exe:23770): WARNING **: Shared memory sanity check
failed.
** (/tmp/hello.exe:23770): WARNING **: Failed to attach shared memory!
Falling back to non-shared handles
Reason:
02:00:00 < totte> .wapi is the shared memory file folder used to handle process.start and someother functions for our IO lib
3b. Question:
Mono does not work for me (wrong version of mscorlib reported) or
monodevelop breaks on start (MonoDevelop.Core.dll has incorrect
version...)
Answer:
Most likely you have compiled some old Mono version before and have
a funny mixture of upstream and Debian files in different versions.
Make sure that /usr/local does not appear in the output of the
following commands and remove the particular files in /usr/local/...:
which mono
which mint
ldd $(which mono)
ls /usr/local/lib/Mono*dll
ls /usr/local/lib/System*dll
ls /usr/local/lib/I18*dll
(and maybe most other dll files there)
4. (for developers)
The main coordination site of the maintainers is on
http://pkg-mono.alioth.debian.org/, more details can be found there.
CLI Policy for packaging Mono libraries/applications can be found on
http://pkg-mono.alioth.debian.org/cli-policy/
An offline version is in /usr/share/doc/cli-common/ of the the cli-common package.
-----------------------------------------------------------------------------
PS: Some comparisons (not real benchmarks!), testing different
invocation methods:
The "native" method via exec, binfmt_misc, binfmpt-support (Perl
script), binfmt-detector-cli:
time for x in `seq 1000` ; do ./hello.exe > /dev/null; done
real 3m2.969s
user 2m8.060s
sys 0m14.540s
The shell wrapper method using mono:
time for x in `seq 1000` ; do ./hello.sh > /dev/null; done
real 2m43.146s
user 1m45.990s
sys 0m11.140s
Using "cli-wrapper" with a symlink:
time for x in `seq 1000` ; do ./hello > /dev/null; done
real 2m23.958s
user 1m32.720s
sys 0m9.640s
The "interpreter" method using mono:
time for x in `seq 1000` ; do /usr/bin/cli ./hello.exe > /dev/null; done
real 2m23.699s
user 1m33.140s
sys 0m8.920s
Eduard Bloch <blade@debian.org> -- Sat, 19 Jun 2004 02:28:40 +0200
|