[ https://issues.apache.org/jira/browse/THRIFT-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282728#comment-16282728 ]
James E. King, III commented on THRIFT-4412: -------------------------------------------- You may want to explicitly add -L<prefix path> to force the linker to look there before going to the system library paths. Let me know if that resolves the issue. > thrift cmake does not use absolute library path, linking system libraries > ------------------------------------------------------------------------- > > Key: THRIFT-4412 > URL: https://issues.apache.org/jira/browse/THRIFT-4412 > Project: Thrift > Issue Type: Bug > Components: Build Process > Affects Versions: 0.10.0, 0.11.0 > Reporter: Mario Emmenlauer > > I build thrift using cmake on Linux. It works generally very good on many > platforms (I've tested Linux, Windows and MacOSX extensively). But one issue > is plaguing me. I have my own custom boost libraries, libevent and others. I > set {{CMAKE_PREFIX_PATH}} to their install directory. This generally also > works well, and cmake finds the libraries. However in the final Makefile, the > linker command uses {{-lxxx}} for library {{xxx}} instead of the usual cmake > absolute path {{/a/b/c/libxxx.so}}. This is a problem because {{ld}} suddenly > prefers the system libraries over my custom builds. This in turn breaks the > build for me. > I do not have this problem with any other cmake builds. And I tried various > workarounds to force cmake to use the absolute path, but failed. Did somebody > maybe add this on purpose? -- This message was sent by Atlassian JIRA (v6.4.14#64029)