Re: back to an old problem

[Jack <ostroffjh sbcglobal net>]

Well,  I'm finally getting back to spending some time trying to get  
this to work, still with no luck.

I do not find libgtk-win32 anywhere.  As I said, it is mapped in the  
gac to libgtk-x11, which is in /usr/lib/....  Should there be a copy of  
it in /usr/local/lib/f-spot?  That directory has lots of .dll files,  
some with an associated .mdb  and some with a .config.  The only .so in  
that directory is libfspot.so.  However, both FSpot.Gui.dll.config and  
Hyena.Gui.dll.config include a line mapping libgtk-win32-2.0-0.dll to  
libgtk-x11-2.0.so.0.

Any suggestions on further troubleshooting would be greatly appreciated.

Jack


On 2015.03.29 15:47, Matthieu Nguyen wrote:
> I recall having a problem with a dll like that because it was somehow  
> copied to the bin folder without a .dll.config to go with it, so in  
> the end F-Spot was trying to load the .dll from the  
> /usr/local/lib/f-spot/ folder which was missing the .config linking  
> to the proper .so, rather than taking the lib from the gac.
>
> Check what you have in your /usr/local/lib/f-spot folder, just in  
> case...
>
> On Sun, Mar 29, 2015 at 9:19 PM, Jack <ostroffjh sbcglobal net> wrote:
> > As I said in the other thread, I have gotten f-spot from git-head to  
> > compile, but I still get a dll not found error on  
> > libgth-win32-2.0-0.dll. This seems odd, because that library is in a  
> > dllmap in the gac for both gnome-sharp and gtk-sharp, both pointing  
> > to target="libgtk-x11-2.0.so.0" which exists in both /usr/lib32 and  
> > /use/lib64, and is loaded before, and is searched in both before and  
> > immediately after the error, if I run f-spot with  
> > MONO_LOG_LEVEL=debug.
> >
> > I've found this error referenced in a few bug reports (f-spot and  
> > other apps) but no definitive solution, just claims that something  
> > wasn't installed correctly.  It seems as if neither of those two  
> > dllmap entries is being read.  I could try putting it explicitly in  
> > f-spot.exe.config, but I don't know if that's really a good solution  
> > for the long run, or just a quick work-around.
> >
> > Any thoughts or suggestions?