From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1537] New: dev entries not created anymore
Date: Tue, 13 Apr 2010 16:30:45 +0000 (UTC) [thread overview]
Message-ID: <bug-1537-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1537
Host: Linux i686
Target: Linux ARM and i686
Build: Linux i686
Summary: dev entries not created anymore
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P3
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: luca.ceresoli at tiscali.it
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=1501)
--> (https://bugs.busybox.net/attachment.cgi?id=1501)
default i686 non-cross config to reproduce the bug
After a regular `git pull` I found buildroot is not generating device entries
in output/target/dev/ anymore. The resulting images are then obviously broken.
The visible effect is that fs/common.mk finds TARGET_DEVICE_TABLE empty,
thus is does not call makedevs.
This seems to be happening since commit:
0585241 Move all filesystem generation code to fs/
Verified with Linux-i686 as a development host, two targets:
- Linux ARM, custom config,
- Linux i686, default config (make menuconfig, exit, save; it's attached
anyway),
on git commit 9554403ad0b81f29dd4ee1404de755aa5b72cac5.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-04-13 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 16:30 bugzilla at busybox.net [this message]
2010-04-17 0:52 ` [Buildroot] [Bug 1537] dev entries not created anymore bugzilla at busybox.net
2010-04-18 20:35 ` 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-1537-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.