public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/7] Isar cross-compilation support
Date: Sun, 22 Jul 2018 23:15:10 +0300	[thread overview]
Message-ID: <877fdc7a-c6c7-5192-0113-ce4b9a0f5b68@ilbers.de> (raw)
In-Reply-To: <2ce080a3-ab36-6a00-c8cb-80ff2d39b7f3@siemens.com>



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 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

  reply	other threads:[~2018-07-22 20:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 13:18 Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 1/7] isar-bootstrap: Update routine to determine host arch Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 2/7] buildchroot: Split generic part Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 3/7] buildchroot: Add host buildchroot Alexander Smirnov
2018-07-17 19:48   ` Jan Kiszka
2018-07-17 13:18 ` [PATCH v3 4/7] isar-bootstrap-helper: Add target architecture for dpkg Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 5/7] build.sh: Add additional parameter Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 6/7] cross-compilation: Introduce variable switch Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 7/7] linux: Add cross-compilation support Alexander Smirnov
2018-07-17 13:38 ` [PATCH v3 0/7] Isar " Jan Kiszka
2018-07-17 14:40   ` Jan Kiszka
2018-07-17 15:06     ` Alexander Smirnov
2018-07-17 15:18       ` Alexander Smirnov
2018-07-17 15:24         ` Jan Kiszka
2018-07-17 15:29           ` Alexander Smirnov
2018-07-17 15:41   ` Alexander Smirnov
2018-07-17 19:45     ` Jan Kiszka
2018-07-17 20:48       ` Alexander Smirnov
2018-07-18  7:06         ` Jan Kiszka
2018-07-18  8:19           ` Jan Kiszka
2018-07-18  8:37             ` Jan Kiszka
2018-07-18 18:52           ` Alexander Smirnov
2018-07-18 19:00             ` Jan Kiszka
2018-07-19 20:59               ` Alexander Smirnov
2018-07-20  5:56                 ` Jan Kiszka
2018-07-22 20:15                   ` Alexander Smirnov [this message]
2018-07-22 20:32                     ` Alexander Smirnov
2018-07-22 21:54                       ` Jan Kiszka
2018-07-23  6:55                         ` Jan Kiszka
2018-07-24  8:21                         ` Jan Kiszka
2018-07-22 21:40                     ` 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=877fdc7a-c6c7-5192-0113-ce4b9a0f5b68@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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