All of lore.kernel.org
 help / color / mirror / Atom feed
* Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems
@ 2016-06-15  8:27 Anicic Damir (PSI)
  2016-06-15  9:31 ` Burton, Ross
  2016-06-15 19:23 ` Khem Raj
  0 siblings, 2 replies; 5+ messages in thread
From: Anicic Damir (PSI) @ 2016-06-15  8:27 UTC (permalink / raw)
  To: yocto

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

Hi !

I am trying to build Yocto 2.1 for PowerPC64, e6500 CPU.

I managed to build, with warnings that some steps will be postponed to first boot,
but if I add "read-only-rootfs" then warnings change to errors.

The problem seems to be missing qemu-ppc64, see down "exit code: 127".
qemu-* executables ( tmp/sysroots/x86_64-linux/usr/bin/qemu-* ) are built, but qemu-ppc64 is missing.

If I build qemu-ppc64 (qemu 2.6) myself (install it to /usr/local/bin which is in PATH),
then I get "Invalid instruction" from my qemu-ppc64.


My build (core-image-psi-gfa-cmd is basically core-image-full-cmdline ):

  Build Configuration:
  BB_VERSION        = "1.30.0"
  BUILD_SYS         = "x86_64-linux"
  NATIVELSBSTRING   = "ScientificLinux-6.4"
  TARGET_SYS        = "powerpc64-poky-linux"
  MACHINE           = "powerpc64-ppc64e6500"
  DISTRO            = "gfa-ppc64e6500"
  DISTRO_VERSION    = "2.1"
  TUNE_FEATURES     = "m64 fpu-hard e6500 altivec"
  TARGET_FPU        = ""
  meta
  meta-poky
  meta-yocto-bsp
  meta-gfa          = "krogoth-gfa-v2:898a78357e72fb80f1f8e26ba90bad5b7b054a4f"

  NOTE: Preparing RunQueue
  NOTE: Executing SetScene Tasks
  NOTE: Executing RunQueue Tasks
  WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log for details!
  WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstalls for the following packages will be postponed for first boot: libglib-2.0-0
  WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 'WARNING:'):
  [log_check] WARNING: The postinstall intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log for details!

  WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 'WARNING:'):
  [log_check] WARNING: The postinstalls for the following packages will be postponed for first boot: libglib-2


If I build core-image-psi-gfa-cmd ( which is basicaly core-image-lsb-sdk ),
then there are few more postinstall problems, too:
  The postinstalls for the following packages will be postponed for first boot:
                 libgdk-pixbuf-2.0-loader-ico libgdk-pixbuf-2.0-loader-bmp libgdk-pixbuf-2.0-loader-jpeg
                 libgdk-pixbuf-2.0-loader-png   libgdk-pixbuf-2.0-loader-gif libgdk-pixbuf-2.0-loader-xpm libgdk-pixbuf-2.0-loader-ani

all with the same qemu-ppc64 problem.


I have additionally eudev postinstall problem (generating hwdb.bin) -probably also qemu related


Please help.

Kind regards,

Damir



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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems
  2016-06-15  8:27 Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems Anicic Damir (PSI)
@ 2016-06-15  9:31 ` Burton, Ross
  2016-06-15 10:52   ` Burton, Ross
  2016-06-15 19:23 ` Khem Raj
  1 sibling, 1 reply; 5+ messages in thread
From: Burton, Ross @ 2016-06-15  9:31 UTC (permalink / raw)
  To: Anicic Damir (PSI); +Cc: yocto

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

On 15 June 2016 at 09:27, Anicic Damir (PSI) <damir.anicic@psi.ch> wrote:

> The problem seems to be missing qemu-ppc64, see down "exit code: 127".
> qemu-* executables ( tmp/sysroots/x86_64-linux/usr/bin/qemu-* ) are built,
> but qemu-ppc64 is missing.
>

Fixing this is trivial, add ppc64 to QEMU_TARGETS in qemu.inc.


> If I build qemu-ppc64 (qemu 2.6) myself (install it to /usr/local/bin
> which is in PATH),
> then I get "Invalid instruction" from my qemu-ppc64.
>

Can you test this again with QEMU_TARGETS changed to see what happens with
our own (patched) qemu?

Ross

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems
  2016-06-15  9:31 ` Burton, Ross
@ 2016-06-15 10:52   ` Burton, Ross
  0 siblings, 0 replies; 5+ messages in thread
From: Burton, Ross @ 2016-06-15 10:52 UTC (permalink / raw)
  To: Anicic Damir (PSI); +Cc: yocto

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

On 15 June 2016 at 10:31, Burton, Ross <ross.burton@intel.com> wrote:

> Fixing this is trivial, add ppc64 to QEMU_TARGETS in qemu.inc.
>

I'm wrong - this is more complicated as there's numerous options for
ppc64.  I've filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=9778
to track this.  Obviously we need qemuppc64 in oe-core to test this.

Ross

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems
  2016-06-15  8:27 Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems Anicic Damir (PSI)
  2016-06-15  9:31 ` Burton, Ross
@ 2016-06-15 19:23 ` Khem Raj
  2016-06-15 19:52   ` akuster
  1 sibling, 1 reply; 5+ messages in thread
From: Khem Raj @ 2016-06-15 19:23 UTC (permalink / raw)
  To: Anicic Damir (PSI); +Cc: yocto


[-- Attachment #1.1: Type: text/plain, Size: 3315 bytes --]


> On Jun 15, 2016, at 1:27 AM, Anicic Damir (PSI) <damir.anicic@psi.ch> wrote:
> 
> Hi !
> 
> I am trying to build Yocto 2.1 for PowerPC64, e6500 CPU.
> 
> I managed to build, with warnings that some steps will be postponed to first boot,
> but if I add "read-only-rootfs" then warnings change to errors.
> 
> The problem seems to be missing qemu-ppc64, see down "exit code: 127".
> qemu-* executables ( tmp/sysroots/x86_64-linux/usr/bin/qemu-* ) are built, but qemu-ppc64 is missing.
> 
> If I build qemu-ppc64 (qemu 2.6) myself (install it to /usr/local/bin which is in PATH),
> then I get "Invalid instruction" from my qemu-ppc64.
> 
> 
> My build (core-image-psi-gfa-cmd is basically core-image-full-cmdline ):
> 
>   Build Configuration:
>   BB_VERSION        = "1.30.0"
>   BUILD_SYS         = "x86_64-linux"
>   NATIVELSBSTRING   = "ScientificLinux-6.4"
>   TARGET_SYS        = "powerpc64-poky-linux"
>   MACHINE           = "powerpc64-ppc64e6500"
>   DISTRO            = "gfa-ppc64e6500"
>   DISTRO_VERSION    = "2.1"
>   TUNE_FEATURES     = "m64 fpu-hard e6500 altivec"
>   TARGET_FPU        = ""
>   meta
>   meta-poky
>   meta-yocto-bsp
>   meta-gfa          = "krogoth-gfa-v2:898a78357e72fb80f1f8e26ba90bad5b7b054a4f"
> 
>   NOTE: Preparing RunQueue
>   NOTE: Executing SetScene Tasks
>   NOTE: Executing RunQueue Tasks
>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log for details!
>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstalls for the following packages will be postponed for first boot: libglib-2.0-0
>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 'WARNING:'):
>   [log_check] WARNING: The postinstall intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log for details!
> 
>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 'WARNING:'):
>   [log_check] WARNING: The postinstalls for the following packages will be postponed for first boot: libglib-2
> 
> 
> If I build core-image-psi-gfa-cmd ( which is basicaly core-image-lsb-sdk ),
> then there are few more postinstall problems, too:
>   The postinstalls for the following packages will be postponed for first boot:
>                  libgdk-pixbuf-2.0-loader-ico libgdk-pixbuf-2.0-loader-bmp libgdk-pixbuf-2.0-loader-jpeg
>                  libgdk-pixbuf-2.0-loader-png   libgdk-pixbuf-2.0-loader-gif libgdk-pixbuf-2.0-loader-xpm libgdk-pixbuf-2.0-loader-ani
> 
> all with the same qemu-ppc64 problem.


we do not have qemuppc64 working correctly in all cases. We now depend on Qemu to do some compile tasks which are not easily cross compilable. Those will fail.

> 
> 
> I have additionally eudev postinstall problem (generating hwdb.bin) -probably also qemu related
> 
> 
> Please help.
> 
> Kind regards,
> 
> Damir
> 
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>

[-- Attachment #1.2: Type: text/html, Size: 9151 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems
  2016-06-15 19:23 ` Khem Raj
@ 2016-06-15 19:52   ` akuster
  0 siblings, 0 replies; 5+ messages in thread
From: akuster @ 2016-06-15 19:52 UTC (permalink / raw)
  To: Khem Raj, Anicic Damir (PSI); +Cc: yocto



On 06/15/2016 12:23 PM, Khem Raj wrote:
> 
>> On Jun 15, 2016, at 1:27 AM, Anicic Damir (PSI) <damir.anicic@psi.ch> wrote:
>>
>> Hi !
>>
>> I am trying to build Yocto 2.1 for PowerPC64, e6500 CPU.
>>
>> I managed to build, with warnings that some steps will be postponed to first boot,
>> but if I add "read-only-rootfs" then warnings change to errors.
>>
>> The problem seems to be missing qemu-ppc64, see down "exit code: 127".
>> qemu-* executables ( tmp/sysroots/x86_64-linux/usr/bin/qemu-* ) are built, but qemu-ppc64 is missing.
>>
>> If I build qemu-ppc64 (qemu 2.6) myself (install it to /usr/local/bin which is in PATH),
>> then I get "Invalid instruction" from my qemu-ppc64.
>>
>>
>> My build (core-image-psi-gfa-cmd is basically core-image-full-cmdline ):
>>
>>   Build Configuration:
>>   BB_VERSION        = "1.30.0"
>>   BUILD_SYS         = "x86_64-linux"
>>   NATIVELSBSTRING   = "ScientificLinux-6.4"
>>   TARGET_SYS        = "powerpc64-poky-linux"
>>   MACHINE           = "powerpc64-ppc64e6500"
>>   DISTRO            = "gfa-ppc64e6500"
>>   DISTRO_VERSION    = "2.1"
>>   TUNE_FEATURES     = "m64 fpu-hard e6500 altivec"
>>   TARGET_FPU        = ""
>>   meta
>>   meta-poky
>>   meta-yocto-bsp
>>   meta-gfa          = "krogoth-gfa-v2:898a78357e72fb80f1f8e26ba90bad5b7b054a4f"
>>
>>   NOTE: Preparing RunQueue
>>   NOTE: Executing SetScene Tasks
>>   NOTE: Executing RunQueue Tasks
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log for details!
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstalls for the following packages will be postponed for first boot: libglib-2.0-0
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 'WARNING:'):
>>   [log_check] WARNING: The postinstall intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log for details!
>>
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 'WARNING:'):
>>   [log_check] WARNING: The postinstalls for the following packages will be postponed for first boot: libglib-2
>>
>>
>> If I build core-image-psi-gfa-cmd ( which is basicaly core-image-lsb-sdk ),
>> then there are few more postinstall problems, too:
>>   The postinstalls for the following packages will be postponed for first boot:
>>                  libgdk-pixbuf-2.0-loader-ico libgdk-pixbuf-2.0-loader-bmp libgdk-pixbuf-2.0-loader-jpeg
>>                  libgdk-pixbuf-2.0-loader-png   libgdk-pixbuf-2.0-loader-gif libgdk-pixbuf-2.0-loader-xpm libgdk-pixbuf-2.0-loader-ani
>>
>> all with the same qemu-ppc64 problem.

There is no official qemuppc64 on OE. I do have it in my own bsp layer.
I will be submitting patches soon.

- armin
> 
> 
> we do not have qemuppc64 working correctly in all cases. We now depend on Qemu to do some compile tasks which are not easily cross compilable. Those will fail.
> 
>>
>>
>> I have additionally eudev postinstall problem (generating hwdb.bin) -probably also qemu related
>>
>>
>> Please help.
>>
>> Kind regards,
>>
>> Damir
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
> 
> 
> 


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2016-06-15 19:52 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-15  8:27 Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems Anicic Damir (PSI)
2016-06-15  9:31 ` Burton, Ross
2016-06-15 10:52   ` Burton, Ross
2016-06-15 19:23 ` Khem Raj
2016-06-15 19:52   ` akuster

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.