Yeah, that totally worked~ ... well, it didn't fix it, but it did actually run successfully.
How do I fix binfmt? My /usr/local/binfmts/cli reads: package mono-runtime detector /usr/lib/cli/binfmt-detector-cli interpreter /usr/bin/cli magic MZ I'd just change that to /usr/local/lib, but I don't have a /usr/local/bin/cli/ ~ Doug. On Thu, Jun 16, 2011 at 2:55 PM, Ian Norton <[email protected]> wrote: > Looks like your binrfmt support is running it with /usr/bin/mono. Try > running it manually with /usr/local/bin/mono. If that works you should fix > binfmt. > > Ian > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > > Doug <[email protected]> wrote: >> >> Hi, >> >> I can compile a file using dynamic objects like this: >> dmcs /debug+ /warn:4 ./dynamic.cs /out:a.out >> >> However, when I run it get this error: >> WARNING: The runtime version supported by this application is >> unavailable. >> Using default runtime: v1.1.4322 >> The assembly mscorlib.dll was not found or could not be loaded. >> It should have been installed in the `/usr/lib/mono/1.0/mscorlib.dll' >> directory. >> >> I'm running 2.10 and I've got it installed in /usr/local/lib.... >> but I don't have a 1.0 directory at all, only 2.0, 3.5 and 4.0 in >> /usr/local/lib/mono >> >> I thought maybe I should be using mcs, not dmcs, but I can't get that to >> compile: >> ./dynamic.cs(2,14): error CS0234: The type or namespace name `Dynamic' >> does not exist in the namespace `System'. Are you missing an assembly >> reference? >> ./dynamic.cs(14,40): error CS0246: The type or namespace name >> `InvokeMemberBinder' could not be found. Are you missing a using directive >> or an assembly reference? >> >> What compile flags should I be using to target the 4.0 runtime? >> >> ~ >> Doug. >> >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
