Ticket #1125 (new defect)

Opened 7 years ago

Last modified 7 years ago

cave fix-linkage doesn't find all broken libs and packages

Reported by: doggie Owned by:
Priority: Sometime Milestone:
Component: clients/cave Version: 0.58.5
Keywords: Cc:
Blocked By: Blocking:
Distribution: N/A

Description

cave fix-linkage finds 7 broken packages, while revdep-rebuild finds 39!

I'll attach all necessary logs.

Attachments

cave.log Download (11.5 KB) - added by doggie 7 years ago.
cave fix-linkage
revdep-rebuild.log Download (73.5 KB) - added by doggie 7 years ago.
revdep-rebuild -p
revdep-rebuild_cache.tar.bz2 Download (90.6 KB) - added by doggie 7 years ago.
/var/cache/revdep-rebuild/*.rr
cave_info.log Download (5.8 KB) - added by doggie 7 years ago.
cave info
emerge_info.log Download (6.2 KB) - added by doggie 7 years ago.
emerge --info (USE, etc. not up to date)

Change History

Changed 7 years ago by doggie

cave fix-linkage

Changed 7 years ago by doggie

revdep-rebuild -p

Changed 7 years ago by doggie

/var/cache/revdep-rebuild/*.rr

Changed 7 years ago by doggie

cave info

Changed 7 years ago by doggie

emerge --info (USE, etc. not up to date)

comment:1 Changed 7 years ago by ciaranm

Looks like revdep-rebuild is doing something with .la files that we're not.

dleverton?

comment:2 Changed 7 years ago by doggie

Do you need a cave -L d fix-linkage log? It's very noisy.

comment:3 Changed 7 years ago by ciaranm

Probably not. At least, not until I find out what exactly's supposed to happen with .la files...

comment:4 Changed 7 years ago by dleverton

broken /usr/lib64/libavahi-ui.la (requires -lglitz-glx)

(and similar)

The problem here is that we don't currently verify -l flags in .la files, only references from one .la to another. (Assuming there's only one problem, that is.)

First question that comes to mind: does the quoted example only require libgliz-glx.so with the same arch as /usr/lib64/libavahi-ui.so, or for every arch for which libavahi-ui.so exists? I think the former makes more sense, but I'm not sure exactly how libtool is supposed to interact with multilib.

comment:5 Changed 7 years ago by ciaranm

Why would a -l be issued for something not in dependency_libs?

Note: See TracTickets for help on using tickets.