After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 367259 - configuration script does not check for mono-cairo libraries
configuration script does not check for mono-cairo libraries
Status: RESOLVED NOTABUG
Product: f-spot
Classification: Other
Component: General
CVS
Other Linux
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-29 23:08 UTC by Patrick Wagstrom
Modified: 2006-11-01 21:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
error log from f-spot compilation (16.12 KB, text/plain)
2006-11-01 21:56 UTC, Patrick Wagstrom 		Details

Description Patrick Wagstrom 2006-10-29 23:08:20 UTC 
I'm running Ubuntu Edgy and I noticed that the configuration script for F-spot does not check for the mono-cairo libraries.  I was able to get past the ./configure to the point where it told me to run make to compile, however the compile died because I did not have mono-cairo installed.

Of course, installing mono-cairo fixes this, but it should be checked in the configuration script.
Comment 1 Larry Ewing 2006-11-01 21:43:25 UTC 
f-spot doesn't actually use the mono cairo bindings; It uses cairo directly.  What packages did you install to resolve the issue?
Comment 2 Patrick Wagstrom 2006-11-01 21:56:22 UTC 
Created attachment 75799 [details]
error log from f-spot compilation

This attachment shows the error generated by Make when I attempt to compile the package.
Comment 3 Patrick Wagstrom 2006-11-01 21:59:30 UTC 
It looks like the issue might actually be an Ubuntu issue.  To fix the error I installed libmono-cairo-2.0 which provides the following files:

[patrick@hedgehog] dpkg -L libmono-cairo2.0-cil
/.
/usr
/usr/lib
/usr/lib/mono
/usr/lib/mono/gac
/usr/lib/mono/gac/Mono.Cairo
/usr/lib/mono/gac/Mono.Cairo/2.0.0.0__0738eb9f132ed756
/usr/lib/mono/gac/Mono.Cairo/2.0.0.0__0738eb9f132ed756/Mono.Cairo.dll
/usr/lib/mono/gac/Mono.Cairo/2.0.0.0__0738eb9f132ed756/Mono.Cairo.dll.mdb
/usr/lib/mono/gac/Mono.Cairo/2.0.0.0__0738eb9f132ed756/Mono.Cairo.dll.config
/usr/lib/mono/2.0
/usr/share
/usr/share/doc
/usr/share/doc/libmono-cairo2.0-cil
/usr/share/doc/libmono-cairo2.0-cil/NEWS.Debian.gz
/usr/share/doc/libmono-cairo2.0-cil/copyright
/usr/share/doc/libmono-cairo2.0-cil/changelog.Debian.gz
/usr/lib/mono/2.0/Mono.Cairo.dll

However, it seems that it was not f-spot that was having the error, rather it was gdk-sharp which had the error.  I'm not sure if a workaround is needed for F-spot or not.  I'll file a bug with Ubuntu on this one because of a missed dependency on  their part and mark this as NOTABUG.