[Mono-dev] Building from Source Fails with mcs: Command not found

Alexander Köplinger alex.koeplinger at outlook.com
Thu May 21 11:19:31 UTC 2015

The basic.exe in monolite is mcs. I think you're heading down the wrong path, judging from your log it tries a system-wide mcs first (as expected) and then falls back to monolite because Mono isn't installed.
Invoking monolite's basic.exe fails though with "Illegal instruction", which points to some runtime issue.
-- Alex
> Date: Thu, 21 May 2015 03:38:02 -0700
> From: chaselton at gmail.com
> To: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-dev] Building from Source Fails with mcs: Command not	found
> More information:
> I examined the mcs and mono files in _tmpdir/bin after realizing they were
> created on the fly...they are shell scripts.  The mono script sets up some
> env variables...and does some other stuff I haven't looked to closely at
> yet.  The mcs script is this:
> #! /bin/sh
> exec "/bld/mono/mono-4.0.0/runtime/_tmpinst/bin/mono"
> "/bld/mono/mono-4.0.0/mcs/class/lib/build/mcs.exe" "$@"
> That's a space between the shebang and /bin/sh...and the second
> directory...mcs/class/lib/build...doesn't exist.  The directory
> mcs/class/lib/monolite does...but it doesn't contain mcs.exe...it contains
> build.exe and some other files.
> Thoughts?  Are the generated scripts incorrect or should monolite include a
> copy of mcs.exe
> --
> View this message in context: http://mono.1490590.n4.nabble.com/Building-from-Source-Fails-with-mcs-Command-not-found-tp4666000p4666007.html
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150521/f6da626d/attachment.html>

More information about the Mono-devel-list mailing list