From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8541] fail to build host-fakeroot-1.20.2
Date: Mon, 04 Jan 2016 21:41:57 +0000 [thread overview]
Message-ID: <bug-8541-163-uGfRe2Keua@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8541-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8541
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Peter Korsgaard <jacmet@uclibc.org> ---
Fixed in git by:
commit 6fc5de4ef466b649b37a86e4f4994a667149dd80
Author: Ricardo Martincoski <ricardo.martincoski@gmail.com>
Date: Mon Jan 4 16:33:56 2016 -0200
fakeroot: fix build when libcap-dev is installed
Fixes https://bugs.busybox.net/show_bug.cgi?id=8541
Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-01-04 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 16:03 [Buildroot] [Bug 8541] New: fail to build host-fakeroot-1.20.2 bugzilla at busybox.net
2015-12-18 16:09 ` [Buildroot] [Bug 8541] " bugzilla at busybox.net
2015-12-18 16:49 ` bugzilla at busybox.net
2015-12-18 17:19 ` bugzilla at busybox.net
2016-01-04 12:04 ` bugzilla at busybox.net
2016-01-04 18:43 ` bugzilla at busybox.net
2016-01-04 21:41 ` bugzilla at busybox.net [this message]
2020-04-03 14:55 ` bugzilla at busybox.net
2020-04-05 8:02 ` bugzilla at busybox.net
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-8541-163-uGfRe2Keua@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.