So I've built and installed kernel 4.13.0 with this patch in 18.04.
Building mate-applets with -lcpupower fails near the end with an unusual error message:
...................
dh_shlibdeps
dpkg-shlibdeps: error: no dependency information found for /usr/lib/libcpupower.so.4.13.0-32 (used by debian/mate-applets/usr/lib/mate-applets/mate-cpufreq-applet)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/mate-applets.substvars debian/mate-applets/usr/lib/mate-applets/command-applet debian/mate-applets/usr/lib/mate-applets/mate-drivemount-applet debian/mate-applets/usr/lib/mate-applets/mate-charpick-applet debian/mate-applets/usr/lib/mate-applets/accessx-status-applet debian/mate-applets/usr/lib/mate-applets/trashapplet debian/mate-applets/usr/lib/mate-applets/timer-applet debian/mate-applets/usr/lib/mate-applets/mate-geyes-applet debian/mate-applets/usr/lib/mate-applets/mate-multiload-applet debian/mate-applets/usr/lib/mate-applets/mate-netspeed-applet debian/mate-applets/usr/lib/mate-applets/mateweather-applet debian/mate-applets/usr/lib/mate-applets/battstat-applet debian/mate-applets/usr/lib/mate-applets/mate-cpufreq-applet debian/mate-applets/usr/lib/mate-applets/stickynotes-applet debian/mate-applets/usr/bin/mate-cpufreq-selector returned exit code 255
dh_shlibdeps: Aborting due to earlier error
debian/rules:10: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
-------------------
I've checked the contents of libcpupower1 and libcpupower-dev. Something's not right... Usually there's one real library and two symlinks to it, but here it's not so:
So I've built and installed kernel 4.13.0 with this patch in 18.04.
Building mate-applets with -lcpupower fails near the end with an unusual error message:
...................
dh_shlibdeps libcpupower. so.4.13. 0-32 (used by debian/ mate-applets/ usr/lib/ mate-applets/ mate-cpufreq- applet) mate-applets. substvars debian/ mate-applets/ usr/lib/ mate-applets/ command- applet debian/ mate-applets/ usr/lib/ mate-applets/ mate-drivemount -applet debian/ mate-applets/ usr/lib/ mate-applets/ mate-charpick- applet debian/ mate-applets/ usr/lib/ mate-applets/ accessx- status- applet debian/ mate-applets/ usr/lib/ mate-applets/ trashapplet debian/ mate-applets/ usr/lib/ mate-applets/ timer-applet debian/ mate-applets/ usr/lib/ mate-applets/ mate-geyes- applet debian/ mate-applets/ usr/lib/ mate-applets/ mate-multiload- applet debian/ mate-applets/ usr/lib/ mate-applets/ mate-netspeed- applet debian/ mate-applets/ usr/lib/ mate-applets/ mateweather- applet debian/ mate-applets/ usr/lib/ mate-applets/ battstat- applet debian/ mate-applets/ usr/lib/ mate-applets/ mate-cpufreq- applet debian/ mate-applets/ usr/lib/ mate-applets/ stickynotes- applet debian/ mate-applets/ usr/bin/ mate-cpufreq- selector returned exit code 255
dpkg-shlibdeps: error: no dependency information found for /usr/lib/
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/
dh_shlibdeps: Aborting due to earlier error
debian/rules:10: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
-------------------
I've checked the contents of libcpupower1 and libcpupower-dev. Something's not right... Usually there's one real library and two symlinks to it, but here it's not so:
$ ls -l /usr/lib/ libcpupower. so* libcpupower. so libcpupower. so.1 -> libcpupower. so.4.13. 0-32 libcpupower. so.4.13. 0-32
-rw-r--r-- 1 root root 79416 фев 4 21:36 /usr/lib/
lrwxrwxrwx 1 root root 24 фев 4 21:36 /usr/lib/
-rw-r--r-- 1 root root 22760 фев 4 21:36 /usr/lib/
For reference, in Debian Stretch I have this:
$ ls -l /usr/lib/ libcpupower. so* libcpupower. so -> libcpupower. so.0.0. 1 libcpupower. so.0.0. 1 libcpupower. so.1 -> libcpupower. so.0.0. 1
lrwxrwxrwx 1 root root 20 янв 4 14:12 /usr/lib/
-rw-r--r-- 1 root root 22824 янв 4 14:12 /usr/lib/
lrwxrwxrwx 1 root root 20 янв 4 14:12 /usr/lib/
I don't know, is it a problem in the patch, or something's with my kernel build?