[Mono-dev] monolite URL
Alex J Lennon
ajlennon at dynamicdevices.co.uk
Thu Dec 11 06:33:23 UTC 2014
On 11/12/2014 01:47, Alexander Köplinger wrote:
> Hey Alex,
> monolite is built and uploaded automatically by Wrench:
> the issue I think was that the build was broken there so a new
> monolite didn't get uploaded, this is now fixed.
Ah that explains a great deal. Thanks for explaining that to me.
> The thing to keep in mind is that the corlib version inside monolite
> needs to match the runtime version or bootstrapping the classlib build
> won't work, so you can't just keep an old monolite and use it to build
> newer Mono (at least that's how I understood it).
This is also news to me and very helpful to know thanks. I am not
disagreeing but I am surprised that we have to have an exactly matching
build of monolite for this, whereas we don't if using a "full-fat"
Mono. I wonder why that is? Because monolite is very barebones just for
bootstrapping purposes ?
> If you don't want to rely on monolite, another option is to
> just install a recent Mono release and use that for bootstrapping
> (e.g. right now the build still works with Mono 3.2).
Now I understand that the monolite package is auto-built I'd prefer to
use that. Although I've had ongoing issues on and off for long time with
missing old monolite archives and so forth.
In that case I will leave Appveyor using get-monolite-latest for now,
but the use of EXTERNAL_MCS I mentioned was, as you say, to attempt to
use the pre-installed Mono image they have on their "build worker" VM
images as standard.
Thanks again, much appreciated.
> -- Alex
> > Date: Thu, 11 Dec 2014 01:28:44 +0100
> > From: ajlennon at dynamicdevices.co.uk
> > To: alex.koeplinger at outlook.com; bperry.volatile at gmail.com;
> gacevedo at gmail.com
> > CC: mono-devel-list at lists.ximian.com
> > Subject: Re: [Mono-dev] monolite URL
> > On 10/12/2014 20:46, Gabriel Acevedo wrote:
> > > Thank you all. I built mono-3.8.0 yesterday, and I was able to get
> > > monolite-111 from the URL in Makefile without problems. I guess it
> > > changed today.
> > >
> > > Thanks again.
> > The Windows Appveyor builds have been broken for some days as when
> > mono_corlib_version (I think) changes, the monolite URL dependency
> > changes (?), but often the appropriate download isn't available, and
> > similarly sometimes old versions aren't available.
> > It would be great not to have this external dependency for build. I
> > started out trying to work-around this by removing the
> > get-monolite-latest step from the Appveyor config in favour of use of
> > EXTERNAL_MCS
> > I couldn't quite seem to hit the right incantations though and ran out
> > of time, but will revisit.
> > Cheers, Alex
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list