From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10051] New: make: *** No rule to make target 'raspberrpi3_defconfig'. Stop reported with Buildroot v 2o17.05.1
Date: Wed, 12 Jul 2017 16:27:51 +0000 [thread overview]
Message-ID: <bug-10051-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10051
Bug ID: 10051
Summary: make: *** No rule to make target
'raspberrpi3_defconfig'. Stop reported with Buildroot
v 2o17.05.1
Product: buildroot
Version: 2017.05.1
Hardware: All
OS: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ptomov at mirion.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7106
--> https://bugs.busybox.net/attachment.cgi?id=7106&action=edit
Screenshot of the error
Hi,
I cloned the Buildroot to version 2017.05.1. with:
git clone https://git.buildroot.net/buildroot
But now when running
make rasberrypi3_defconfig
Buildroot does not create a .config file in /../../buildroot/ folder. The
following error was reported:
make: *** No rule to make target 'raspberrpi3_defconfig'. Stop.
In did not change any configuration. The Make file is the original one. Please
see the attached screenshot and advise me how to fix this problem.
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:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 16:27 bugzilla at busybox.net [this message]
2017-07-12 16:29 ` [Buildroot] [Bug 10051] make: *** No rule to make target 'raspberrpi3_defconfig'. Stop reported with Buildroot v 2o17.05.1 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-10051-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.