From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13296] host-libcap failed to build
Date: Fri, 06 Nov 2020 07:28:10 +0000 [thread overview]
Message-ID: <bug-13296-163-Do0tpDkPbc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13296-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13296
--- Comment #7 from Dr I J Ormshaw <ian_ormshaw@waters.com> ---
I am still seeing the same error, with either version of the patch after doing
the following:
1) Deleting my build directory.
2) Checking out the source from tag 2020.11-rc1
3) In the where the source is checked out applying the patch with:
patch -p1 -i <path to
patch>/0001-package-libcap-fix-building-on-host-package.patch
4) Copying my config file to the build directoty
5) Building buildroot
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-06 7:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 9:10 [Buildroot] [Bug 13296] New: host-libcap failed to build bugzilla at busybox.net
2020-11-05 12:10 ` [Buildroot] [Bug 13296] " bugzilla at busybox.net
2020-11-05 16:22 ` bugzilla at busybox.net
2020-11-05 16:22 ` bugzilla at busybox.net
2020-11-05 16:35 ` bugzilla at busybox.net
2020-11-05 19:03 ` bugzilla at busybox.net
2020-11-05 19:05 ` bugzilla at busybox.net
2020-11-05 19:06 ` bugzilla at busybox.net
2020-11-06 7:28 ` bugzilla at busybox.net [this message]
2020-11-06 7:31 ` bugzilla at busybox.net
2020-11-06 7:38 ` bugzilla at busybox.net
2020-11-09 22:13 ` bugzilla at busybox.net
2020-11-10 9:33 ` bugzilla at busybox.net
2020-11-10 11:21 ` bugzilla at busybox.net
2020-11-10 15:01 ` bugzilla at busybox.net
2020-11-11 12:00 ` bugzilla at busybox.net
2020-11-11 12:05 ` bugzilla at busybox.net
2020-11-15 15:48 ` 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-13296-163-Do0tpDkPbc@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