Description of problem: When trying to compile a project monodevelop says "Framework 'Mono / .NET 3.5' is not installed" although all mono-related stuff is installed. Version-Release number of selected component (if applicable): 2.2 alpha 1 How reproducible: Create a new project and click on compile. Actual results: The mentioned error message appears.
monodevelop console output: WARNING [2009-10-20 16:26:23Z]: mscorlib assembly not found for framework '3.5'. The framework may not be installed. I searched for the file: $ find /usr/lib64/mono -name "mscorlib*" output: /usr/lib64/mono/1.0/mscorlib.dll /usr/lib64/mono/1.0/mscorlib.dll.mdb /usr/lib64/mono/2.0/mscorlib.dll /usr/lib64/mono/2.0/mscorlib.dll.mdb /usr/lib64/mono/2.1/mscorlib.dll /usr/lib64/mono/2.1/mscorlib.dll.mdb
Found the problem: Monodevelop searches in /usr/lib instead of /usr/lib64 So the problem could have something to to with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=528952
The problem is caused by some hardcoded "lib" references in the sources of monodevelop. I've added a workaround for now. Because my access to an x86_64 system is limited to a console login (X forwarding is way too slow), I could only test it with "mdtool". But since I could reproduce the problem clearly even with this tool, I'm quite confident that the root cause is found and fully fixed. Please try out whether the following build works for you: https://koji.fedoraproject.org/koji/buildinfo?buildID=140150
(In reply to comment #3) > Please try out whether the following build works for you: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=140150 Works here. There's still some warnings about missing NUnit files, but that's probably a separate bug.
monodevelop-2.1.0-4.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/monodevelop-2.1.0-4.fc12
monodevelop-2.1.0-4.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update monodevelop'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-11420
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 539386 has been marked as a duplicate of this bug. ***
monodevelop-2.1.0-4.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
Not sure of best way to report this, but in current rawhide, monodevelop 2.2 on x86_64 has had this behaviour return. As a hack, linking /usr/lib/mono and /usr/lib/monodevelopy to the /usr/lib64 made the problem go away. can test with mdtool build as described above
File as a new bug, but to be honest, it looks like you've got the 32 bit packages installed as on a 64 bit system, MD should be in /usr/lib64
OK, will file a new bug. Perhaps the new build of monodevelop 2.2 does not include the fixes. I know some of the source add-in packages from the monodevelop site explicitly use lib and have no way of doing a lib64 FYI - rpm -qa | grep ^mono mono-ndoc-1.3.1-8.fc13.x86_64 mono-data-sqlite-2.6.1-1.fc13.x86_64 mono-nunit-2.6.1-1.fc13.x86_64 mono-wcf-2.6.1-1.fc13.x86_64 mono-addins-0.4-9.20091702svn127062.fc12.x86_64 mono-web-2.6.1-1.fc13.x86_64 monodoc-2.6.1-1.fc13.x86_64 mono-core-2.6.1-1.fc13.x86_64 mono-nunit22-2.2.10-12.fc13.x86_64 mono-data-2.6.1-1.fc13.x86_64 mono-sharpcvslib-0.35-14.fc13.x86_64 monodevelop-2.2.1-1.fc13.x86_64 mono-extras-2.6.1-1.fc13.x86_64 mono-winforms-2.6.1-1.fc13.x86_64 (all from rawhide in F12 x86_64 host) Cheers