Trying to compile devicekit-power-014 on kernel 2.6.32 fails
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to compile devicekit-power-014 on kernel 2.6.33 fails
I'm trying to compile a newer version of devicekit-power (currently I have 009) so maybe I can suspend/hibernate my laptop again, after I updated the kernel.
I installed every package "./configure" asked, so it made a Makefile. When I use "make", it builds a few files, then I get this error:
Code:
devkit_power_daemon-dkp-device.o: In function `dkp_device_coldplug':
dkp-device.c:(.text+0x1e7d): undefined reference to `dkp_device_type_to_text'
devkit_power_daemon-dkp-qos.o: In function `dkp_qos_get_latency_requests':
dkp-qos.c:(.text+0x135): undefined reference to `dkp_qos_type_to_text'
devkit_power_daemon-dkp-qos.o: In function `dkp_qos_get_latency':
dkp-qos.c:(.text+0x2b6): undefined reference to `dkp_qos_type_from_text'
devkit_power_daemon-dkp-qos.o: In function `dkp_qos_latency_perhaps_changed':
dkp-qos.c:(.text+0x3a2): undefined reference to `dkp_qos_type_to_text'
devkit_power_daemon-dkp-qos.o: In function `dkp_qos_set_minimum_latency':
dkp-qos.c:(.text+0x45f): undefined reference to `dkp_qos_type_from_text'
devkit_power_daemon-dkp-qos.o: In function `dkp_qos_request_latency':
dkp-qos.c:(.text+0x6e1): undefined reference to `dkp_qos_type_from_text'
devkit_power_daemon-dkp-wakeups.o: In function `dkp_wakeups_data_get_or_create':
dkp-wakeups.c:(.text+0x683): undefined reference to `dkp_wakeups_obj_new'
devkit_power_daemon-dkp-wakeups.o: In function `dkp_wakeups_init':
dkp-wakeups.c:(.text+0x1449): undefined reference to `dkp_wakeups_obj_free'
devkit_power_daemon-dkp-history.o: In function `dkp_history_array_to_file':
dkp-history.c:(.text+0xd0): undefined reference to `dkp_history_obj_to_string'
devkit_power_daemon-dkp-history.o: In function `dkp_history_array_copy_cb':
dkp-history.c:(.text+0x3ee): undefined reference to `dkp_history_obj_copy'
devkit_power_daemon-dkp-history.o: In function `dkp_history_array_from_file':
dkp-history.c:(.text+0x4cb): undefined reference to `dkp_history_obj_from_string'
devkit_power_daemon-dkp-history.o: In function `dkp_history_set_time_empty_data':
dkp-history.c:(.text+0x6e2): undefined reference to `dkp_history_obj_create'
devkit_power_daemon-dkp-history.o: In function `dkp_history_set_time_full_data':
dkp-history.c:(.text+0x7b2): undefined reference to `dkp_history_obj_create'
devkit_power_daemon-dkp-history.o: In function `dkp_history_set_rate_data':
dkp-history.c:(.text+0x876): undefined reference to `dkp_history_obj_create'
devkit_power_daemon-dkp-history.o: In function `dkp_history_set_charge_data':
dkp-history.c:(.text+0x92e): undefined reference to `dkp_history_obj_create'
devkit_power_daemon-dkp-history.o: In function `dkp_history_set_id':
dkp-history.c:(.text+0xb15): undefined reference to `dkp_history_obj_create'
dkp-history.c:(.text+0xb1f): undefined reference to `dkp_history_obj_copy'
dkp-history.c:(.text+0xb39): undefined reference to `dkp_history_obj_copy'
dkp-history.c:(.text+0xb53): undefined reference to `dkp_history_obj_copy'
dkp-history.c:(.text+0xb6d): undefined reference to `dkp_history_obj_copy'
dkp-history.c:(.text+0xb87): undefined reference to `dkp_history_obj_free'
devkit_power_daemon-dkp-history.o: In function `dkp_history_get_profile_data':
dkp-history.c:(.text+0xc0d): undefined reference to `dkp_stats_obj_create'
devkit_power_daemon-dkp-history.o: In function `dkp_history_get_data':
dkp-history.c:(.text+0xf56): undefined reference to `dkp_history_obj_copy'
dkp-history.c:(.text+0xfb9): undefined reference to `dkp_history_obj_free'
dkp-history.c:(.text+0x10ff): undefined reference to `dkp_history_obj_new'
dkp-history.c:(.text+0x11c3): undefined reference to `dkp_history_obj_new'
devkit_power_daemon-dkp-history.o: In function `dkp_history_init':
dkp-history.c:(.text+0x141a): undefined reference to `dkp_history_obj_free'
dkp-history.c:(.text+0x142c): undefined reference to `dkp_history_obj_free'
dkp-history.c:(.text+0x143e): undefined reference to `dkp_history_obj_free'
dkp-history.c:(.text+0x1450): undefined reference to `dkp_history_obj_free'
dummy/.libs/libdkpshared.a(dkp-backend.o): In function `dkp_backend_test':
dkp-backend.c:(.text+0x26d): undefined reference to `egg_test_start'
dkp-backend.c:(.text+0x283): undefined reference to `egg_test_title'
dkp-backend.c:(.text+0x29d): undefined reference to `egg_test_assert'
dkp-backend.c:(.text+0x2ad): undefined reference to `egg_test_end'
dummy/.libs/libdkpshared.a(dkp-native.o): In function `dkp_native_test':
dkp-native.c:(.text+0x3a): undefined reference to `egg_test_start'
dkp-native.c:(.text+0x50): undefined reference to `egg_test_title'
dkp-native.c:(.text+0x82): undefined reference to `egg_test_assert'
dkp-native.c:(.text+0x8a): undefined reference to `egg_test_end'
collect2: ld returned 1 exit status
What could be missing? Is this a bug?
Also, is upower-0.90/91 the same thing but newer?
Last edited by Geriao; 04-13-2010 at 07:49 AM.
Reason: Kernel 2.6.33 actually
I have recompiled a new version of pm-utils before it. I think I also had to compile eggdbus before (it was absent on my system). I'll try to recompile eggdbus again anyway...
Does anyone know where those functions gcc misses are from?
Well, I alredy have updated eggdbus with version 0.6, I did it again, but devicekit-power-014 doesn't compile... Same error... The version of pm-util I have now is 1.3.0.
I am a programmer by hobby and it looks as if this is a linker error. You apparently have the headers installed, but apparently the libs are not installed or are not the correct version hence the missing function references.
Sorry I can't help more but maybe it will point you in the right direction. I would look at whatever libraries these are referring to and check the required versions. Could be a case where the configure script isn't checking for the right version.
It could even be a bad makefile that isn't linking the libs in, it's hard to tell. This seems unlikely though unless the package isn't very mature.
I am a programmer by hobby and it looks as if this is a linker error. You apparently have the headers installed, but apparently the libs are not installed or are not the correct version hence the missing function references.
Sorry I can't help more but maybe it will point you in the right direction. I would look at whatever libraries these are referring to and check the required versions. Could be a case where the configure script isn't checking for the right version.
It could even be a bad makefile that isn't linking the libs in, it's hard to tell. This seems unlikely though unless the package isn't very mature.
The problem is: what are those libraries it's trying to link to, and what package contains them?
SRC RPMS are usually very informative : DeviceKit-power.spec ..
%define dbus_version 0.90
%define dbus_glib_version 0.70
1) They seem to use dbus_glib ,,, may have been fixed
..... to be as usable as eggdbus. ?
2) If dbus_glib, eggdbus use coincident versioning, eggdbus should be ' 0.7 '
.....
I'll try and install dbus0glib 0.86, which is latest I found... Anyway, I have 0.80 installed, shouldn't be a problem. The latest eggdbus is 0.6 which is installed. It seems that there's no 0.7 yet...
I hope it's not too late to resurrect this, but was there a solution to this problem? The latest DeviceKit-power is still 0.14, and it won't build with this exact problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.