Re: [PATCH 5/9] buildchroot-cross: Initial implementation

[Alexander Smirnov <asmirnov@ilbers.de>]

Hi Jan,

On 06/15/2018 02:12 PM, Jan Kiszka wrote:
> On 2018-06-15 12:56, Alexander Smirnov wrote:
>> On Thu, Jun 14, 2018 at 05:55:48PM +0200, Jan Kiszka wrote:
>>> On 2018-06-13 15:08, Alexander Smirnov wrote:
>>>> Add initial generation of buildchroot for cross-compilation.
>>>>
>>>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>>>> ---
>>>>   meta/conf/isar-bitbake.conf                        |  1 +
>>>>   .../buildchroot/buildchroot-cross.bb               | 53 ++++++++++++++++++++++
>>>>   .../buildchroot/files/build-cross.sh               | 29 ++++++++++++
>>>>   3 files changed, 83 insertions(+)
>>>>   create mode 100644 meta/recipes-devtools/buildchroot/buildchroot-cross.bb
>>>>   create mode 100644 meta/recipes-devtools/buildchroot/files/build-cross.sh
>>>>
>>>> diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf
>>>> index ead7798..1412508 100644
>>>> --- a/meta/conf/isar-bitbake.conf
>>>> +++ b/meta/conf/isar-bitbake.conf
>>>> @@ -22,6 +22,7 @@ WORKDIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PF}"
>>>>   DL_DIR = "${TOPDIR}/downloads"
>>>>   SSTATE_DIR ?= "${TMPDIR}/sstate-cache"
>>>>   BUILDCHROOT_DIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot/rootfs"
>>>> +BUILDCHROOT_CROSS_DIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-cross/rootfs"
>>>>   CACHE = "${TMPDIR}/cache"
>>>>   
>>>>   OVERRIDES_append = ":${DISTRO}:${DISTRO_ARCH}"
>>>> diff --git a/meta/recipes-devtools/buildchroot/buildchroot-cross.bb b/meta/recipes-devtools/buildchroot/buildchroot-cross.bb
>>>> new file mode 100644
>>>> index 0000000..935a626
>>>> --- /dev/null
>>>> +++ b/meta/recipes-devtools/buildchroot/buildchroot-cross.bb
>>>> @@ -0,0 +1,53 @@
>>>> +# Root filesystem for packages cross-building
>>>> +#
>>>> +# This software is a part of ISAR.
>>>> +# Copyright (C) 2015-2016 ilbers GmbH
>>>> +
>>>> +DESCRIPTION = "Isar development cross-filesystem"
>>>> +
>>>> +LICENSE = "gpl-2.0"
>>>> +LIC_FILES_CHKSUM = "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
>>>> +
>>>> +FILESPATH_prepend := "${THISDIR}/files:"
>>>> +SRC_URI = "file://configscript.sh \
>>>> +           file://build-cross.sh"
>>>> +PV = "1.0"
>>>> +
>>>> +inherit isar-bootstrap-helper
>>>> +
>>>> +BUILDCHROOT_CROSS_PREINSTALL ?= "gcc-multilib \
>>>> +                                 make \
>>>> +                                 build-essential \
>>>> +                                 debhelper \
>>>> +                                 autotools-dev \
>>>> +                                 dpkg \
>>>> +                                 locales \
>>>> +                                 docbook-to-man \
>>>> +                                 apt \
>>>> +                                 automake \
>>>> +                                 devscripts \
>>>> +                                 equivs"
>>>> +
>>>> +# TODO: make this inclusion depending on the target arch
>>>> +BUILDCHROOT_CROSS_PREINSTALL += "binutils"
>>>> +
>>>> +WORKDIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PN}"
>>>> +
>>>> +do_build[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
>>>> +do_build[root_cleandirs] = "${BUILDCHROOT_CROSS_DIR} \
>>>> +                            ${BUILDCHROOT_CROSS_DIR}/isar-apt \
>>>> +                            ${BUILDCHROOT_CROSS_DIR}/downloads \
>>>> +                            ${BUILDCHROOT_CROSS_DIR}/home/builder"
>>>> +do_build[depends] = "isar-apt:do_cache_config isar-bootstrap-host:do_deploy"
>>>> +
>>>> +do_build() {
>>>> +    setup_root_file_system --host-arch "${BUILDCHROOT_CROSS_DIR}" ${BUILDCHROOT_CROSS_PREINSTALL}
>>>> +
>>>> +    # Install package builder script
>>>> +    sudo chmod -R a+rw "${BUILDCHROOT_CROSS_DIR}/home/builder"
>>>> +    sudo install -m 755 ${WORKDIR}/build-cross.sh ${BUILDCHROOT_CROSS_DIR}/build.sh
>>>> +
>>>> +    # Configure root filesystem
>>>> +    sudo install -m 755 ${WORKDIR}/configscript.sh ${BUILDCHROOT_CROSS_DIR}
>>>> +    sudo chroot ${BUILDCHROOT_CROSS_DIR} /configscript.sh
>>>> +}
>>>> diff --git a/meta/recipes-devtools/buildchroot/files/build-cross.sh b/meta/recipes-devtools/buildchroot/files/build-cross.sh
>>>> new file mode 100644
>>>> index 0000000..8c3ddaf
>>>> --- /dev/null
>>>> +++ b/meta/recipes-devtools/buildchroot/files/build-cross.sh
>>>> @@ -0,0 +1,29 @@
>>>> +#!/bin/bash
>>>> +#
>>>> +# This software is a part of ISAR.
>>>> +# Copyright (C) 2015-2017 ilbers GmbH
>>>> +# Copyright (c) 2018 Siemens AG
>>>> +
>>>> +set -e
>>>> +
>>>> +# Go to build directory
>>>> +cd $1
>>>> +
>>>> +# Add target architecture
>>>> +dpkg --add-architecture $2
>>>> +
>>>> +# To avoid Perl locale warnings:
>>>> +export LC_ALL=C
>>>> +export LANG=C
>>>> +export LANGUAGE=C
>>>> +
>>>> +# If autotools files have been created, update their timestamp to
>>>> +# prevent them from being regenerated
>>>> +for i in configure aclocal.m4 Makefile.am Makefile.in; do
>>>> +    if [ -f "${i}" ]; then
>>>> +        touch "${i}"
>>>> +    fi
>>>> +done
>>>> +
>>>> +# Build the package
>>>> +dpkg-buildpackage -a$2
>>>>
>>>
>>> This build-cross.sh doesn't install any of the build dependencies the
>>> target package lists. How do they come in? Or is this a limitation of
>>> this version? For the kernel cross-build, I'm currently trying to
>>> translate the what is needed for a corresponding build-kernel-cross.sh.
>>>
>>
>> That's exactly the limitation of this series about which I mentioned in
>> the cover letter. Attempt to install them in similar way like for
>> 'build.sh' failed, due to it tries to replace native packages like:
>> build-essentials, binutils by foreign ones :-(. Henning already proposed
>> to try to play with mk-build-deps params, so I'm going to do this.
> 
> OK, this would be a road-blocker for building anything cross. Already
> libhello would lack docbook-to-man (if that is a real dependency).
> 
>>
>>> Those packages would go into the cross-buildchroot, or are we also using
>>> the native buildchroot here?
>>
>> buildchroot and buildchroot-cross has nothing common except isar-apt
>> repository.
> 
> So the plan is to install all build deps into the buildchroot-cross, right?
> 
> Is there an officially documented way in Debian to do cross builds? What
> does it say regarding build-deps installation?
> 

According to the following link (and some others):

https://wiki.debian.org/Multiarch/HOWTO#Installing_cross-dependencies

The official way to install build deps:

$ apt-get build-dep ...

But this doesn't work for us, because we have no source package yet :-(

Alex