Re: [PATCH v3 0/7] Isar cross-compilation support

[Alexander Smirnov <asmirnov@ilbers.de>]

Hi Jan,

On 07/22/2018 11:15 PM, Alexander Smirnov wrote:
> 
> 
> On 07/20/2018 08:56 AM, Jan Kiszka wrote:
>> Hi Alex,
>>
>> On 2018-07-19 22:59, Alexander Smirnov wrote:
>>> Hi Jan,
>>>
>>> [...]
>>>
>>>>> Just an observation, you use here buster but I didn't test it.
>>>>
>>>> Yes, but only for the pre-built u-boot package, and only for the Orange
>>>> Pi. See conf/multiconfig/preferences.orangepi-zero.conf.
>>>
>>> I've found several issue with v3 regarding kernel and modules 
>>> cross-compilation. I've fixed them and pushed asmirnov/devel branch.
>>>
>>> Now I'm able to cross-build orangepi kernel and example-module for 
>>> it, huh! :-)
>>
>> That's good news, and I can confirm that at least the linux-headers 
>> packages looks good now. It's also clear now that there can be no 
>> mixed-mode when building kernel modules because this package with its 
>> host tools is generated for the build host, not the target arch.
>>
>> However, I'm still stuck on the Python dependency problems. I bet you 
>> can also reproduce them by declaring the hello package to build-depend 
>> on "python". Same for "python-pip".
>>

I've found an interesting notes here:

https://wiki.debian.org/DebianBootstrap/TODO#Remove_blockers_for_:any_and_:native_introduction

adding native qualifier for python solves the issue for me (i.e. 
python:native).

Do you think current status contains enough functionality for the first
implementation, so I could format clean patches and add the documentation?

Alex

>>>
>>> I've tried to make commits on the top small just to demonstrate my 
>>> findings.
>>>
>>> Could you please try this branch with your use-case? Unfortunately I 
>>> wasn't able to quickly run clean jailhoust build, I have fedora as 
>>> host OS and use debian in chroot. I've tried to run build scripts but 
>>> docker fails with tons of errors :-(
>>
>> Can you share your error dump? That would be interesting as the whole 
>> docker story is about removing the host-side dependency on a 
>> particular distribution with a particular package set pre-installed, 
>> not to speak of the sudo config hack.
> 
> builder@zbook:~/jailhouse-images$ sudo 
> KAS_TARGET="multiconfig:orangepi-zero-jailhouse:demo-image" 
> ./build-images.sh
> Unable to find image 'kasproject/kas-isar:latest' locally
> latest: Pulling from kasproject/kas-isar
> 6de29172b78c: Pull complete
> 0e2ff9900052: Pull complete
> 89b3b64c6e1a: Pull complete
> c4ede5890983: Pull complete
> 63b0417b6e80: Pull complete
> 2095a826ca1c: Pull complete
> 519ff2acda8f: Pull complete
> 3568c8b200f9: Pull complete
> 84fb75e6e501: Pull complete
> a8e3362d930a: Pull complete
> fa1925a99ab2: Pull complete
> af55a23213f5: Pull complete
> 2f0f64c16666: Pull complete
> 875a76dca692: Pull complete
> 4e9bfef3b1d2: Pull complete
> 6e603ec88847: Pull complete
> b41c12cafe1e: Pull complete
> cf73b0705769: Pull complete
> Digest: 
> sha256:c44212948d6f9b60faf17f3e769cc7bc926873ff1628adafb5c1ff1960931177
> Status: Downloaded newer image for kasproject/kas-isar:latest
> FATA[0085] Error response from daemon: Cannot start container 
> 32bdec7e11264b90a4090ea2892cb9b359a8f95b8b42e1c81ac2010d63ebefa3: [8] 
> System error: mountpoint for cpu not found
> 
> 
>>
>> If you have a Debian 9 build host, you can also leave out the docker 
>> wrapping, just installing kas via pip and then doing
>>
>> mkdir -p out
>> cd out
>> kas build /path/to/jailhouse-images/kas.yml
>>
> 
> Will try, thanks for the hint!
> 
> Alex
>