public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2] conf: Add support for new debian distro "buster"
Date: Thu, 16 Aug 2018 17:04:53 +0200	[thread overview]
Message-ID: <10dd4117-b80f-6d4d-58a6-5cd678b6488d@siemens.com> (raw)
In-Reply-To: <20180816170323.3115df3f@md1pvb1c.ad001.siemens.net>

On 2018-08-16 17:03, Henning Schild wrote:
> Am Thu, 16 Aug 2018 16:51:29 +0200
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> 
>> On 2018-08-16 16:49, [ext] Henning Schild wrote:
>>> Am Thu, 16 Aug 2018 14:57:44 +0300
>>> schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
>>>    
>>>> Hi Henning,
>>>>
>>>> It seems that under jessie we have similar problem with unsupported
>>>> syscall with qemuarm as we had with qemuarm64 on stretch:
>>>>
>>>> cat
>>>> build/tmp/work/debian-buster-armhf/buildchroot-target/temp/log.do_build:
>>>> === Setting up libperl5.26:armhf (5.26.2-7) ...
>>>> Setting up man-db (2.8.4-2) ...
>>>> Building database of manual pages ...
>>>> qemu: Unsupported syscall: 383
>>>> ===
>>>>
>>>> May be it makes sense to exclude for now qemuarm from buster patch
>>>> (at least while we support jessie)?
>>>
>>> No. For arm64 i agree, we have that problem and can not build buster
>>> images from any distro < buster. But for arm we just have that
>>> problem for debian8 and not 9, so arm should be part of the patch.
>>
>> So, qemu-user-static from buster works fine? Is there possibly some
>> backport of that available for stretch?
> 
> I did not try that yet, and there do not seem to be backports.
> 

As it's "static", we would likely be fine with the buster package - 
provided that helps.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-08-16 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15  2:26 Maxim Yu. Osipov
2018-08-16  8:48 ` Henning Schild
2018-08-16  8:56   ` Jan Kiszka
2018-08-16  9:04   ` Maxim Yu. Osipov
2018-08-16  9:04 ` Henning Schild
2018-08-16 11:57   ` Maxim Yu. Osipov
2018-08-16 14:49     ` Henning Schild
2018-08-16 14:51       ` Jan Kiszka
2018-08-16 15:03         ` Henning Schild
2018-08-16 15:04           ` Jan Kiszka [this message]
2018-08-16 15:10             ` Henning Schild
2018-08-16 15:14               ` Jan Kiszka
2018-08-16 16:20                 ` Henning Schild
2018-08-16 16:25                   ` Jan Kiszka
2018-08-16 15:10       ` Maxim Yu. Osipov

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=10dd4117-b80f-6d4d-58a6-5cd678b6488d@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox