From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13216] New: [Documentation] 2020.02.6 requires GNU find utils
Date: Tue, 22 Sep 2020 02:42:04 +0000 [thread overview]
Message-ID: <bug-13216-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13216
Bug ID: 13216
Summary: [Documentation] 2020.02.6 requires GNU find utils
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: waitman at waitman.net
CC: buildroot at uclibc.org
Target Milestone: ---
The documentation states that GNU binutils are required, however binutils does
not include "find". If user has a "find" that is not from GNU find utils
package then the Makefile stops with error.
Documentation should specify that GNU find utils are required.
../buildroot-2020.02.6/output/build/host-e2fsprogs-1.45.6
find: unrecognized: -printf
GNU find utils are available at the following URL:
https://www.gnu.org/software/findutils/
(optionally update Makefile so that GNU find utils are not required)
Additionally there is no "2020.06.2" option (the long term support release) in
the version select box, in the bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-09-22 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 2:42 bugzilla at busybox.net [this message]
2020-09-22 2:43 ` [Buildroot] [Bug 13216] [Documentation] 2020.02.6 requires GNU find utils bugzilla at busybox.net
2020-09-29 18:46 ` bugzilla at busybox.net
2020-09-29 18:49 ` bugzilla at busybox.net
2020-09-29 19:47 ` bugzilla at busybox.net
2020-09-29 22:40 ` bugzilla at busybox.net
2022-09-18 12:58 ` 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-13216-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