New: getfattr 2.4.48 issue
https://bugs.busybox.net/show_bug.cgi?id=11916
Bug ID: 11916
Summary: getfattr 2.4.48 issue
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
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
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 11916] getfattr 2.4.48 issue
https://bugs.busybox.net/show_bug.cgi?id=11916
--- Comment #1 from Jean-pierre Cartal <[email protected]> --- Created attachment 8061
--> https://bugs.busybox.net/attachment.cgi?id=8061&action=edit
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.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 11916] getfattr 2.4.48 issue
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=11916
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
CC| |[email protected]
Status|NEW |RESOLVED--- Comment #2 from Yann E. MORIN <[email protected]> --- 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!
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot