From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10056] New: No .config file was produced in /buildroot folder
Date: Wed, 12 Jul 2017 16:52:43 +0000 [thread overview]
Message-ID: <bug-10056-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10056
Bug ID: 10056
Summary: No .config file was produced in /buildroot folder
Product: buildroot
Version: 2017.05.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ptomov at mirion.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hi,
When running:
make raspberrypi3_defconfig
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.
According to your answer to my previous ticket10011,
in order to enable "SUDO" command in the image, I have to
add BR2_PACKAGE_SUDO=y into this .config file.
Thanks,
Pavel
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-07-12 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 16:52 bugzilla at busybox.net [this message]
2017-07-12 19:07 ` [Buildroot] [Bug 10056] No .config file was produced in /buildroot folder bugzilla at busybox.net
2017-07-13 7:41 ` 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-10056-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