Bug 11829

Summary:	image including multilib:lib64 python3-dev package does not reach login
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component:	core	Assignee:	Alejandro Hernandez <alejandro.hernandez>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	meta.mr.watcher, meta.watcher, randy.macleod
Version:	2.4
Target Milestone:	2.4 M4
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Leonardo Sandoval Gonzalez 2017-07-24 16:19:46 UTC

* clone poky and prepare environment
* touch and include the following text into conf/auto.conf

IMAGE_INSTALL_append = "lib64-python3-dev"
require conf/multilib.conf
MULTILIBS = "multilib:lib64"
DEFAULTTUNE_virtclass-multilib-lib64 = "x86-64"

* create a core-image-minimal image with bitbake
* boot it with runqemu
* expected: login prompt should be reached
* actual:

[    6.732574] Write protecting the kernel read-only data: 2524k
INIT: version 2.88 booting
INIT: cannot execute "/bin/sh"
INIT: Entering runlevel: 5
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: cannot execute "/bin/sh"
INIT: Id "S1" respawning too fast: disabled for 5 minutes
INIT: cannot execute "/bin/sh"
INIT: Id "S0" respawning too fast: disabled for 5 minutes

Comment 1 Leonardo Sandoval Gonzalez 2017-08-29 17:27:58 UTC

(In reply to comment #0)
> * clone poky and prepare environment
> * touch and include the following text into conf/auto.conf
> 
> IMAGE_INSTALL_append = "lib64-python3-dev"

minor typo, it should be

IMAGE_INSTALL_append = " lib64-python3-dev"

(note the space after quote)


> require conf/multilib.conf
> MULTILIBS = "multilib:lib64"
> DEFAULTTUNE_virtclass-multilib-lib64 = "x86-64"
> 
> * create a core-image-minimal image with bitbake
> * boot it with runqemu
> * expected: login prompt should be reached
> * actual:
> 
> [    6.732574] Write protecting the kernel read-only data: 2524k
> INIT: version 2.88 booting
> INIT: cannot execute "/bin/sh"
> INIT: Entering runlevel: 5
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: cannot execute "/bin/sh"
> INIT: Id "S1" respawning too fast: disabled for 5 minutes
> INIT: cannot execute "/bin/sh"
> INIT: Id "S0" respawning too fast: disabled for 5 minutes

Comment 2 Alejandro Hernandez 2017-08-29 19:01:02 UTC

I believe this might be a config error, since for what I can see, you are trying to run 64 bit libraries on a 32 bit machine (qemux86), the other way around would be ok though.

Comment 3 Leonardo Sandoval Gonzalez 2017-08-29 19:41:29 UTC

(In reply to comment #2)
> I believe this might be a config error, since for what I can see, you are
> trying to run 64 bit libraries on a 32 bit machine (qemux86), the other way
> around would be ok though.

My bad (sorry for wasting your time), I though I was testing with a 64bit machine, but it was not the case, it was a 32bit, so init cannot be executed due to this reason.