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

[Alexander Smirnov <asmirnov@ilbers.de>]

On 07/17/2018 06:06 PM, Alexander Smirnov wrote:
> On 07/17/2018 05:40 PM, Jan Kiszka wrote:
>> On 2018-07-17 15:38, [ext] Jan Kiszka wrote:
>>> On 2018-07-17 15:18, Alexander Smirnov wrote:
>>>> Hi everybody,
>>>>
>>>> sorry for the delay, this is the third version of cross-compilation
>>>> support for Isar.
>>>>
>>>
>>> Thanks for the update!
>>>
>>>> Supported targets for cross-compilation:
>>>>   - stretch armhf
>>>>   - stretch amd64
>>>>
>>>> Artifacts could be cross-compiled:
>>>>   - dpkg.bbclass users
>>>>   - dpkg-raw.bbclass users
>>>>   - kernel
>>>>
>>>> Known issues:
>>>>   - if target and host architectures are the same, there is no need
>>>>     to use host buildchroot.
>>>>   - kernel module doesn't support cross-compilation. Default 
>>>> linux-headers
>>>>     package depends from target gcc binaries. So attempt to install, 
>>>> for
>>>>     example linux-headers-armmp, tries to install gcc:armhf, what rises
>>>>     conflict with the host tools.
>>>
>>> Could you imagine overriding such specialties with extra rules, even if
>>> package specific? Not having kernel module in the cross compilation
>>> chain main cause troubles (or does it work fine to cross-build the
>>> kernel and then natively build the modules?).
>>>
>>>>
>>>> To enable cross-compilation, the variable ISAR_CROSS_COMPILE should 
>>>> be set
>>>> to "1" in local.conf file.
>>>
>>> I will retry that series soon, on my standard testcase jailhouse-images.
>>> It's growing and urgently needs an accelerator :).
>>>
>>
>> What's the baseline of these patches, master? Why not using next?
>>
> 
> mosipov-devel to avoid additional rebase, let me check.
> 

Sorry, mosipov-next.

Alex