From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11916] New: getfattr 2.4.48 issue
Date: Mon, 27 May 2019 12:46:52 +0000 [thread overview]
Message-ID: <bug-11916-163@https.bugs.busybox.net/> (raw)
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.
next reply other threads:[~2019-05-27 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 12:46 bugzilla at busybox.net [this message]
2019-05-28 13:12 ` [Buildroot] [Bug 11916] getfattr 2.4.48 issue bugzilla at busybox.net
2024-06-15 14:49 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11916-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox