As far as I understood it, even with an old mcs in the PATH it should first try to use that one, detect that it is too old/doesn't work and then fallback to the monolite directory. So it should "just work" :) -- Alex > Date: Fri, 17 Apr 2015 18:23:21 +0200 > From: fab...@canvon.de > To: mono-devel-list@lists.ximian.com > Subject: Re: [Mono-dev] Build failure on ARMv6/Raspberry Pi with > Raspbian/armhf > > * Alexander Köplinger (Fri, 17 Apr 2015 17:40:28 +0200): > > > > > That worked. I'd suggest the README.md would be updated, though, as it > > > specifically says to use monolite with EXTERNAL_MCS for bootstrapping > > > (under "If you don't have a working Mono installation"). It should say to > > > remove any existing gmcs from the $PATH, instead. > > > > That came up before already and we updated the readme, looks like you don't > > have the latest version: > > https://github.com/mono/mono#if-you-dont-have-a-working-mono-installation > > > > -- Alex > > Yes, I'm using mono-3.12.0-branch (to get a stable version) where it is > not updated yet. > > > Also I'd suggest to change > > | The build will then use the files downloaded by `make get-monolite-latest`. > > to > > | The build will then use the files downloaded by `make get-monolite-latest`, > | as long as there is no existing gmcs in $PATH. > > (or something on that lines) so people won't accidentally end up with the > wrong > bootstrap compiler. Or is that no longer correct on the master branch? > > Regards, Fabian > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
