|Summary:||mono-1.1.2 works on amd64 but 2004.3 has -mono in profile|
|Product:||Gentoo Linux||Reporter:||Martin Allchin <mallchin>|
|Component:||New packages||Assignee:||AMD64 Project <amd64>|
|Package list:||Runtime testing required:||---|
|Bug Depends on:||120100|
Description Martin Allchin 2005-04-01 11:45:22 UTC
The mono use flag is hard-set in 2004.3 for amd64, yet I have successfully compiled and tested several mono apps. Can we remove the hard-set use flag and enable/disable mono use flag in make.conf as usual. Reproducible: Always Steps to Reproduce: 1. Compile an app with mono support, eg 'emerge -pv dbus' 2. 3. Actual Results: [ebuild R ] sys-apps/dbus-0.23.4 +X -debug +gtk (-mono) +python -qt +xml2 Expected Results: [ebuild R ] sys-apps/dbus-0.23.4 +X -debug +gtk +mono +python -qt +xml2
Comment 1 Peter Johanson (RETIRED) 2005-04-01 11:56:30 UTC
We really can't do this yet. mono-1.0.x on amd64 doesn't offer the necessary tools, only mono-1.1.x does (for amd64, other arches 1.0.x is enough). Unmasking the USE flag requires mono-1.1.x to be out of package.mask, which it won't be for at least another 2 weeks, if not significantly longer. If you remove that mask before we have a 1.1.x stable (or at least out of package.mask), prepare for massive breakage. When it does come time to get that USE flag back, you'll also have to do something along the lines of: mono? ( dev-lang/mono amd64? ( >=dev-lang/mono-1.1.4 ) ) in order to make sure that amd64 has a new enough mono which includes the amd64 JIT.
Comment 2 Danny van Dyk (RETIRED) 2005-04-01 16:09:23 UTC
Peter: No, we will stabilise mono-1.1.4 as soon as possible and then package mask all lesser version. That way, we don't need to modify each ebuild depending on mono in the tree.
Comment 3 Martin Allchin 2005-04-02 12:57:46 UTC
Sounds like a plan, I can confirm mono-1.1.2 works on amd64 too, I have it built and have tested several apps (namely beagle) If you need extra testing on mono before it's unmasked I am willing to help :)
Comment 4 Mark Rosenstand 2005-06-04 09:04:06 UTC
Now that mono-1.1* is in ~amd64, it would be nice if you either removed the mono USE-flag from use.mask or gave instructions on how to override.
Comment 5 Simon Stelling (RETIRED) 2005-06-04 09:11:10 UTC
we can't unmask it since it's not yet stable but we have packages marked stable that use the mono flag. unmasking it would screw up the dependency tree. you could just take mono out of default-linux/amd64/use.mask
Comment 6 Simon Stelling (RETIRED) 2005-06-04 09:17:50 UTC
sorry, just changing the profile itself is a bad idea, since it will be overwritten everytime you sync, but `echo "-mono" >> /etc/portage/profile/use.mask` is a nice solution
Comment 7 Mark Rosenstand 2005-06-04 09:29:41 UTC
(In reply to comment #6) > sorry, just changing the profile itself is a bad idea, since it will be > overwritten everytime you sync, but `echo "-mono" >> > /etc/portage/profile/use.mask` is a nice solution I discovered that, but thanks anyway. Maybe it'd be an idea to einfo amd64 users about that in the mono ebuild?
Comment 8 Simon Stelling (RETIRED) 2005-06-04 11:18:24 UTC
i don't think that we should explain portage's functionality in an ebuild, man portage already covers that. and the use flag will get out of use.mask soon anyway...
Comment 9 Simon Stelling (RETIRED) 2005-07-12 06:14:08 UTC
we have to wait for mono-1.1.7 becoming stable to unmask the use flag
Comment 10 Mike Doty (RETIRED) 2006-03-08 06:50:07 UTC
I hope we're still not talking about the 2004.3 profile like the summary suggests
Comment 11 Luis Medinas (RETIRED) 2006-03-19 16:52:50 UTC
mono 220.127.116.11 is stable on amd64 and the use mask has been removed. Really close this bug.