On Sat, Aug 12, 2006 at 08:47:55PM +0200, Mirco Bauer wrote:
> first I thought the compiler is broken, but then I saw CLR v2.0 which
> means _bad_ things.
> 
> I installed libmono2.0-cil which pulls the base CLR 2.0 packages in, and
> then booc didn't fail with that error, but with another saying the libs
> are not found. They libs are installed though, but since boo uses now
> CLR 2.0 it wants the 2.0 version of those libs (instead of 1.1 as
> before).
> 
> So I installed the 2.0 versions, and the build was happy, but I am not.
> 
> The resulting package depends on on the 2.0 runtime of Mono, because the
> compiler linked it against 2.0 instead of 1.1
> Unluckily this is a problem now.
> 
> I could add now the 2.0 stuff to monodevelop build deps but that is not
> fixing the cause. Boo must be able to link against 1.1 or 2.0 somehow,
> else all resulting libs or apps require 2.0 from now on.
> 
> C# solved this by having mcs (C# 1.0) which links against CLR 1.1 and
> gmcs (C# 2.0) which links against CLR 2.0
> 
> Also I noticed that boo is not correctly fetching the binary
> dependencies with dh_clideps, but I guess that must be some CDBS problem
> since no other package has the problem. Probably is the make target too
> early or too late or something. Then you would not need to manually
> depend on mono (which is btw a bad idea since its a meta-package with 2
> real deps).

Well, to be honest, I only switched to gmcs (and therefore 2.0)
because it seemed to be the default way for nant to build boo.
I had a bug where nant failed to find gmcs.  If you think its not
a good time to be switching to 2.0 i'll look at ways of switching
back or providing 2 version of boo, one built against 1.1 and
other build againt 2.0.  I suspect that the former will be good
enough for now.  I'll make sure I can build monodevelop before
uploading.

I'll certainly look into the dh_clideps problem, too.

-- 
sam clegg
:: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369
$superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $

Attachment: signature.asc
Description: Digital signature

Reply via email to