[MonoDevelop] Running MonoDevelop on CentOS 7

Travis Paul Tr at vispaul.me
Mon Nov 3 17:13:13 UTC 2014


After a helpful suggestion to run with the --no-redirect flag, I have
a descriptive error message:

  ...
  Scanning file: /usr/lib/monodevelop/AddIns/NUnit/MonoDevelop.NUnit.dll
  WARNING: [MonoDevelop.NUnit,5.5] Could not load some add-in
assemblies: Could not find file
"/usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll"
  ...

This file exists but points to a broken symlink:

  $ file /usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll
  /usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll: broken symbolic
link to `/usr/lib/mono/nunit//lib/mono/gac/nunit.core'

Looking at the specfile for mono-core, it appears that nunit.core is
installed to %{_prefix}/lib/mono/gac/nunit.core

I manually symlinked to nunit.core thinking this would solve my issue
but I got the same error from MonoDevelop:
  $ sudo rm /usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll
  $ sudo ln -s /usr/lib/mono/gac/nunit.core
/usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll

  ...
  WARNING: [MonoDevelop.NUnit,5.5] Could not load some add-in
assemblies: Could not find file
"/usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll"
  ...

Then, I tried manually symlinking to a specific version and started
making progress (I got a different error)
  $ sudo ln -s /usr/lib/mono/4.5/nunit.core.dll
/usr/lib/monodevelop/AddIns/NUnit/nunit.core.dll
  $ monodevelop --no-redirect
  ...
  WARNING: [MonoDevelop.NUnit,5.5] Could not load some add-in
assemblies: Could not find file
"/usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll
  ...

So I fixed the resulting errors with symlinks:

  $ file /usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll
  /usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll: broken
symbolic link to `/usr/lib/mono/nunit/nunit.
  $ sudo rm /usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll
  $ sudo ln -s  /usr/lib/mono/4.5/nunit.core.interfaces.dll
/usr/lib/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll

  $ file /usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll
  /usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll: broken
symbolic link to `/usr/lib/mono/nunit/nunit.framework.dll'
  $ sudo rm /usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll
  $ sudo ln -s /usr/lib/mono/4.5/nunit.framework.dll
/usr/lib/monodevelop/AddIns/NUnit/nunit.framework.dll


And now I finally have MonoDevelop launching. I hope this information
helps someone in the future.


On Mon, Nov 3, 2014 at 11:10 AM, Travis Paul <Tr at vispaul.me> wrote:
> I apologize for the wrong hastebin link, the trace output is here:
> http://hastebin.com/kijixiwozu
>
>
> On Mon, Nov 3, 2014 at 11:08 AM, Travis Paul <Tr at vispaul.me> wrote:
>> I have installed mono-complete from the project's official yum repo.
>> When I run MonoDevelop, the program does not launch and there are no
>> error messages in the console.  I discovered that the monodevelop
>> command in my path was a shell script installed at
>> /usr/bin/monodevelop.  After viewing the script I have also tried
>> running MonoDevelop directly with:
>>
>>   exec -a monodevelop mono-sgen  "/usr/lib/monodevelop/bin/MonoDevelop.exe"
>>
>> I also tried adding --trace options to mono-sgen and --trace seems to
>> run in an infinite loop.  I've posted output here:
>> http://hastebin.com/misihoruqi
>>
>> I have been able to run the examples on the mono project's website so
>> mono itself seems to be installed and functioning correctly.  I am
>> running CentOS 7 x86_64.
>>
>> Any guidance or advice is greatly appreciated,
>> Travis Paul


More information about the Monodevelop-list mailing list