From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8546] New: build instructions for raspberry pi don't work
Date: Tue, 22 Dec 2015 23:29:22 +0000 [thread overview]
Message-ID: <bug-8546-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8546
Bug ID: 8546
Summary: build instructions for raspberry pi don't work
Product: buildroot
Version: 2015.11
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: craigswank at gmail.com
CC: buildroot at uclibc.org
When trying to build for raspberry pi, I follow the instructions from
"board/raspberrypi/readme.txt":
$ make raspberrypi_defconfig
$ make linux/linux.mk:409: *** No kernel defconfig name specified, check your
BR2_LINUX_KERNEL_DEFCONFIG setting. Stop.
Makefile:36: recipe for target '_all' failed
make: *** [_all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-12-22 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 23:29 bugzilla at busybox.net [this message]
2015-12-22 23:30 ` [Buildroot] [Bug 8546] build instructions for raspberry pi don't work bugzilla at busybox.net
2015-12-23 8:21 ` bugzilla at busybox.net
2015-12-23 8:54 ` 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-8546-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.