[MonoDevelop] build fail
"Andrés G. Aragoneses"
knocte at gmail.com
Wed Feb 26 20:43:59 UTC 2014
On 25/02/14 18:59, Bric wrote:
> On 02/22/2014 05:54 PM, Bric wrote:
>> On 02/22/2014 01:01 PM, "Andrés G. Aragoneses" wrote:
>>> On 22/02/14 11:18, Bric wrote:
>>>> started compiling from latest git, got this error:
>>>>
>>>> http://www.flight.us/misc/monodevelop_build_fail1.txt
>>>>
>>>> thanks.
>>>>
>>> >From reading this in your log:
>>>
>>> /data/installers/git/monodevelop/main/Main.sln (default targets) ->
>>> (Build target) ->
>>> /data/installers/git/monodevelop/main/src/addins/MonoDevelop.GtkCore/libstetic/libstetic.csproj
>>>
>>> (default targets) ->
>>> /usr/local/lib/mono/4.5/Microsoft.CSharp.targets (CoreCompile target) ->
>>>
>>> ClassDescriptor.cs(186,23): error CS0012: The type `GLib.IIcon' is
>>> defined in an assembly that is not referenced. Consider adding a
>>> reference to assembly `gio-sharp, Version=3.0.0.0, Culture=neutral,
>>> PublicKeyToken=35e10195dab3c99f'
>>>
>>> It appears that you tried to install gtk-sharp from the master branch
>>> (or gtk-sharp 3.0)? MonoDevelop uses gtk-sharp 2.x, not 3.x.
>>
>> Thanks. OK, I did "make uninstall" in the gtk-sharp source tree. I
>> don't see the offending version in this my new build error:
>>
>> http://www.flight.us/misc/build_error2.txt
>>
>> a bunch of "could not find file" messages... I have libpango dev,
>> libatk dev , etc installed. May have missed a few, but the error
>> mentions pango and atk. What gives?
>>
>> still mentions glib-sharp, and I don't know where to find that.
>>
>> thanks
>>
>
> just a <bump>
>
> I have been updating the git source and re-trying the past few days.
> Same EXACT error messages, since after removing gtk-sharp3 ...
>
> $ diff build_error2.txt build_error5.txt
> 15c15
> < Build started 2/22/2014 5:34:25 PM.
> ---
> > Build started 2/25/2014 12:46:57 PM.
> 1803c1803
> < Time Elapsed 00:00:08.7218890
> ---
> > Time Elapsed 00:00:19.8191080
>
Sometimes, removing gtk-sharp3 is not enough for xbuild to stop
"finding" it. This is a bug, which may still be unresolved in your
version of mono: https://bugzilla.xamarin.com/show_bug.cgi?id=11133
There's a workaround in the bug.
More information about the Monodevelop-list
mailing list