On 12/09/2013 06:31 PM, ChenQi wrote:
On 12/09/2013 07:52 PM, Otavio Salvador wrote:
Hello,

I agree with the commit but ...

On Mon, Dec 9, 2013 at 1:17 AM,  <qi.c...@windriver.com> wrote:
From: Chen Qi <qi.c...@windriver.com>

Default USE_DEVFS to "1" so that the `makedevs' command is not run
at rootfs time by default. There are mainly two reasons to do so.
1. This will fix a build failure with initramfs-kexecboot-klibc-image.
Can you elaborate this error? is it something we can/should fix?

It's "makedevs: No entry for root in search list ", just as Andrea said.
I've updated the commit message in remote tree.
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=ChenQi/USE_DEVFS&id=435b6e6e34c4c65022e57b78a246cfd8fcd2d71f

Please resend as a V2

Sau!


Thanks,
Chen Qi

2. Most of our images use a filesystem over /dev. Most of the time, it's
    just devtmpfs. So we actually are using a filesystem over /dev.

Signed-off-by: Chen Qi <qi.c...@windriver.com>
---
  meta/classes/image.bbclass |    2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index cc65e35..b8bd462 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -77,7 +77,7 @@ PACKAGE_INSTALL_ATTEMPTONLY ?=
"${FEATURE_INSTALL_OPTIONAL}"
  # Images are generally built explicitly, do not need to be part of
world.
  EXCLUDE_FROM_WORLD = "1"

-USE_DEVFS ?= "0"
+USE_DEVFS ?= "1"

  PID = "${@os.getpid()}"

--
1.7.9.5

_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core



_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to