From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9416] Running on 2016.11-rc1 second make fails "makedevs: line 23: Couldnt create node /buildroot-2016.11-rc1/output/target/dev/console: File exists"
Date: Thu, 01 Dec 2016 14:23:02 +0000 [thread overview]
Message-ID: <bug-9416-163-z9DU67oAHc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9416-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9416
Andy Shevchenko <andy.shevchenko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #2 from Andy Shevchenko <andy.shevchenko@gmail.com> ---
Have another message, what did I miss?
makedevs: line 24: node ...output/target/dev/console exists but is of wrong
file type
fs/cpio/cpio.mk:42: recipe for target '...output/images/rootfs.cpio' failed
93106e9 Update for 2016.11-rc3
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-01 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 9:10 [Buildroot] [Bug 9416] New: Running on 2016.11-rc1 second make fails "makedevs: line 23: Couldnt create node /buildroot-2016.11-rc1/output/target/dev/console: File exists" bugzilla at busybox.net
2016-11-10 9:14 ` [Buildroot] [Bug 9416] " bugzilla at busybox.net
2016-12-01 14:23 ` bugzilla at busybox.net [this message]
2016-12-01 18:02 ` bugzilla at busybox.net
2016-12-02 9:16 ` bugzilla at busybox.net
2016-12-02 10:04 ` bugzilla at busybox.net
2016-12-07 15:06 ` 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-9416-163-z9DU67oAHc@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