Bug 11916 - getfattr 2.4.48 issue
Summary: getfattr 2.4.48 issue
Status: RESOLVED MOVED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2019.02.2
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-27 12:46 UTC by Jean-pierre Cartal
Modified: 2024-06-15 14:49 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:


Attachments
Patch to avoid symbol version lookup issue (539 bytes, patch)
2019-05-28 13:12 UTC, Jean-pierre Cartal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-pierre Cartal 2019-05-27 12:46:52 UTC
Hello,

It seems that since attr was updated to v2.4.48, the getfattr command is not working properly anymore.

The following tests were done with BR 2018.02.4 (2.4.47), BR 2018.02.5 (2.4.48) and BR 2019.02.2 with getfattr and libattr.so* being copied to /home/guest and the LD_LIBRARY_PATH set accordingly.

BR 2018.02.4 :
#  /home/guest/getfattr --version
getfattr 2.4.47
#  /home/guest/getfattr /bin/ls

BR 2018.02.5/2019.02.2
#  /home/guest/getfattr --version
getfattr 2.4.48
#  /home/guest/getfattr /bin/ls
/home/guest/getfattr: relocation error: /home/guest/getfattr: symbol listxattr, version ATTR_1.0 not defined in file libattr.so.1 with link time reference

Regards
Comment 1 Jean-pierre Cartal 2019-05-28 13:12:44 UTC
Created attachment 8061 [details]
Patch to avoid symbol version lookup issue

This patch solves the issue by not linking setfattr and getfattr with libattr, and thus use the glibc version of the *xattr() functions.

Add the libattr to only attr linking command where it is really needed.
Comment 2 Yann E. MORIN 2024-06-15 14:49:35 UTC
Thank you for your report.

The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
    https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.

Thank you!