Crash when trying to compile MD from SVN

The problem is not with mono, but with boo. You need to
build boo using
the 2.0 profile, or use a boo configuration file which sets
the 2.0
runtime for boo. 

However, we need to find a workaround for this before the
next release.

Lluis.

El dl 17 de 07 del 2006 a les 08:28 +0200, en/na
"Andrés G. Aragoneses
[ knocte ]" va escriure:
> Thanks for your reply.
> 
> Rafael Teixeira escribió:
> > You need to compile mono with the 2.0 profile
also, to be able to
> > compile MD now that it is built with gmcs instead
of mcs.
> 
> Are you sure? (Then, can't we compile MD with a stable
mono package?)
> 
> I ask this because I have been always successful
compiling MD until now. 
> And the change to 2.0 features in MD has been made more
than one month 
> ago IIRC (and last week it was compiling fine).
> 
> BTW, this only happens for the Boo addin (if I don't
specify 
> "--enable-boo", the compilation works).
> 
> Regards,
> 
> 	Andrés	[ knocte ]
> 

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

On Mon, 2006-07-17 at 12:03 +0200, Lluis Sanchez wrote:
> The problem is not with mono, but with boo. You need to
build boo using
> the 2.0 profile, or use a boo configuration file which
sets the 2.0
> runtime for boo. 
> 
> However, we need to find a workaround for this before
the next release.
> 

I wonder if it is enough to add a .config file for each boo
exe that has
something like this (from NAnt.exe.config):
<configuration>
    <startup>
        <!-- .NET Framework 2.0 -->
        <supportedRuntime
version="v2.0.50727" />
        <!-- .NET Framework 2.0 Beta 2 -->
        <supportedRuntime
version="v2.0.50215" />
        <!-- .NET Framework 2.0 Beta 1 -->
        <supportedRuntime
version="v2.0.40607" />
        <!-- .NET Framework 1.1 -->
        <supportedRuntime version="v1.1.4322"
/>
        <!-- .NET Framework 1.0 -->
        <supportedRuntime version="v1.0.3705"
/>
    </startup>
</configuration>

seems to work here

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

John Luke escribió:
> On Mon, 2006-07-17 at 12:03 +0200, Lluis Sanchez wrote:
>> The problem is not with mono, but with boo. You
need to build boo using
>> the 2.0 profile, or use a boo configuration file
which sets the 2.0
>> runtime for boo. 
>>
>> However, we need to find a workaround for this
before the next release.
>>
> 
> I wonder if it is enough to add a .config file for each
boo exe that has
> something like this (from NAnt.exe.config):
> <configuration>
>     <startup>
>         <!-- .NET Framework 2.0 -->
>         <supportedRuntime
version="v2.0.50727" />
>         <!-- .NET Framework 2.0 Beta 2 -->
>         <supportedRuntime
version="v2.0.50215" />
>         <!-- .NET Framework 2.0 Beta 1 -->
>         <supportedRuntime
version="v2.0.40607" />
>         <!-- .NET Framework 1.1 -->
>         <supportedRuntime
version="v1.1.4322" />
>         <!-- .NET Framework 1.0 -->
>         <supportedRuntime
version="v1.0.3705" />
>     </startup>
> </configuration>
> 
> seems to work here

I don't know if this proposal was used for the purpose, but
FYI now with
the 0.7.6 version of boo (whose RPM depends now on NAnt), MD
compiles
correctly with --enable-boo.

Regards,

	Andrés	[ knocte ]

-- 

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st