On Tue, Aug 29, 2006 at 12:10:41PM -0400, Steven M. Bellovin wrote:
> On Tue, 29 Aug 2006 17:56:25 +0200, Bernd Ernesti <netbsd@lists.veego.de>
> wrote:
> 
> > On Tue, Aug 29, 2006 at 11:45:25AM -0400, Steven M. Bellovin wrote:
> > [..]
> > 
> > > ld: warning: libstdc++.so.5, needed by /usr/pkgsrc/devel/glibmm/work/.buildlink/
> > > lib/libsigc-2.0.so, may conflict with libstdc++.so.6
> > 
> > My guess is that you still have libstdc++.so.5 from gcc3 on your system while
> > you now use gcc4 with libstdc++.so.6.
> > First rebuild all packages which still use libstdc++.so.5 and then we will know
> > if the error disapears.
> > 
> 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.

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 ....

> (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.

Bernd