Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#3782 - libgpod missing .la

Attached to Project: Arch Linux
Opened by Lou (cmf) - Sunday, 15 January 2006, 10:42 GMT
Last edited by Dale Blount (dale) - Sunday, 15 January 2006, 17:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To arjan timmerman (blaasvis)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I relalise most .la files were removed during the libtool slay, however it's resulted in an issue with libgpod and amarok svn.

In amarok svn g_object_get is called, meaning during compilation amarok tries to link to the a .la normally owned by libgpod, because it's been removed compilation fails.

Just wondered what the correct procedure would be here, or if it can be fixed.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Monday, 23 January 2006, 09:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  patched the .pc file shoudl work now.
Comment by Martin Aumueller (aumuell) - Sunday, 15 January 2006, 10:54 GMT
amaroK's iPod plugin depends on calling g_object_get for determining the iPod model. g_object_get is normally defined in libgobject-2.0, and on most distributions this symbol is resolved via transitivity when linking with libgpod. This fails on arch because of the missing
The really serious problem is that the configure check for g_object_get is successful when linking with libgpod. So I don't have a possibility to know if it is necessary to add libgobject to the list of dependencies.
Comment by Jan de Groot (JGC) - Monday, 16 January 2006, 20:24 GMT
[root@jan ~]# pkg-config --libs --cflags libgpod-1.0
-I/usr/include/gpod-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lgpod -lglib-2.0

Libtool files are evil things, please use pkg-config, which is much cleaner these days. When checking for libgpod, use "pkg-config --exists libgpod-1.0" to determine if libgpod exists. Use the --cflags and --libs option to get the cflags and the required libs.
Comment by Martin Aumueller (aumuell) - Monday, 16 January 2006, 20:37 GMT
Of course we use pkg-config for finding what it takes to use libgpod. Alas, the --libs output does not include libgobject.
So you mean we should file a bug against libgpod in order to include all the relevant libs in its pkgconfig file? If that includes libgobject, then this should probably solve our problem.
Comment by Jan de Groot (JGC) - Monday, 16 January 2006, 21:05 GMT
Hmm, glib-2.0 is something else than gobject, sorry for that. This looks like an issue in the libgpod pkgconfig files. The gobject-2.0 dependency should be in there, since several internal features in libgpod which are exported as public api use the g_object_get/set functions, which are only available in gobject-2.0. The glib-2.0 dependency in libgpod.pc should be replaced with a gobject-2.0 dependency.