Subject: Re: build failure in devel/glibmm
To: Joerg Sonnenberger <joerg@britannica.bec.de>
From: Steven M. Bellovin <smb@cs.columbia.edu>
List: pkgsrc-users
Date: 08/29/2006 13:14:22
On Tue, 29 Aug 2006 18:32:16 +0200, Joerg Sonnenberger
<joerg@britannica.bec.de> wrote:
> 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... (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.
>
Ahh -- thanks!
--Steven M. Bellovin, http://www.cs.columbia.edu/~smb