From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9456] mkusers script bash errors
Date: Tue, 29 Nov 2016 12:13:53 +0000 [thread overview]
Message-ID: <bug-9456-163-7dHYDANV9W@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9456-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9456
--- Comment #2 from George Y. <georgebrmz@oss3d.com> ---
Created attachment 6811
--> https://bugs.busybox.net/attachment.cgi?id=6811&action=edit
Buildroot config
The config is attached. Nothing specifically different.
By the way, the build process does not stop. It continues and ignores those
errors, so if it happens for you as well, you'll only see it from the messages,
but the building will continue and will give an impression of success.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-11-29 12:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 22:49 [Buildroot] [Bug 9456] New: mkusers script bash errors bugzilla at busybox.net
2016-11-29 7:27 ` [Buildroot] [Bug 9456] " bugzilla at busybox.net
2016-11-29 12:13 ` bugzilla at busybox.net [this message]
2016-11-29 21:46 ` bugzilla at busybox.net
2016-11-30 22:54 ` bugzilla at busybox.net
2017-02-13 20:44 ` bugzilla at busybox.net
2017-02-26 20:21 ` bugzilla at busybox.net
2017-02-26 22:51 ` bugzilla at busybox.net
2017-02-28 19:18 ` bugzilla at busybox.net
2017-02-28 21:04 ` bugzilla at busybox.net
2017-02-28 21:15 ` bugzilla at busybox.net
2017-02-28 21:57 ` bugzilla at busybox.net
2017-02-28 22:10 ` bugzilla at busybox.net
2017-02-28 23:23 ` bugzilla at busybox.net
2017-03-01 7:46 ` bugzilla at busybox.net
2017-03-01 16:19 ` bugzilla at busybox.net
2017-03-01 16:38 ` bugzilla at busybox.net
2017-03-01 17:30 ` bugzilla at busybox.net
2017-03-01 17:46 ` bugzilla at busybox.net
2017-03-01 22:41 ` bugzilla at busybox.net
2017-03-02 0:09 ` bugzilla at busybox.net
2017-03-02 17:28 ` bugzilla at busybox.net
2017-03-02 23:17 ` bugzilla at busybox.net
2017-03-03 15:26 ` bugzilla at busybox.net
2017-03-03 17:31 ` bugzilla at busybox.net
2017-03-03 17:37 ` bugzilla at busybox.net
2017-03-03 21:50 ` bugzilla at busybox.net
2017-03-03 21:57 ` bugzilla at busybox.net
2017-03-03 22:10 ` bugzilla at busybox.net
2017-03-03 23:06 ` bugzilla at busybox.net
2017-03-04 10:05 ` bugzilla at busybox.net
2017-03-04 10:58 ` 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-9456-163-7dHYDANV9W@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