Re: [RFC PATCH 0/6] ISAR SDK root filesystem

["Maxim Yu. Osipov" <mosipov@ilbers.de>]

On 06/18/2018 09:08 AM, Henning Schild wrote:
> Am Thu, 14 Jun 2018 11:46:23 +0200
> schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> 
>> On 06/14/2018 10:48 AM, Henning Schild wrote:
>> <snip>
>>>> Limitation
>>>>
>>>> Only Debian Stretch for SDK root filesystem is supported as only
>>>> Stretch provides crossbuild environment by default. (Debian Jessie
>>>> requires some additional preconfiguration steps see
>>>> https://wiki.debian.org/CrossToolchains#Installation for
>>>> details).
>>>
>>> Are we ready for buster? Not many people care about the past, but
>>> let us make sure this will work in the future.
>>
>> Your patch regarding buster support is still pending as additional
>> feedback from you is needed (see email below I've sent you a week
>> ago).
> 
> Ok, i will look into the buster-wic thing. But my question is whether
> the SDK/crossbuild approach that works for stretch will also work for
> buster.

I didn't install buster, but from the first glance, approach should work 
for buster too as crossbuild-essential-* packages are shipped by default 
with buster (see f.e. 
ftp://ftp.de.debian.org/debian/dists/buster/main/binary-amd64/Packages.gz).

Kind regards,
Maxim.

> Henning
> 
>> 8<---
>>> -------- Forwarded Message --------
>>> Subject: Re: [PATCHv2 2/2] conf: Add support for new debian distro
>>> "buster" Date: Thu, 7 Jun 2018 11:53:13 +0200
>>> From: Maxim Yu. Osipov <mosipov@ilbers.de>
>>> Organization: ilbers GmbH
>>> To: Henning Schild <henning.schild@siemens.com>,
>>> isar-users@googlegroups.com CC: Alexander Smirnov
>>> <asmirnov@ilbers.de>
>>>
>>> Hello Henning,
>>>
>>> Did you experience the problem Alexander reported in email below?
>>>
>>> Kind regards,
>>> Maxim.
>>>
>>> On 05/27/2018 09:54 PM, Alexander Smirnov wrote:
>>>> Hi Henning,
>>>>
>>>> thank you for the first patch, now there is no problem with
>>>> trusted repo. But there is another issue with wic:
>>>>
>>>> 8<--
>>>> ERROR: mc:qemui386-buster:isar-image-base-1.0-r0 do_wic_image:
>>>> Function failed: do_wic_image (log file is located at
>>>> /home/builder/isar/build/tmp/work/debian-buster-i386/isar-image-base/temp/log.do_wic_image.6282)
>>>>    
>>
>> 8<---
>>
>>
>>>> Example
>>>>
>>>>    - Trigger creation of SDK root filesystem
>>>>
>>>>
>>>> bitbake -c do_isar_sdk multiconfig:qemuarm-stretch:isar-image-base
>>>>
>>>>
>>>>    - Mount the following directories in chroot by passing resulting
>>>> rootfs as an argument to the script `mount_chroot.sh`:
>>>>
>>>>
>>>> $ cat mount_chroot.sh
>>>> #!/bin/bash
>>>> sudo mount /tmp     $1/tmp                 -o bind
>>>> sudo mount proc     $1/proc    -t proc     -o nosuid,noexec,nodev
>>>> sudo mount sysfs    $1/sys     -t sysfs    -o nosuid,noexec,nodev
>>>> sudo mount devtmpfs $1/dev     -t devtmpfs -o mode=0755,nosuid
>>>> sudo mount devpts   $1/dev/pts -t devpts   -o gid=5,mode=620
>>>> sudo mount tmpfs    $1/dev/shm -t tmpfs    -o
>>>> rw,seclabel,nosuid,nodev
>>>>
>>>> $ ./mount_chroot.sh ./build/tmp/work/debian-stretch-armhf/sdkchroot/rootfs
>>>
>>> Imagine this being copied over to a totally different Linux-distro
>>> or into a docker container.
>>>
>>> The "sudos" should not be in the script. So people can choose to not
>>> use sudo at all or call the script with sudo.
>>
>> OK.
>>
>>> Maybe adding a Dockerfile would be a good idea to understand more
>>> such implications.
>>>
>>> Henning
>>
>> Kind regards,
>> Maxim.
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov