Re: build failure in devel/glibmm

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

On Tue, 29 Aug 2006 18:32:16 +0200, Joerg Sonnenberger
<joerg%britannica.bec.de@localhost> wrote:

> > How can I find such packages?  Pkgsrc dependencies show things in pkgsrc,
> > not those in the base system.  I suppose I could run 'find' and locate
> > all executables in /usr/pkg...  (There's another problem, though: one
> > package I have that I know uses libstdc++.so.5, psi, won't build now --
> > checksum failure on psi-0.10-20060806/psi_bg.qm)
> 
> Grep for REQUIRES.*libstdc\+\+\.so\.5 in /var/db/pkg/*/+BUILD_INFO or
> so. Or use pkg_info -B $foo with the same idea.
> 
For whatever reason, I found at least one package where that didn't work,
on three different machines: db4.

 $ ldd /usr/pkg/lib/libdb4_cxx-4.4.so
/usr/pkg/lib/libdb4_cxx-4.4.so:
        -lstdc++.5 => /usr/lib/libstdc++.so.5
        -lm.0 => /usr/lib/libm387.so.0
        -lm.0 => /usr/lib/libm.so.0
        -lgcc_s.1 => /usr/lib/libgcc_s.so.1

shows that it's used, but 

$ pkg_info -B db4 |grep REQUIRES    
REQUIRES=/usr/lib/libc.so.12
REQUIRES=/usr/pkg/lib/libdb4-4.4.so.4

claims that it isn't.  And yes, deleting db4 made that file go away, so
it wasn't just a left-over.


                --Steven M. Bellovin, http://www.cs.columbia.edu/~smb