[PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

[PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

[changqing.li]

From: Changqing Li <changqing.li@windriver.com>

Configrations:
MACHINE: qemux86-64
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

Reproduce steps:
bitbake lib32-core-image-minimal
runqemu qemux86-64 nographic lib32-core-image-minimal

Errors:
qemu cannot bootup since:
Booting from ROM...
This kernel requires an x86-64 CPU, but only detected an i686 CPU.
Unable to boot - please use a kernel appropriate for your CPU.
QEMU: Terminated

For lib32 image, override has x86, so the qemubin set to qemu-system-i386,
fix by move qemuboot parameters to corresponding conf, don't use the override

Signed-off-by: Changqing Li <changqing.li@windriver.com>
---
 meta-yocto-bsp/conf/machine/genericx86-64.conf         | 16 ++++++++++++++++
 meta-yocto-bsp/conf/machine/genericx86.conf            | 16 ++++++++++++++++
 .../conf/machine/include/genericx86-common.inc         |  1 -
 meta/conf/machine/include/qemuboot-x86.inc             | 18 ------------------
 meta/conf/machine/qemux86-64.conf                      | 17 ++++++++++++++++-
 meta/conf/machine/qemux86.conf                         | 17 ++++++++++++++++-
 6 files changed, 64 insertions(+), 21 deletions(-)
 delete mode 100644 meta/conf/machine/include/qemuboot-x86.inc

diff --git a/meta-yocto-bsp/conf/machine/genericx86-64.conf b/meta-yocto-bsp/conf/machine/genericx86-64.conf
index c489462..bf85af0 100644
--- a/meta-yocto-bsp/conf/machine/genericx86-64.conf
+++ b/meta-yocto-bsp/conf/machine/genericx86-64.conf
@@ -7,3 +7,19 @@ require conf/machine/include/tune-core2.inc
 require conf/machine/include/genericx86-common.inc
 
 SERIAL_CONSOLES_CHECK = "ttyS0"
+
+# For runqemu
+IMAGE_CLASSES += "qemuboot"
+
+QB_SYSTEM_NAME = "qemu-system-x86_64"
+QB_CPU = "-cpu core2duo"
+QB_CPU_KVM = "-cpu core2duo"
+
+QB_AUDIO_DRV = "alsa"
+QB_AUDIO_OPT = "-soundhw ac97,es1370"
+QB_KERNEL_CMDLINE_APPEND = "vga=0 uvesafb.mode_option=${UVESA_MODE} oprofile.timer=1 uvesafb.task_timeout=-1"
+QB_OPT_APPEND = "-vga vmware -show-cursor -usb -device usb-tablet"
+# Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
+QB_OPT_APPEND += "-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0"
+
+UVESA_MODE ?= "640x480-32"
diff --git a/meta-yocto-bsp/conf/machine/genericx86.conf b/meta-yocto-bsp/conf/machine/genericx86.conf
index 9929d27..d8a573e 100644
--- a/meta-yocto-bsp/conf/machine/genericx86.conf
+++ b/meta-yocto-bsp/conf/machine/genericx86.conf
@@ -7,3 +7,19 @@ require conf/machine/include/tune-core2.inc
 require conf/machine/include/genericx86-common.inc
 
 MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "gma500-gfx-check"
+
+# For runqemu
+IMAGE_CLASSES += "qemuboot"
+
+QB_SYSTEM_NAME = "qemu-system-i386"
+QB_CPU = "-cpu core2duo"
+QB_CPU_KVM = "-cpu core2duo"
+
+QB_AUDIO_DRV = "alsa"
+QB_AUDIO_OPT = "-soundhw ac97,es1370"
+QB_KERNEL_CMDLINE_APPEND = "vga=0 uvesafb.mode_option=${UVESA_MODE} oprofile.timer=1 uvesafb.task_timeout=-1"
+QB_OPT_APPEND = "-vga vmware -show-cursor -usb -device usb-tablet"
+# Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
+QB_OPT_APPEND += "-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0"
+
+UVESA_MODE ?= "640x480-32"
diff --git a/meta-yocto-bsp/conf/machine/include/genericx86-common.inc b/meta-yocto-bsp/conf/machine/include/genericx86-common.inc
index f83ce5c..75db054 100644
--- a/meta-yocto-bsp/conf/machine/include/genericx86-common.inc
+++ b/meta-yocto-bsp/conf/machine/include/genericx86-common.inc
@@ -1,5 +1,4 @@
 include conf/machine/include/x86-base.inc
-require conf/machine/include/qemuboot-x86.inc
 MACHINE_FEATURES += "wifi efi pcbios"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
diff --git a/meta/conf/machine/include/qemuboot-x86.inc b/meta/conf/machine/include/qemuboot-x86.inc
deleted file mode 100644
index 82ce46d..0000000
--- a/meta/conf/machine/include/qemuboot-x86.inc
+++ /dev/null
@@ -1,18 +0,0 @@
-# For runqemu
-IMAGE_CLASSES += "qemuboot"
-QB_SYSTEM_NAME_x86 = "qemu-system-i386"
-QB_CPU_x86 = "-cpu core2duo"
-QB_CPU_KVM_x86 = "-cpu core2duo"
-
-QB_SYSTEM_NAME_x86-64 = "qemu-system-x86_64"
-QB_CPU_x86-64 = "-cpu core2duo"
-QB_CPU_KVM_x86-64 = "-cpu core2duo"
-
-QB_AUDIO_DRV = "alsa"
-QB_AUDIO_OPT = "-soundhw ac97,es1370"
-QB_KERNEL_CMDLINE_APPEND = "vga=0 uvesafb.mode_option=${UVESA_MODE} oprofile.timer=1 uvesafb.task_timeout=-1"
-QB_OPT_APPEND = "-vga vmware -show-cursor -usb -device usb-tablet"
-# Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
-QB_OPT_APPEND += "-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0"
-
-UVESA_MODE ?= "640x480-32"
diff --git a/meta/conf/machine/qemux86-64.conf b/meta/conf/machine/qemux86-64.conf
index 383e3bd..c39f72d 100644
--- a/meta/conf/machine/qemux86-64.conf
+++ b/meta/conf/machine/qemux86-64.conf
@@ -10,7 +10,6 @@ PREFERRED_PROVIDER_virtual/libgles2 ?= "mesa"
 require conf/machine/include/qemu.inc
 DEFAULTTUNE ?= "core2-64"
 require conf/machine/include/tune-core2.inc
-require conf/machine/include/qemuboot-x86.inc
 
 UBOOT_MACHINE ?= "qemu-x86_64_defconfig"
 
@@ -39,3 +38,19 @@ module_conf_uvesafb = "options uvesafb mode_option=${UVESA_MODE}"
 
 WKS_FILE ?= "qemux86-directdisk.wks"
 do_image_wic[depends] += "syslinux:do_populate_sysroot syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot"
+
+# For runqemu
+IMAGE_CLASSES += "qemuboot"
+
+QB_SYSTEM_NAME = "qemu-system-x86_64"
+QB_CPU = "-cpu core2duo"
+QB_CPU_KVM = "-cpu core2duo"
+
+QB_AUDIO_DRV = "alsa"
+QB_AUDIO_OPT = "-soundhw ac97,es1370"
+QB_KERNEL_CMDLINE_APPEND = "vga=0 uvesafb.mode_option=${UVESA_MODE} oprofile.timer=1 uvesafb.task_timeout=-1"
+QB_OPT_APPEND = "-vga vmware -show-cursor -usb -device usb-tablet"
+# Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
+QB_OPT_APPEND += "-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0"
+
+UVESA_MODE ?= "640x480-32"
diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/qemux86.conf
index 272ad1e..cce87b6 100644
--- a/meta/conf/machine/qemux86.conf
+++ b/meta/conf/machine/qemux86.conf
@@ -10,7 +10,6 @@ PREFERRED_PROVIDER_virtual/libgles2 ?= "mesa"
 require conf/machine/include/qemu.inc
 DEFAULTTUNE ?= "core2-32"
 require conf/machine/include/tune-corei7.inc
-require conf/machine/include/qemuboot-x86.inc
 
 UBOOT_MACHINE ?= "qemu-x86_defconfig"
 
@@ -39,3 +38,19 @@ module_conf_uvesafb = "options uvesafb mode_option=${UVESA_MODE}"
 
 WKS_FILE ?= "qemux86-directdisk.wks"
 do_image_wic[depends] += "syslinux:do_populate_sysroot syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot"
+
+# For runqemu
+IMAGE_CLASSES += "qemuboot"
+
+QB_SYSTEM_NAME = "qemu-system-i386"
+QB_CPU = "-cpu core2duo"
+QB_CPU_KVM = "-cpu core2duo"
+
+QB_AUDIO_DRV = "alsa"
+QB_AUDIO_OPT = "-soundhw ac97,es1370"
+QB_KERNEL_CMDLINE_APPEND = "vga=0 uvesafb.mode_option=${UVESA_MODE} oprofile.timer=1 uvesafb.task_timeout=-1"
+QB_OPT_APPEND = "-vga vmware -show-cursor -usb -device usb-tablet"
+# Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
+QB_OPT_APPEND += "-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0"
+
+UVESA_MODE ?= "640x480-32"
-- 
2.7.4

Re: [PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

[Richard Purdie]

On Wed, 2019-07-31 at 11:40 +0800, changqing.li@windriver.com wrote:
> From: Changqing Li <changqing.li@windriver.com>
> 
> Configrations:
> MACHINE: qemux86-64
> require conf/multilib.conf
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
> 
> Reproduce steps:
> bitbake lib32-core-image-minimal
> runqemu qemux86-64 nographic lib32-core-image-minimal
> 
> Errors:
> qemu cannot bootup since:
> Booting from ROM...
> This kernel requires an x86-64 CPU, but only detected an i686 CPU.
> Unable to boot - please use a kernel appropriate for your CPU.
> QEMU: Terminated
> 
> For lib32 image, override has x86, so the qemubin set to qemu-system-
> i386,
> fix by move qemuboot parameters to corresponding conf, don't use the
> override

Why remove/move the whole file when its just QB_SYSTEM_NAME that is the
issue and that alone could be moved?

Cheers,

Richard

Re: [PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

[Changqing Li]

On 7/31/19 5:00 PM, Richard Purdie wrote:
> On Wed, 2019-07-31 at 11:40 +0800, changqing.li@windriver.com wrote:
>> From: Changqing Li <changqing.li@windriver.com>
>>
>> Configrations:
>> MACHINE: qemux86-64
>> require conf/multilib.conf
>> MULTILIBS = "multilib:lib32"
>> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>>
>> Reproduce steps:
>> bitbake lib32-core-image-minimal
>> runqemu qemux86-64 nographic lib32-core-image-minimal
>>
>> Errors:
>> qemu cannot bootup since:
>> Booting from ROM...
>> This kernel requires an x86-64 CPU, but only detected an i686 CPU.
>> Unable to boot - please use a kernel appropriate for your CPU.
>> QEMU: Terminated
>>
>> For lib32 image, override has x86, so the qemubin set to qemu-system-
>> i386,
>> fix by move qemuboot parameters to corresponding conf, don't use the
>> override
> Why remove/move the whole file when its just QB_SYSTEM_NAME that is the
> issue and that alone could be moved?

I think maybe put qemuboot related parameter together in one file is better

than some config is here and some config is there. So I move the whole 
content

>
> Cheers,
>
> Richard
>
>
-- 
BRs

Sandy(Li Changqing)

Re: [PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

[richard.purdie]

On Wed, 2019-07-31 at 17:38 +0800, Changqing Li wrote:
> On 7/31/19 5:00 PM, Richard Purdie wrote:
> > On Wed, 2019-07-31 at 11:40 +0800, changqing.li@windriver.com
> > wrote:
> > > From: Changqing Li <changqing.li@windriver.com>
> > > 
> > > Configrations:
> > > MACHINE: qemux86-64
> > > require conf/multilib.conf
> > > MULTILIBS = "multilib:lib32"
> > > DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
> > > 
> > > Reproduce steps:
> > > bitbake lib32-core-image-minimal
> > > runqemu qemux86-64 nographic lib32-core-image-minimal
> > > 
> > > Errors:
> > > qemu cannot bootup since:
> > > Booting from ROM...
> > > This kernel requires an x86-64 CPU, but only detected an i686
> > > CPU.
> > > Unable to boot - please use a kernel appropriate for your CPU.
> > > QEMU: Terminated
> > > 
> > > For lib32 image, override has x86, so the qemubin set to qemu-
> > > system-
> > > i386,
> > > fix by move qemuboot parameters to corresponding conf, don't use
> > > the
> > > override
> > Why remove/move the whole file when its just QB_SYSTEM_NAME that is
> > the
> > issue and that alone could be moved?
> 
> I think maybe put qemuboot related parameter together in one file is
> better
> 
> than some config is here and some config is there. So I move the
> whole  content

I would prefer not to duplicate this kind of configuration if we can
help it...

Cheers,

Richard

error in building qt5-image

[Niche Consulting India]

hello,
 i encountered this error when building qt5-image for ubuntu 14.04 on warrior branch.
 
 
Can someone tell me how to fix this? does this mean i checked out an older version of code?

————
# bit bake qt5-image
….
n file included from libavdevice/avdevice.h:51,
                 from libavdevice/avdevice.c:23:
./libavformat/avformat.h:2070:17: note: declared here
 AVOutputFormat *av_oformat_next(const AVOutputFormat *f);
                 ^~~~~~~~~~~~~~~
libavdevice/avdevice.c:92:13: warning: 'av_iformat_next' is deprecated [-Wdeprecated-declarations]
             if (!(prev = av_iformat_next(prev)))
             ^~
In file included from libavdevice/avdevice.h:51,
                 from libavdevice/avdevice.c:23:
./libavformat/avformat.h:2062:17: note: declared here
 AVInputFormat  *av_iformat_next(const AVInputFormat  *f);
                 ^~~~~~~~~~~~~~~
make[1]: *** write jobserver: Bad file descriptor.  Stop.
ERROR: oe_runmake failed
make: *** [compile] Error 2
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_compile (log file is located at /data/build_area/warrior/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_compile.26121)

Re: error in building qt5-image

[Khem Raj]

It seems to be a parallel build issue. Try to enforce -j1 and see if that helps

On Wed, Jul 31, 2019 at 8:23 AM Niche Consulting India
<contact@nicheconsult.in> wrote:
>
> hello,
>  i encountered this error when building qt5-image for ubuntu 14.04 on warrior branch.
>
>
> Can someone tell me how to fix this? does this mean i checked out an older version of code?
>
> ————
> # bit bake qt5-image
> ….
> n file included from libavdevice/avdevice.h:51,
>                  from libavdevice/avdevice.c:23:
> ./libavformat/avformat.h:2070:17: note: declared here
>  AVOutputFormat *av_oformat_next(const AVOutputFormat *f);
>                  ^~~~~~~~~~~~~~~
> libavdevice/avdevice.c:92:13: warning: 'av_iformat_next' is deprecated [-Wdeprecated-declarations]
>              if (!(prev = av_iformat_next(prev)))
>              ^~
> In file included from libavdevice/avdevice.h:51,
>                  from libavdevice/avdevice.c:23:
> ./libavformat/avformat.h:2062:17: note: declared here
>  AVInputFormat  *av_iformat_next(const AVInputFormat  *f);
>                  ^~~~~~~~~~~~~~~
> make[1]: *** write jobserver: Bad file descriptor.  Stop.
> ERROR: oe_runmake failed
> make: *** [compile] Error 2
> WARNING: exit code 1 from a shell command.
> ERROR: Function failed: do_compile (log file is located at /data/build_area/warrior/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_compile.26121)
>
> --
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky

Re: error in building qt5-image

[Niche Consulting India]

[-- Attachment #1: Type: text/plain, Size: 8412 bytes --]

there is no option to enforce single build process. Given below is usage of bit bake.

———
> Usage: bitbake [options] [recipename/target recipe:do_task ...]
> 
>     Executes the specified task (default is 'build') for a given set of target recipes (.bb files).
>     It is assumed there is a conf/bblayers.conf available in cwd or in BBPATH which
>     will provide the layer, BBFILES and other configuration information.
> 
> Options:
>   --version             show program's version number and exit
>   -h, --help            show this help message and exit
>   -b BUILDFILE, --buildfile=BUILDFILE
>                         Execute tasks from a specific .bb recipe directly.
>                         WARNING: Does not handle any dependencies from other
>                         recipes.
>   -k, --continue        Continue as much as possible after an error. While the
>                         target that failed and anything depending on it cannot
>                         be built, as much as possible will be built before
>                         stopping.
>   -f, --force           Force the specified targets/task to run (invalidating
>                         any existing stamp file).
>   -c CMD, --cmd=CMD     Specify the task to execute. The exact options
>                         available depend on the metadata. Some examples might
>                         be 'compile' or 'populate_sysroot' or 'listtasks' may
>                         give a list of the tasks available.
>   -C INVALIDATE_STAMP, --clear-stamp=INVALIDATE_STAMP
>                         Invalidate the stamp for the specified task such as
>                         'compile' and then run the default task for the
>                         specified target(s).
>   -r PREFILE, --read=PREFILE
>                         Read the specified file before bitbake.conf.
>   -R POSTFILE, --postread=POSTFILE
>                         Read the specified file after bitbake.conf.
>   -v, --verbose         Enable tracing of shell tasks (with 'set -x'). Also
>                         print bb.note(...) messages to stdout (in addition to
>                         writing them to ${T}/log.do_<task>).
>   -D, --debug           Increase the debug level. You can specify this more
>                         than once. -D sets the debug level to 1, where only
>                         bb.debug(1, ...) messages are printed to stdout; -DD
>                         sets the debug level to 2, where both bb.debug(1, ...)
>                         and bb.debug(2, ...) messages are printed; etc.
>                         Without -D, no debug messages are printed. Note that
>                         -D only affects output to stdout. All debug messages
>                         are written to ${T}/log.do_taskname, regardless of the
>                         debug level.
>   -q, --quiet           Output less log message data to the terminal. You can
>                         specify this more than once.
>   -n, --dry-run         Don't execute, just go through the motions.
>   -S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER
>                         Dump out the signature construction information, with
>                         no task execution. The SIGNATURE_HANDLER parameter is
>                         passed to the handler. Two common values are none and
>                         printdiff but the handler may define more/less. none
>                         means only dump the signature, printdiff means compare
>                         the dumped signature with the cached one.
>   -p, --parse-only      Quit after parsing the BB recipes.
>   -s, --show-versions   Show current and preferred versions of all recipes.
>   -e, --environment     Show the global or per-recipe environment complete
>                         with information about where variables were
>                         set/changed.
>   -g, --graphviz        Save dependency tree information for the specified
>                         targets in the dot syntax.
>   -I EXTRA_ASSUME_PROVIDED, --ignore-deps=EXTRA_ASSUME_PROVIDED
>                         Assume these dependencies don't exist and are already
>                         provided (equivalent to ASSUME_PROVIDED). Useful to
>                         make dependency graphs more appealing
>   -l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS
>                         Show debug logging for the specified logging domains
>   -P, --profile         Profile the command and save reports.
>   -u UI, --ui=UI        The user interface to use (knotty, ncurses or taskexp
>                         - default knotty).
>   --token=XMLRPCTOKEN   Specify the connection token to be used when
>                         connecting to a remote server.
>   --revisions-changed   Set the exit code depending on whether upstream
>                         floating revisions have changed or not.
>   --server-only         Run bitbake without a UI, only starting a server
>                         (cooker) process.
>   -B BIND, --bind=BIND  The name/address for the bitbake xmlrpc server to bind
>                         to.
>   -T SERVER_TIMEOUT, --idle-timeout=SERVER_TIMEOUT
>                         Set timeout to unload bitbake server due to
>                         inactivity, set to -1 means no unload, default:
>                         Environment variable BB_SERVER_TIMEOUT.
>   --no-setscene         Do not run any setscene tasks. sstate will be ignored
>                         and everything needed, built.
>   --setscene-only       Only run setscene tasks, don't run any real tasks.
>   --remote-server=REMOTE_SERVER
>                         Connect to the specified server.
>   -m, --kill-server     Terminate any running bitbake server.
>   --observe-only        Connect to a server as an observing-only client.
>   --status-only         Check the status of the remote bitbake server.
>   -w WRITEEVENTLOG, --write-log=WRITEEVENTLOG
>                         Writes the event log of the build to a bitbake event
>                         json file. Use '' (empty string) to assign the name
>                         automatically.
>   --runall=RUNALL       Run the specified task for any recipe in the taskgraph
>                         of the specified target (even if it wouldn't otherwise
>                         have run).
>   --runonly=RUNONLY     Run only the specified task within the taskgraph of
>                         the specified targets (and any task dependencies those
>                         tasks may have).

> On 31-Jul-2019, at 10:15 PM, Khem Raj <raj.khem@gmail.com> wrote:
> 
> It seems to be a parallel build issue. Try to enforce -j1 and see if that helps
> 
> On Wed, Jul 31, 2019 at 8:23 AM Niche Consulting India
> <contact@nicheconsult.in> wrote:
>> 
>> hello,
>> i encountered this error when building qt5-image for ubuntu 14.04 on warrior branch.
>> 
>> 
>> Can someone tell me how to fix this? does this mean i checked out an older version of code?
>> 
>> ————
>> # bit bake qt5-image
>> ….
>> n file included from libavdevice/avdevice.h:51,
>>                 from libavdevice/avdevice.c:23:
>> ./libavformat/avformat.h:2070:17: note: declared here
>> AVOutputFormat *av_oformat_next(const AVOutputFormat *f);
>>                 ^~~~~~~~~~~~~~~
>> libavdevice/avdevice.c:92:13: warning: 'av_iformat_next' is deprecated [-Wdeprecated-declarations]
>>             if (!(prev = av_iformat_next(prev)))
>>             ^~
>> In file included from libavdevice/avdevice.h:51,
>>                 from libavdevice/avdevice.c:23:
>> ./libavformat/avformat.h:2062:17: note: declared here
>> AVInputFormat  *av_iformat_next(const AVInputFormat  *f);
>>                 ^~~~~~~~~~~~~~~
>> make[1]: *** write jobserver: Bad file descriptor.  Stop.
>> ERROR: oe_runmake failed
>> make: *** [compile] Error 2
>> WARNING: exit code 1 from a shell command.
>> ERROR: Function failed: do_compile (log file is located at /data/build_area/warrior/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_compile.26121)
>> 
>> --
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky


[-- Attachment #2: Type: text/html, Size: 19277 bytes --]

Re: error in building qt5-image

[Richard Purdie]

On Wed, 2019-07-31 at 22:53 +0530, Niche Consulting India wrote:
> there is no option to enforce single build process. Given below is
> usage of bit bake.

PARALLEL_MAKE = ""

or

PARALLEL_MAKE_pn-omxplayer = ""

will do that either globally or for that specific recipe.

Cheers,

Richard

Re: [PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

[Changqing Li]

On 7/31/19 6:20 PM, richard.purdie@linuxfoundation.org wrote:
> On Wed, 2019-07-31 at 17:38 +0800, Changqing Li wrote:
>> On 7/31/19 5:00 PM, Richard Purdie wrote:
>>> On Wed, 2019-07-31 at 11:40 +0800, changqing.li@windriver.com
>>> wrote:
>>>> From: Changqing Li <changqing.li@windriver.com>
>>>>
>>>> Configrations:
>>>> MACHINE: qemux86-64
>>>> require conf/multilib.conf
>>>> MULTILIBS = "multilib:lib32"
>>>> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>>>>
>>>> Reproduce steps:
>>>> bitbake lib32-core-image-minimal
>>>> runqemu qemux86-64 nographic lib32-core-image-minimal
>>>>
>>>> Errors:
>>>> qemu cannot bootup since:
>>>> Booting from ROM...
>>>> This kernel requires an x86-64 CPU, but only detected an i686
>>>> CPU.
>>>> Unable to boot - please use a kernel appropriate for your CPU.
>>>> QEMU: Terminated
>>>>
>>>> For lib32 image, override has x86, so the qemubin set to qemu-
>>>> system-
>>>> i386,
>>>> fix by move qemuboot parameters to corresponding conf, don't use
>>>> the
>>>> override
>>> Why remove/move the whole file when its just QB_SYSTEM_NAME that is
>>> the
>>> issue and that alone could be moved?
>> I think maybe put qemuboot related parameter together in one file is
>> better
>>
>> than some config is here and some config is there. So I move the
>> whole  content
> I would prefer not to duplicate this kind of configuration if we can
> help it...
OK, I will send a V2 and only move QB_SYSTEM_NAME out
>
> Cheers,
>
> Richard
>
>
-- 
BRs

Sandy(Li Changqing)

Re: error in building qt5-image

[Niche Consulting India]

there is a bitbake.conf file which i had to locate as i am new to this ecosystem.
i was ale to build qt5 image but the tar.xz file which was generated, when i flashed it onto usb stick using dd, it is not booting up. can someone tell me what file to collect from tmp/deploy and what to do with it on mac os/xz to get the image to boot?

> On 01-Aug-2019, at 3:55 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> On Wed, 2019-07-31 at 22:53 +0530, Niche Consulting India wrote:
>> there is no option to enforce single build process. Given below is
>> usage of bit bake.
> 
> PARALLEL_MAKE = ""
> 
> or
> 
> PARALLEL_MAKE_pn-omxplayer = ""
> 
> will do that either globally or for that specific recipe.
> 
> Cheers,
> 
> Richard
> 
> 
> 
> 
>