Summary: | sys-fs/udisks-1.0.2 - libatasmart.so: undefined reference to `udev_device_get_property_value' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Coben <jcoben> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | udisks-1.0.2 build log |
Description
John Coben
2011-04-07 07:05:30 UTC
Created attachment 268815 [details]
udisks-1.0.2 build log
Either your udev is to old or there's something more broken on your system. Which version of sys-fs/udev do you have? I have udev-151r4. I tried doing 'ACCEPT_KEYWORDS="~x86" emerge udev' but there was no change with that version. udev_device_get_property_value should already be present in udev 154. Check libudev for the presence of that symbol and check with ldd if libatasmart properly links to libudev. (In reply to comment #5) > udev_device_get_property_value should already be present in udev 154. > Check libudev for the presence of that symbol and check with ldd if libatasmart > properly links to libudev. /usr/lib # ldd libatasmart.so linux-gate.so.1 => (0xb778e000) libudev.so.0 => /usr/local/lib/libudev.so.0 (0xb7753000) libc.so.6 => /lib/libc.so.6 (0xb760d000) /lib/ld-linux.so.2 (0xb778f000) /usr/lib # nm --dynamic libudev.so.0 ... 00005430 T udev_device_get_property_value ... 00006490 T udev_device_get_parent_with_subsystem_devtype ... If I understood you this all looks right. I noticed I had no /usr/local/lib/libudev.so.0. I copied it over and udisks compiles. Thanks! You should *not* have a /usr/local/lib/libudev.so.0. Actually, you should not have /usr/local/lib/<anything> of anything that's in portage and adding /usr/local/lib/<anything> just breaks your system more. (In reply to comment #8) > You should *not* have a /usr/local/lib/libudev.so.0. > Actually, you should not have /usr/local/lib/<anything> of anything that's in > portage and adding /usr/local/lib/<anything> just breaks your system more. Well, I'm open to suggestions of how to fix it. What kind of stuff do you have in /usr/local/include and /usr/local/lib? I think the obvious way: check /usr/local/{bin,lib} (perhaps a dir or two more) for anything provided by portage tree, remove that stuff, then run revdep-rebuild. (In reply to comment #10) > What kind of stuff do you have in /usr/local/include and /usr/local/lib? /usr/local/lib $ ls dri libdrm.so libhpip.so.0.0.1 libntfs-3g.a libvolume_id.so.1 udev findcruft libdrm.so.2 libhpmud.la libntfs-3g.la libvolume_id.so.1.0.6 wine libdrm_intel.la libdrm.so.2.3.0 libhpmud.so libntfs-3g.so libwine.so libdrm_intel.so libdrm.so.2.3.1 libhpmud.so.0 libudev.so libwine.so.1 libdrm_intel.so.1 libhpip.la libhpmud.so.0.0.6 libudev.so.0 libwine.so.1.0 libdrm_intel.so.1.0.0 libhpip.so libiw.so libudev.so.0.0.6 pkgconfig libdrm.la libhpip.so.0 libiw.so.29 libvolume_id.so python2.6 /usr/local/include $ ls drm intel_bufmgr.h iwlib.h libudev.h~ libvolume_id.h ntfs-3g wine wireless.h xf86drm.h None of that junk looked important so I gave it all the axe, ran revdep-rebuild and just to be safe did 'emerge udev libatasmart udisks' then etc-update. Everything went smoothly and /usr/local is still empty so I think I've fixed it. I have no idea how udev got in there. Now I know it shouldn't be, and knowing is half the battle. Ok to close this bug as fixed then? |