meinproc4 broke? ("version `GLIBCXX_3.4.5' not found")

Matt Rogers mattr at kde.org
Tue May 22 22:25:01 BST 2007


On Tuesday 22 May 2007 16:07, Matthew Woehlke wrote:
> Matthew Woehlke wrote:
> > Ok, last I checked it isn't Monday... everyone else can build kdelibs,
> > right? I'm getting this:
> >
> > [ 77%] Generating index.cache.bz2
> > /usr/local/kde/home/build/kde-trunk-svn/kdelibs/bin/meinproc4:
> > /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.5' not found (required by
> > /usr/local/kde-trunk-svn/lib/libstreamanalyzer.so.0)
> > make[2]: *** [doc/sonnet/index.cache.bz2] Error 1
> >
> > 'ldd' doesn't like meinproc4 either, so it seems something is going
> > amiss when linking it. I've tried deleting my entire kdelibs build tree
> > with no change. Meanwhile I guess I'll start walking back in history to
> > try to isolate the change that broke meinproc4.
> >
> > I'm using:
> > $ which gcc
> > /usr/local/kde/gcc4/bin/gcc
> > $ gcc --version
> > gcc (GCC) 4.1.2
> > Copyright (C) 2006 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.  There is
> > NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> > $ /usr/bin/gcc --version # shouldn't be used?
> > gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.1)
> > Copyright (C) 2004 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.  There is
> > NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
>
> never mind, it's not meinproc4, it's just that meinproc4 is the only (or
> at least, first) broken thing being run by the build system... somehow
> *everything* got hosed (all the way back to strigi). The only thing
> that's changed since things worked was that I updated (svn up)
> yesterday, I'm even in the same shell session I've been running in for
> weeks.
>
> What changed this weekend that broke the KDE build system on my box?

have you cleaned your build dirs or at the very least, removed your 
CMakeCache.txt file in the build dirs? If not, go back and clean you build 
dirs and try again. 
-- 
Matt




More information about the kde-core-devel mailing list