From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10051] make: *** No rule to make target 'raspberrpi3_defconfig'. Stop reported with Buildroot v 2o17.05.1
Date: Wed, 12 Jul 2017 16:29:54 +0000 [thread overview]
Message-ID: <bug-10051-163-LuUf8s3qbw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10051-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10051
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Did you notice the typos in the defconfig you used?
Please look at "make list-defconfigs" or "ls configs/" and use defconfig names
that actually exist.
Also, please double check what you're doing before reporting issues in the bug
tracker. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-07-12 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 16:27 [Buildroot] [Bug 10051] New: make: *** No rule to make target 'raspberrpi3_defconfig'. Stop reported with Buildroot v 2o17.05.1 bugzilla at busybox.net
2017-07-12 16:29 ` 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-10051-163-LuUf8s3qbw@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