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#9983 - libgphoto2 2.4.0-5 should not delete *.la files

Attached to Project: Arch Linux
Opened by Paul Bredbury (brebs) - Thursday, 27 March 2008, 13:51 GMT
Last edited by Jan de Groot (JGC) - Sunday, 20 April 2008, 12:52 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jason Chu (jason)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Hi, libgphoto2 2.4.0-5 presumably should *not* contain this line:

rm -f ${startdir}/pkg/usr/lib/*.la

Otherwise, it is the only package I have installed which has lots of broken *.la links with findbrokenpkgs:


$ grep '^dependency_libs' /usr/lib/libgphoto2_port/0.8.0/
dependency_libs=' /usr/lib/ -lltdl -lusb'
$ ls /usr/lib/
ls: cannot access /usr/lib/ No such file or directory
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 20 April 2008, 12:52 GMT
Reason for closing:  Fixed
Comment by Jason Chu (jason) - Monday, 07 April 2008, 23:18 GMT
I don't know what you're saying. Should libgphoto2 include any .la files? Or should it include none?
Comment by Paul Bredbury (brebs) - Monday, 07 April 2008, 23:39 GMT
libgphoto2 should either delete *all* of its .la files (including the ones in *subdirectories* such as /usr/lib/libgphoto2_port/0.8.0/ ) or *none* of them. To avoid dangling references.

But, I don't use the package, so I can't test whether "Some packages need their .la files!" at is applicable.
Comment by Jan de Groot (JGC) - Tuesday, 08 April 2008, 06:39 GMT
libgphoto2 needs those .la files because it uses libtool to load its plugins. Without the .la files, the plugins can't be found.
Comment by Jason Chu (jason) - Tuesday, 08 April 2008, 07:05 GMT
So you're saying it shouldn't be libtool salyed at all? How is it working as it is now?
Comment by Jan de Groot (JGC) - Tuesday, 08 April 2008, 08:08 GMT
At this moment only the .la file for the library is missing. This file is referenced from all the other .la files, but somehow libtool's dlopen() methods don't care about that. The rm -f /usr/lib/*.la call should be removed from the PKGBUILD to fix these references.