Re: build failure in devel/glibmm

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

On Tue, 29 Aug 2006 18:34:56 +0200, Bernd Ernesti 
<netbsd%lists.veego.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...
> 
> That is not so easy. I usually change to /usr/pkg/lib and execute a
>  ldd *.so | less
> and search for the old library.
> That may not find all libaries, because not all of the shared libaries
> have one which ends with .so but the majority have such a file.
> This avoids to get multiple matches for the same library, because
> of the symlinks there.

That's what I was afraid you were going to say....

> 
> One thing which you could do is to move the old libaries to a different 
> location,
> like a backup directory somewhere else then /usr/lib. This makes it easier to
> find programs and libraries which still depends on it, because then you will
> get a 'not found' entry from the ldd command.
> 
> Like you said, you should check /usr/pkg/bin and sbin too and maybe some other
> locations like qt3, ezm3 or ....

As a project, we need to think of a better solution.  Many people will
have such files in private directories, too.

> > (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)
> 
> I remeber sawing a mail from you, but haven't checked that part.
> Please open a pr so this is not getting lost.
> 
Actually, I thought I had; I only discovered I hadn't when I composed
that note and wanted to cite the PR#.  Will do. 


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