'Re: Still trying to compile f-spot'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       f-spot-list
Subject:    Re: Still trying to compile f-spot
From:       Jack <ostroffjh () sbcglobal ! net>
Date:       2015-03-21 22:19:14
Message-ID: 1426976354.7086.10 () ffortso4
[Download RAW message or body]

Well, I managed to install mono 3.12, and got f-spot to compile without  
error, but crashes on startup with a popup starting
---------------------
An unhandled exception was thrown: libgtk-win32-2.0-0.dll
   at (wrapper managed-to-native) GtkBeans.Builder:gtk_builder_get_type  
()
   at GtkBeans.Builder.get_GType () [0x00000] in <filename unknown>:0
   at GtkSharp.GtkbeansSharp.ObjectManager.Initialize () [0x00000] in  
<filename unknown>:0
   at GtkBeans.Builder..cctor () [0x00000] in <filename unknown>:0
An exception was thrown by the type initializer for GtkBeans.Builder
   at FSpot.MainWindow..ctor (FSpot.Database.Db db) [0x00000] in  
<filename unknown>:0
   at FSpot.App.get_Organizer () [0x00000] in <filename unknown>:0
   at FSpot.App.HandleOrganize () [0x00000] in <filename unknown>:0
   at FSpot.App.Organize () [0x00000] in <filename unknown>:0
   at FSpot.Driver.Startup () [0x00000] in <filename unknown>:0
   at Hyena.Gui.CleanRoomStartup.Startup  
(Hyena.Gui.StartupInvocationHandler startup) [0x00000] in <filename  
unknown>:0
.NET Version: 4.0.30319.17020
OS Version: Unix 3.17.8.1
---------------------

So - I wiped everything out and started from scratch, and now I get a  
compile error (omitting lots of warnings):
---------------------
/usr/lib64/mono/4.5/Microsoft.Common.targets:  warning : Reference  
'nunit.framework, Version=2.6.3.0, Culture=neutral,  
PublicKeyToken=96d09a1eb7f44a77' not resolved
GIOTagLibFileAbstractionTests.cs(31,7): error CS0234: The type or  
namespace name `Framework' does not exist in the namespace `NUnit'. Are  
you missing an assembly reference?
MetadataTest.cs(31,7): error CS0234: The type or namespace name  
`Framework' does not exist in the namespace `NUnit'. Are you missing an  
assembly reference?
SafeUriTests.cs(33,7): error CS0234: The type or namespace name  
`Framework' does not exist in the namespace `NUnit'. Are you missing an  
assembly reference?
SidecarXmpExtensionsTests.cs(34,7): error CS0234: The type or namespace  
name `Framework' does not exist in the namespace `NUnit'. Are you  
missing an assembly reference?
XdgThumbnailSpecTests.cs(32,7): error CS0234: The type or namespace  
name `Framework' does not exist in the namespace `NUnit'. Are you  
missing an assembly reference?
CSC:  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
Mono.Addins.Gui/HeaderBox.cs(148,10): warning CS0618:  
`Cairo.Context.Pattern' is obsolete: `Use GetSource/GetSource'
Makefile:1074: recipe for target 'sln_build' failed
make: *** [sln_build] Error 1
---------------------

The only reference to nunit.framework I find under mono is 2.4.8, so I  
wonder if I still have some version dependency issues

Jack

On 2015.03.12 13:19, Stephen Shaw wrote:
> If you want I think you'd be ok to just change the mono requirement  
> down to
> something like 3.2 instead. I think I bumped it to 3.6 because that  
> was the
> current version on my system at the time (I believe it is the version  
> that
> is on openSUSE right now).
> 
> On Thu, Mar 12, 2015 at 5:36 AM, Matthieu Nguyen  
> <nguyen.matthieu@gmail.com>
> wrote:
> 
> > I ran into the same problem recently (Mageia, the build people  
> trying
> > to get it back in the repos are having trouble because of the .NET
> > version updates in the last commits). Maybe, until somebody answers
> > regarding that commit, you could try a checkout to the commit just
> > before that one?
> >
> >
> > On Thu, Mar 12, 2015 at 1:43 AM, Jack <ostroffjh@sbcglobal.net>  
> wrote:
> > > After my last attempt in December, and getting distracted by all  
> sorts of
> > > other issues, I finally got back to trying to compile f-spot, and  
> am now
> > > caught because it requires mono 3.6 or higher.  This was upgraded  
> from
> > 2.2
> > > in a commit on 2014/12/22 "[Build] Clean up build files a bit".   
> I'd call
> > > this  more than a bit of change.  In my particular case (Gentoo)  
> the
> > highest
> > > mono available is 3.2.8, although 3.12 has been released, and  
> there is a
> > > Gentoo bug filed to get a newer version.
> > >
> > > Sorry to vent, but it's going to take me a while to get a new  
> enough mono
> > > installed (and who knows what other things I'll also have to  
> upgrade).  I
> > > also realized that my old, stable mono is gone, as I let lcms1 get
> > > uninstalled, so even though I packaged up the old version, it  
> wont do me
> > any
> > > good.  I only realized this when I found a bunch of photos on my
> > secondary
> > > computer that I want to either confirm as duplicates or else  
> actually
> > add to
> > > my collection.
> > >
> > > Thanks for ignoring my small rant.
> > >
> > > Jack
> > > _______________________________________________
> > > f-spot-list mailing list
> > > f-spot-list@gnome.org
> > > https://mail.gnome.org/mailman/listinfo/f-spot-list
> >
> >
> >
> > --
> > Matthieu Nguyen - ingénieur informatique
> > ENSEIRB promotion 2004 - Info, spé GL.
> > _______________________________________________
> > f-spot-list mailing list
> > f-spot-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/f-spot-list
> >
> 
_______________________________________________
f-spot-list mailing list
f-spot-list@gnome.org
https://mail.gnome.org/mailman/listinfo/f-spot-list
[prev in list] [next in list] [prev in thread] [next in thread] 