* [Buildroot] [Bug 11916] New: getfattr 2.4.48 issue
@ 2019-05-27 12:46 bugzilla at busybox.net
2019-05-28 13:12 ` [Buildroot] [Bug 11916] " bugzilla at busybox.net
2024-06-15 14:49 ` bugzilla
0 siblings, 2 replies; 3+ messages in thread
From: bugzilla at busybox.net @ 2019-05-27 12:46 UTC (permalink / raw)
To: buildroot
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
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Buildroot] [Bug 11916] getfattr 2.4.48 issue 2019-05-27 12:46 [Buildroot] [Bug 11916] New: getfattr 2.4.48 issue bugzilla at busybox.net @ 2019-05-28 13:12 ` bugzilla at busybox.net 2024-06-15 14:49 ` bugzilla 1 sibling, 0 replies; 3+ messages in thread From: bugzilla at busybox.net @ 2019-05-28 13:12 UTC (permalink / raw) To: buildroot https://bugs.busybox.net/show_bug.cgi?id=11916 --- Comment #1 from Jean-pierre Cartal <jpcartal@free.fr> --- 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. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] [Bug 11916] getfattr 2.4.48 issue 2019-05-27 12:46 [Buildroot] [Bug 11916] New: getfattr 2.4.48 issue bugzilla at busybox.net 2019-05-28 13:12 ` [Buildroot] [Bug 11916] " bugzilla at busybox.net @ 2024-06-15 14:49 ` bugzilla 1 sibling, 0 replies; 3+ messages in thread From: bugzilla @ 2024-06-15 14:49 UTC (permalink / raw) To: buildroot https://bugs.busybox.net/show_bug.cgi?id=11916 Yann E. MORIN <yann.morin.1998@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED CC| |yann.morin.1998@free.fr Status|NEW |RESOLVED --- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> --- 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! -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-15 14:49 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-05-27 12:46 [Buildroot] [Bug 11916] New: getfattr 2.4.48 issue bugzilla at busybox.net 2019-05-28 13:12 ` [Buildroot] [Bug 11916] " bugzilla at busybox.net 2024-06-15 14:49 ` bugzilla
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox