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

Thiago Macieira thiago at
Wed May 23 18:29:31 BST 2007

Matthew Woehlke wrote:
>Thiago Macieira wrote:
>> Matthew Woehlke wrote:
>>> Anyway I've worked around it for now by adding
>>> /usr/local/kde/gcc4/lib/gcc/i686-pc-linux-gnu/4.1.2 to my
>>> LD_LIBRARY_PATH, but I'm still confused as to *why* I need to do
>>> this.
>> Because
>> 1) /usr/local/kde/gcc4/lib/gcc/i686-pc-linux-gnu/4.1.2 isn't in your
>> RPATH and 2) /usr/lib/ isn't suitable
>> Given the path above, I doubt that CMake even knew about it. So it
>> wasn't ever considered as an -L or rpath parameter.
>I thought the linker set rpaths? If not, what do I need to do to tell
>cmake to pay attention to the rpaths gcc knows about? (Would this
>qualify as a cmake bug?)

The linker sets the rpaths, but it has to be told which paths to set. 
That's CMake's job: to determine which paths should be passed on to the 
linker and, also important, in which order.

This is not a CMake bug. It's the simple fact that your gcc probably 
passes -L/usr/local/kde/gcc4/lib/gcc/i686-pc-linux-gnu/4.1.2 to the 
linker on its own.

I'm not sure how to make it reveal the paths.

  Thiago Macieira  -  thiago (AT) - thiago (AT)
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <>

More information about the kde-core-devel mailing list