diff options
author | Prarit Bhargava <prarit@redhat.com> | 2017-11-02 01:48:17 +0100 |
---|---|---|
committer | Shuah Khan <shuahkh@osg.samsung.com> | 2017-11-09 18:50:40 +0100 |
commit | d4dbfa4bb4c624636eeef9efc6d87c4b7bf2c611 (patch) | |
tree | 008dca090120b083591f4a78257828e1695806c9 /Documentation/extcon | |
parent | cpupower: Fix no-rounding MHz frequency output (diff) | |
download | linux-d4dbfa4bb4c624636eeef9efc6d87c4b7bf2c611.tar.xz linux-d4dbfa4bb4c624636eeef9efc6d87c4b7bf2c611.zip |
tools/power/cpupower: Add 64 bit library detection
The kernel-tools-lib rpm is installing the library to /usr/lib64, and not
/usr/lib as the cpupower Makefile is doing in the kernel tree. This
resulted in a conflict between the two libraries. After looking at how
other tools installed libraries, and looking at the perf code in
tools/perf it looks like installing to /usr/lib64 for 64-bit arches is the
correct thing to do.
Checks with 'ldd cpupower' on SLES, RHEL, Fedora, and Ubuntu result in
the correct binary AFAICT:
[root@testsystem cpupower]# ldd cpupower | grep cpupower
libcpupower.so.0 => /lib64/libcpupower.so.0 (0x00007f1dab447000)
Commit ac5a181d065d ("cpupower: Add cpuidle parts into library") added a
new cpupower library version. On Fedora, executing the cpupower binary
then resulted in this error
[root@testsystem cpupower]# ./cpupower monitor
./cpupower: symbol lookup error: ./cpupower: undefined symbol:
get_cpu_topology
64-bit libraries should be installed to /usr/lib64, and other libraries
should be installed to /usr/lib.
This code was taken from the perf Makefile.config which supports /usr/lib
and /usr/lib64.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Diffstat (limited to 'Documentation/extcon')
0 files changed, 0 insertions, 0 deletions