Hi, On Wed, Jul 13, 2011 at 04:45:50PM -0000, Rodney Dawes wrote: > OK. I am wondering because we presumably should also use this for our > nightlies builds. But we use the same debian/ dir to build for all > supported versions of Ubuntu, so that we can keep things consistent, > without having to make the same changes N times in N different ways.
That is exactly what using mono-csc gives you. It means that you use the default mono compiler. The reason we're noticing problems now is that this switched from gmcs to dmcs with 2.10 and as libu1 wasn't using the default compiler correctly it was getting 2.0 refs instead of 4.0. You should use this for your nightlies indeed. > And it seems like requiring anyone who builds something on Oneiric to > manually specify the new version by setting MONO_CSC when doing > ./configure is a bit much. Is there no easy way to discover this > automatically? With alternatives or something? It's not required. mono-csc is more to help ensure that all of our packages get built for the distro's default profile. But it's backwards compatible: 4.0 apps can load 2.0 libs just fine. Users don't have to care about this. Cheers, Iain -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/809460 Title: Use default mono compiler correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libubuntuone/+bug/809460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
