From: Alexander Smirnov <asmirnov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v5 05/12] build.sh: Add additional parameter
Date: Thu, 2 Aug 2018 21:16:56 +0300 [thread overview]
Message-ID: <495be0e7-bd1b-63d5-ccae-8732d562ccfc@ilbers.de> (raw)
In-Reply-To: <20180802190524.3ee62b68@md1pvb1c.ad001.siemens.net>
Hi Henning,
On 02.08.2018 20:05, Henning Schild wrote:
> Am Thu, 2 Aug 2018 14:05:12 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>
>> Hi everybody,
>>
>> On 02.08.2018 10:56, Henning Schild wrote:
>>> Am Wed, 1 Aug 2018 17:51:57 +0300
>>> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>>>
>>>> On 30.07.2018 22:39, Alexander Smirnov wrote:
>>>>> Pass target architecture as a parameter for build.
>>>>>
>>>>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>>>>> ---
>>>>> meta/recipes-devtools/buildchroot/files/build.sh | 17
>>>>> +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh
>>>>> b/meta/recipes-devtools/buildchroot/files/build.sh index
>>>>> 73c0889..c2967d2 100644 ---
>>>>> a/meta/recipes-devtools/buildchroot/files/build.sh +++
>>>>> b/meta/recipes-devtools/buildchroot/files/build.sh @@ -6,6 +6,19
>>>>> @@
>>>>> set -e
>>>>>
>>>>> +# Create human-readable names
>>>>> +target_arch=$2
>>>>> +
>>>>> +# Notes:
>>>>> +# mk-build-deps for jessie and jtretch has different parameter
>>>>> name to specify +# host architecture.
>>>>> +debian_version=$(cut -c1 /etc/debian_version)
>>>>> +if [ $(($debian_version)) -ge 9 ]; then
>>>>
>>>> Damn! This doesn't work on stretch:
>>>>
>>>> $ cat /etc/debian_version
>>>> stretch/sid
>>>
>>> Maybe that is an old installation when stretch was still sid?
>>> What does "lsb_release -r" say on that machine? That might be the
>>> better tool, instead of looking directly at the file.
>>> And it might be a good idea to turn the logic around. So if the
>>> check somehow does not work we default to "new".
>>>
>>
>> Sorry for the false alarm, I was in Ubuntu 16.04 chroot. :-( For
>> Debian it's correct:
>
> Did you experiment with building Ubuntu images with Isar? That is
> something i thought about. Not that i want Ubuntu for anything, the
> opposite is true, but to get those communities looking at Isar.
>
Not yet, but I agree with, that this would be helpful. Let me try at
least Ubuntu 16.04 will come back with the results.
Alex
> Henning
>
>> $ cat /etc/debian_version
>> 9.5
>>
>> Alex
>>
>>> Henning
>>>
>>>> But on jessie there were numbers. Will fix this.
>>>>
>>>> Alex
>>>>
>>>>> + set_arch="--host-arch $target_arch"
>>>>> +else
>>>>> + set_arch="-a $target_arch"
>>>>> +fi
>>>>> +
>>>>> # Go to build directory
>>>>> cd $1
>>>>>
>>>>> @@ -36,7 +49,7 @@ install_cmd="apt-get -o
>>>>> Debug::pkgProblemResolver=yes --no-install-recommends -y -o
>>>>> APT::Get::List-Cleanup="0"
>>>>> # Install all build deps
>>>>> - mk-build-deps -t "${install_cmd}" -i -r debian/control
>>>>> + mk-build-deps $set_arch -t "${install_cmd}" -i -r
>>>>> debian/control ) 42>/dpkg.lock
>>>>>
>>>>> # If autotools files have been created, update their timestamp
>>>>> to @@ -48,4 +61,4 @@ for i in configure aclocal.m4 Makefile.am
>>>>> Makefile.in; do done
>>>>>
>>>>> # Build the package
>>>>> -dpkg-buildpackage
>>>>> +dpkg-buildpackage -a$target_arch
>>>>>
>>>>
>>>
>
next prev parent reply other threads:[~2018-08-02 18:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 19:39 [PATCH v5 00/12] Cross-compilation Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 01/12] isar-bootstrap: Update routine to determine host arch Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 02/12] buildchroot: Split generic part Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 03/12] buildchroot: Add host buildchroot Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 04/12] isar-bootstrap-helper: Add target architecture for dpkg Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 05/12] build.sh: Add additional parameter Alexander Smirnov
2018-08-01 14:51 ` Alexander Smirnov
2018-08-02 4:05 ` Maxim Yu. Osipov
2018-08-02 7:56 ` Henning Schild
2018-08-02 11:05 ` Alexander Smirnov
2018-08-02 17:05 ` Henning Schild
2018-08-02 18:16 ` Alexander Smirnov [this message]
2018-07-30 19:39 ` [PATCH v5 06/12] cross-compilation: Introduce variable switch Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 07/12] linux: Add ARM cross-compilation support Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 08/12] isar: Add ARM64 " Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 09/12] linux-module: Export ARCH and CROSS_COMPILE Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 10/12] linux: Drop gcc from dependencies Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 11/12] doc: Provide some notes about cross-compilation Alexander Smirnov
2018-07-30 19:39 ` [PATCH v5 12/12] scripts/ci_build.sh: Add cross-compilation test Alexander Smirnov
2018-08-02 19:00 ` [PATCH v5 00/12] Cross-compilation Alexander Smirnov
2018-08-06 7:57 ` Maxim Yu. Osipov
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=495be0e7-bd1b-63d5-ccae-8732d562ccfc@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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