CentoS 5.5 - lipthread.so issue with cmake MyDumper 0.2.3

Asked by Rob Duncan on 2012-11-15

I've been trying to install mydumper on a CentoS server; I've been researching for a few hours and cannot find a solution to the problem I am having when I use cmake .

Hope someone here might be able to point me in the right direction.

Thanks
-Rob

Here is the output when I do run the command:

$ cmake .
-- Using mysql-config: /usr/bin/mysql_config
-- Found MySQL: /usr/include/mysql, /usr/lib64/mysql/libmysqlclient.so;/usr/lib64/libpthread.so;/lib64/libz.so;/usr/lib64/libm.so;/usr/lib64/librt.so;/usr/lib64/libssl.so;/usr/lib64/libcrypto.so;/usr/lib64/libdl.so
-- Configuring done
CMake Warning at CMakeLists.txt:26 (add_executable):
  Cannot generate a safe runtime search path for target mydumper because
  files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libpthread.so] in /usr/lib64 may be hidden by files in:
      /lib64

  Some of these libraries may not be found correctly.

CMake Warning at CMakeLists.txt:29 (add_executable):
  Cannot generate a safe runtime search path for target myloader because
  files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libpthread.so] in /usr/lib64 may be hidden by files in:
      /lib64

  Some of these libraries may not be found correctly.

-- Generating done
-- Build files have been written to: /home/software/mydumper-0.2.3

Question information

Language:
English Edit question
Status:
Solved
For:
MySQL Data Dumper Edit question
Assignee:
No assignee Edit question
Solved by:
Rob Duncan
Solved:
2012-11-19
Last query:
2012-11-19
Last reply:
2012-11-19
Domas Mituzas (domas-mituzas) said : #1

Does 0.5.2 fix your sisues?

Rob Duncan (rob-duncan-2972) said : #2

This can be closed, I got this up and running on a spare ubuntu server.

I was just going to come and update my post this morning, you beat me to it!

Thank you
-Rob

I was having a similar issue but with libz.so
The problem was that for a reason unkown, the lib exists like a symbolic link in /usr/lib64 but was linked to an incorrect location (an inexistent libz.so.1.2.3)
I just remove the bad ln and create a new (and correct one)