[Mono-dev] [PATCH] Remove UnmanagedType_80
bmaurer at ximian.com
Mon Sep 5 16:41:56 EDT 2005
On Mon, 2005-09-05 at 20:01 +0200, Kornél Pál wrote:
> Using (UnmanagedType) 80 was required because there was a bug in mcs; it
> used I4 as the default ArraySubType instead of 80.
> This bug was fixed so we no more require Consts.UnmanagedType_80.
> Is it OK to commit the patch?
How new of a mcs do you need to compile?
Many people (buildbot and the rpm build machines being one example)
always compile mono by using an rpm install of mono-core for 1.1.n-1.
For example, right now, the buildbot/rpm build machines have mono
18.104.22.168 installed. After we release 1.1.9, we will rug up to that
This means that mono from svn must be buildable with a mono-core install
from the latest released version.
Our build setup would get alot more tricky if we need to depend on
getting monolites in the build system, so I don't think we would want to
break this policy.
Btw, there are a few other hacks like this that could potentially be
removed under the BOOTSTRAP_WITH_OLDLIB name.
More information about the Mono-devel-list