From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10786] New: Linux fails to build unless make linux-menuconfig is run first
Date: Tue, 20 Feb 2018 20:01:08 +0000 [thread overview]
Message-ID: <bug-10786-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10786
Bug ID: 10786
Summary: Linux fails to build unless make linux-menuconfig is
run first
Product: buildroot
Version: 2017.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: adyke at harris.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7476
--> https://bugs.busybox.net/attachment.cgi?id=7476&action=edit
defconfig
When selecting BR2_TARGET_ROOTFS_ISO9660 and BR2_TARGET_SYSLINUX_ISOLINUX,
Linux fails to build until "make linux-menuconfig" is run. It would seem that
the kernel is expecting output/images/rootfs.cpio to exist, but it does not
unless linux-menuconfig is run.
Once linux-menuconfig has been run once, the problem disappears until I rm -rf
everything in output/images. Then running linux-menuconfig again solves the
issue.
Obviously the workaround is to run linux-menuconfig, but trying to build in a
freshly checked out copy of our repo always fails.
A branch of our repo that is identical except it does not have
BR2_TARGET_ROOTFS_ISO9660 and BR2_TARGET_SYSLINUX_ISOLINUX set does not see
this issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-02-20 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 20:01 bugzilla at busybox.net [this message]
2018-02-20 20:13 ` [Buildroot] [Bug 10786] Linux fails to build unless make linux-menuconfig is run first bugzilla at busybox.net
2018-02-21 22:56 ` bugzilla at busybox.net
2018-02-25 21:38 ` 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-10786-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.