From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10056] No .config file was produced in /buildroot folder
Date: Thu, 13 Jul 2017 07:41:22 +0000 [thread overview]
Message-ID: <bug-10056-163-RnOPGZ9lmO@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10056-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10056
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
First of all, please *stop* filing bugs for things that are not bugs but user
issues.
> no .config file was produces in /buildroot folder
> despite the message. Please see the screenshot and
> advise me how to solve this problem. Did something
> change in where Buildroot produces this .config file.
A .config file was definitely produced, I believe you haven't looked properly.
Also, please don't attach screenshots, but copy/paste the text.
> in order to enable "SUDO" command in the image, I have to
> add BR2_PACKAGE_SUDO=y into this .config file.
Not, the .config file should not be edited manually. You should run "make
menuconfig" and adjust the configuration.
Please read the Buildroot manual and training slides.
Also, your next bug reports that are not bugs but user issues will be
immediately closed as INVALID, without any explanation.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-07-13 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 16:52 [Buildroot] [Bug 10056] New: No .config file was produced in /buildroot folder bugzilla at busybox.net
2017-07-12 19:07 ` [Buildroot] [Bug 10056] " bugzilla at busybox.net
2017-07-13 7:41 ` 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-10056-163-RnOPGZ9lmO@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