How to build monodevelop?

tigerton · 11-05-2014, 03:02 PM

I'm trying to install monodevelop from this slackbuild:

http://slackbuilds.org/repository/14...t/monodevelop/

But I get the following message:

Quote:

: warning CS1701: Assuming assembly reference `Mono.Cairo, Version=2.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' matches assembly `Mono.Cairo, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'. You may need to supply runtime policy
gtk-gui/generated.cs(107,18): warning CS0436: The type `Stetic.ActionGroups' conflicts with the imported type of same name'. Ignoring the imported type definition
MonoDevelop.Debugger.Visualizer/TextVisualizer.cs(40,15): warning CS0414: The private field `MonoDevelop.Debugger.Visualizer.TextVisualizer.val' is assigned but its value is never used
: warning CS1701: Assuming assembly reference `Mono.Cairo, Version=2.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' matches assembly `Mono.Cairo, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'. You may need to supply runtime policy
make[1]: *** [sln_build] Error 1
make[1]: Leaving directory `/tmp/SBo/monodevelop-4.0.10'
make: *** [all-recursive] Errore 1

And I can't go on.... what can I do to solve it?

Thanks in advance.

willysr · 11-05-2014, 05:55 PM

Have you installed all the requirements?

tigerton · 11-06-2014, 01:06 AM

yes, I have all I need to build monodevelop.

Any suggestion?

55020 · 11-06-2014, 06:14 AM

First guess is that it might build ok if you don't use multiple jobs:

env MAKEFLAGS="-j1" sh ./monodevelop.SlackBuild

Second guess is that you are using an old SlackBuild (for Slackware 14.0) with an old version of monodevelop and/or old versions of its dependencies. Could you give us a list of your installed dependencies, including the version numbers? Even if you are using Slackware 14.0, perhaps you could try some of the SlackBuilds for 14.1 that build newer versions of mono, gtk-sharp, mono-addins and gnome-sharp. Or, better still, upgrade to Slackware 14.1, because we know that the build works on 14.1.

Edit: Third guess is that the warnings might not be the real problem: there might have been an error logged before them (possibly a *long* way before them).