[Mono-dev] olive without recompile mono

Atsushi Eno atsushi at ximian.com
Tue Jul 22 03:09:59 EDT 2008


Ahh, do not worry. I didn't mean you must demand stable use. As it
is written on our wiki, olive is a workplace for unstable stuff,
mostly for .NET 3.0 and later, and hence it cannot be stable by
its nature. When we hack olive, we make some or many changes in
mono (mostly class libs), and we cannot wait for its release for,
say, half a year.

Having said that, since there isn't a lot of changes in olive and
mono in sync lately, such mismatches between olive trunk and mono
release wouldn't likely to happen once the next 2.0 beta release
gets out.

Atsushi Eno


buhochileno at gmail.com wrote:
> Ok thanks Atsushi...but, I was able to download olive from svn sources 
> and compile just olive without recompile all my mono installation, also 
> I find some olive RPM's in opensuse repos, also work whitout problems, 
> so now I'm able to use my dependence, very happy :-) , but of course as 
> you say, probably compile all from sources is the best choice to be sure 
> that all is working properly...
> Sorry "demand"?, I was just asking for "options" nothing more...If you 
> think that "is not posible", ok, it was just a question not a "demand 
> for stable use", I really apreciate all the great effor that all of you 
> made in all the mono related aspects...
> 
> About my cross posting thanks for the clarification, no idea about the 
> separation ...
> 
> Thanks Atsuchi..
> 
> Mauricio
> 
> Atsushi Eno wrote:
>> Olive will always be mono and mcs from trunk, so no, you have to always
>> build mono from svn. Olive is defined as "under heavy development"
>> stuff. We don't welcome those who demand stable use of it. And of
>> course forcing dependent stuff is the only good idea.
>>
>> Once the next version of mono is released, you'll be able to build
>> olive (if you are not very unlucky).
>>
>> BTW (as you are cross posting to moonlight-list) olive has nothing
>> to do with moonlight anymore.
>>
>> Atsushi Eno
>>
>>
>> buhochileno at gmail.com wrote:
>>   
>>> Hi guys:
>>>
>>> Curently is not posible for our development team to change the 
>>> development environment (fedora OS, mono version, etc..) and we have a 
>>> pretty new ones of all..but due to a new dependence, we need olive I 
>>> find a RPM in some opensuse repo but claim that need mono 2.1 and of 
>>> course force things is not a good idea, also recompile all mono to allow 
>>> a compilation from source of olive is also not a option for us...
>>>
>>> there are is any other option?, make a rpm from olive sources?, compile 
>>> olive soirce with my curently installed mono version?, how can I check 
>>> if my mono version is able to compile olive?, mono --version give me this:
>>>
>>> Mono JIT compiler version 104788 (tarball)
>>> Copyright (C) 2002-2008 Novell, Inc and Contributors. www.mono-project.com
>>>         TLS:           __thread
>>>         GC:            Included Boehm (with typed GC)
>>>         SIGSEGV:       normal
>>>         Notifications: epoll
>>>         Architecture:  x86
>>>         Disabled:      none
>>>
>>>
>>> any other sugestion?
>>>
>>> Thanks
>>>
>>> Mauricio
>>>
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
>>>     
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>   
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 



More information about the Mono-devel-list mailing list