View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0011914 | CMake | (No Category) | public | 2011-03-01 10:50 | 2016-06-10 14:31 | ||||
Reporter | Dominique Leuenberger | ||||||||
Assigned To | Kitware Robot | ||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | CMake 2.8.3 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0011914: rpath provided libs is ignored when using FindPackage | ||||||||
Description | I'm linking a library (libproxy for that matter) against another library providing a pkgconfig .pc file (mozilla-js for what it matters here). "pkg-config --libs mozilla-js" returns: -Wl,-rpath,/usr/lib64/xulrunner-2.0 -L/usr/lib64/xulrunner-devel-2.0b12/lib -lmozjs -lplds4 -lplc4 -lnspr4 -lpthread -ldl When building the module at the end, the rpath to /usr/lib64/xulrunner-2.0 does not exist, but one to /usr/lib64/xulrunner-devel-2.0b12/lib is inserted into the shared object, as seen here: readelf -a /usr/lib64/libproxy-0.4.6/modules/pacrunner_mozjs.so | grep rpath 0x000000000000000f (RPATH) Library rpath: [/usr/lib64/xulrunner-devel-2.0b12/lib] This is ignoring explicit build instructions provided by the pkgconfig file provider. | ||||||||
Steps To Reproduce | Have a .pc file that specifies explicit rpath for your linker. | ||||||||
Additional Information | An example of this happening is when building libproxy on openSUSE. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0030236) David Cole (manager) 2012-08-11 11:09 |
Sending old, never assigned issues to the backlog. (The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...) If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^] It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing. |
(0041810) Kitware Robot (administrator) 2016-06-10 14:28 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-03-01 10:50 | Dominique Leuenberger | New Issue | |
2012-08-11 11:09 | David Cole | Status | new => backlog |
2012-08-11 11:09 | David Cole | Note Added: 0030236 | |
2016-06-10 14:28 | Kitware Robot | Note Added: 0041810 | |
2016-06-10 14:28 | Kitware Robot | Status | backlog => resolved |
2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |