All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: <Venkata.Pyla@toshiba-tsip.com>, <cip-dev@lists.cip-project.org>
Cc: <dinesh.kumar@toshiba-tsip.com>, <kazuhiro3.hayashi@toshiba.co.jp>
Subject: Re: [cip-dev] [isar-cip-core] cip arm64 build breaks
Date: Tue, 10 May 2022 14:20:53 +0200	[thread overview]
Message-ID: <96356bc9-65d4-ac2c-a0aa-a7f72366afd7@siemens.com> (raw)
In-Reply-To: <OSYPR01MB554240252AF3065DB21B6004A4C99@OSYPR01MB5542.jpnprd01.prod.outlook.com>

On 10.05.22 14:06, Venkata.Pyla@toshiba-tsip.com wrote:
> Hi Jan,
> 
> Thanks for the work to support secureboot in arm64.
> 
> I am building the arm64 image to check secureboot support in arm64, got the below error and do you have any idea about this error.
> 
> ---------------------------------------
> $ ./kas-container build kas-cip.yml:kas/board/qemu-arm64.yml:kas/opt/5.10.yml:kas/opt/bullseye.yml
> :
> .
> I: Extracting liblzma5...
> I: Extracting zlib1g...
> W: Failure trying to run: chroot "/build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/rootfs" /sbin/ldconfig
> W: See /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/rootfs/debootstrap/debootstrap.log for details
> WARNING: exit code 1 from a shell command.
> ERROR: Logfile of failure stored in: /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/temp/log.do_bootstrap.307
> :
> .
> ---------------------------------------
> When I see the bootstrap log at the end it shows "Segmentation fault (core dumped)"
> 
> Thanks,
> Venkata.
> 
> 

Is your kas-container recent?

Do you happen to have qemu-user-static installed also on the host? If
so, please try to remove it then?

Note that CI also passes.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2022-05-10 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 12:06 [cip-dev] [isar-cip-core] cip arm64 build breaks Venkata.Pyla
2022-05-10 12:20 ` Jan Kiszka [this message]
2022-05-10 14:57   ` Venkata.Pyla
2022-05-10 16:33     ` Jan Kiszka

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=96356bc9-65d4-ac2c-a0aa-a7f72366afd7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Venkata.Pyla@toshiba-tsip.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=dinesh.kumar@toshiba-tsip.com \
    --cc=kazuhiro3.hayashi@toshiba.co.jp \
    /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.