From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10126] Cannot run bash from Buildroot 2017.08-git image prompt
Date: Sun, 14 Jan 2018 13:43:40 +0000 [thread overview]
Message-ID: <bug-10126-163-rrJPYYR4uZ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10126-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10126
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
How this is a bug ?
If Bash is not built as part of your Buildroot system, then you don't have
bash. Enable bash in your Buildroot configuration and rebuild.
The os-release file is generated by the main Buildroot Makefile. You can tweak
the os-release file in a post-build script.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-01-14 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10126-163@https.bugs.busybox.net/>
2018-01-14 7:37 ` [Buildroot] [Bug 10126] Cannot run bash from Buildroot 2017.08-git image prompt bugzilla at busybox.net
2018-01-14 13:43 ` bugzilla at busybox.net [this message]
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-10126-163-rrJPYYR4uZ@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