From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6546059049526362112 X-Received: by 2002:a81:a40e:: with SMTP id b14-v6mr1768002ywh.207.1524148856907; Thu, 19 Apr 2018 07:40:56 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a25:5c6:: with SMTP id 189-v6ls1038100ybf.14.gmail; Thu, 19 Apr 2018 07:40:56 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+txQ18TvruXvxi9LqzBL5PbYZGKlYrfB1XA1cqkvAodiYcqr+UHfMJKP2omwP8H3ydSTK6 X-Received: by 2002:a5b:ccd:: with SMTP id e13-v6mr2147529ybr.12.1524148856464; Thu, 19 Apr 2018 07:40:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524148856; cv=none; d=google.com; s=arc-20160816; b=aA9g6x5Tnal5HbxxBtEsZ9AYqRrl/Ohr0qBcGAc/rwfRQIVHC8ZAbVOwLg7hfwpoO7 vkuNeninra3mFwN0JtxplglCiZwgyAszqVCgyBDgIwmtOTG4OpvlNQmX7J8jRys4XwUz 46L59k+YOF+NU2Jncvkf6pcZEDO1SP4ik9HeNGKauSeyQH30/wwRjt/r/kNMUj9Cmo/R SqRnjY4XyY/Kd9bWRRdPW+oC0mhzPKg8EiShZY5Yyr3qvlnOaVFwa+XGy1dBq6VL2xE5 9a0DdCSJup5tYtKeecsg5dESa3225mbVvhTEh2gtC4p1NinuKr8NI0mZm0kkVy84+MDY llsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature:arc-authentication-results; bh=W1EaQ4+FAEg45nJ8hBnW+lxudvodM8BhIoO1lUss2m0=; b=g0f9TfzeSNcVOT0VvNDb/JrhsA+wIpU09/YA5/a3zQXabxBJmgXST8WnWpNQLMC0RQ mwIU7PRTz7hL+HlNOXBr6nq/spxsz5dxkNEpHfLE6Eccw53vDQce55tCUILU0/V0gzd2 Lxj70Exfp886B+fazytrgBr3OhAhEsYkJtqs8yGNH8Ch3xgOmXRLtAdQbmvWeJrmijEi e4hRkDWe7aDQJH2GwzPeQBdfZxXkki/KW52GSQ/ZeIG++EkIkrdliimqmOPReG0emj/l ecMhVUDQJYfr9OXrdO7UJKW/SxZYlTXLYYJoLxQfLwNDAzmOpuU22RT8ck6pwgq/C+Qm 9bZw== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@solid-run-com.20150623.gappssmtp.com header.s=20150623 header.b=TGyT7rYn; spf=pass (google.com: domain of jon@solid-run.com designates 2607:f8b0:4001:c0b::22a as permitted sender) smtp.mailfrom=jon@solid-run.com Return-Path: Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com. [2607:f8b0:4001:c0b::22a]) by gmr-mx.google.com with ESMTPS id k15-v6si223943ybm.1.2018.04.19.07.40.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Apr 2018 07:40:56 -0700 (PDT) Received-SPF: pass (google.com: domain of jon@solid-run.com designates 2607:f8b0:4001:c0b::22a as permitted sender) client-ip=2607:f8b0:4001:c0b::22a; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@solid-run-com.20150623.gappssmtp.com header.s=20150623 header.b=TGyT7rYn; spf=pass (google.com: domain of jon@solid-run.com designates 2607:f8b0:4001:c0b::22a as permitted sender) smtp.mailfrom=jon@solid-run.com Received: by mail-it0-x22a.google.com with SMTP id h143-v6so7312455ita.4 for ; Thu, 19 Apr 2018 07:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=solid-run-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W1EaQ4+FAEg45nJ8hBnW+lxudvodM8BhIoO1lUss2m0=; b=TGyT7rYnGS/c04UhcqowVA3++jkokgCn72QsDqzfL7h7IulP796uPfQsBAVdwvU1GL 0K6bPrhTa6YGeuls8nH2g/bRI8Mau38odwqhW1BIYHhrYFXBpqTzrbOruOwtO9ORq3+D d2wuDg0edmpkzE96rBvs56d5UkLOFckIln2bNNpi0QVjcT0mazPEsDjOsgTcKdEp5E6H 3pwnpnGxjCk4SbFuEjEs5mttyahVLTml/IPiBNVR7y5P/v3z6af4ye/VG7nXpQ6OVE2i wN3jCafCCpZEyhW0pNNtV9QIRdbLLMCbsxDdZKiwzOo57A0rX80tAeIxGJP11pOHFbJm pqSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W1EaQ4+FAEg45nJ8hBnW+lxudvodM8BhIoO1lUss2m0=; b=iM+xUlVeJYwpL3gd916BmyR8YsbM+Fr0sunxyBYZspLaFN5EfWgDkwHG9dRHLqh3XU 15P8iSqs9io3uynifcNEu9AOhWxXbIO3mCBqKuy0ik1r6a17jbL0R+RUMGlFOJ0IhWBE 1YlJBUNTcLQhvVnHbHDeDw7pn/Zv2/aIm2weBytRmEWvhpIBZKy4iWdIzU38iubdE85a xnQOfB5N3w1QPy1MDB8TShuzswWbAR5i2Qt+ThxDDK/dNDjD5Vz++7CZ0QhG0bYdHg3B eUglgRm6xcJIGzIZrqd2FyCrJcxu1MCn9DDlHzuUL4J0Py/VTohOK+RQK7r6x21Z3HUA 5ZKQ== X-Gm-Message-State: ALQs6tAgIW1clnLYwiiyXLr0x4gpGAR3iwm+Z3CKv4CizY1lg31IHto3 W7TNb8LlzMN0CQ1t9Dz1tUWNVvCGSktBL1nltEUMIQ== X-Received: by 2002:a24:c644:: with SMTP id j65-v6mr7203544itg.109.1524148856027; Thu, 19 Apr 2018 07:40:56 -0700 (PDT) MIME-Version: 1.0 References: <20180419111904.7436c6a0@mmd1pvb1c.ad001.siemens.net> <20180419123812.7c8f9a0f@mmd1pvb1c.ad001.siemens.net> <20180419154713.35046708@mmd1pvb1c.ad001.siemens.net> In-Reply-To: From: Jon Nettleton Date: Thu, 19 Apr 2018 14:40:45 +0000 Message-ID: Subject: Re: building custom kernel fails To: Alexander Smirnov Cc: isar-users Content-Type: multipart/alternative; boundary="000000000000260e45056a348f9f" X-TUID: 1OD2S62tGpPr --000000000000260e45056a348f9f Content-Type: text/plain; charset="UTF-8" On Thu, Apr 19, 2018 at 4:35 PM Alexander Smirnov wrote: > On 04/19/2018 05:26 PM, Jon Nettleton wrote: > > > > On Thu, Apr 19, 2018 at 3:47 PM Henning Schild > > > wrote: > > > > Am Thu, 19 Apr 2018 13:27:36 +0000 > > schrieb Jon Nettleton >>: > > > > > On Thu, Apr 19, 2018 at 12:38 PM Henning Schild > > > > > > wrote: > > > > > > > Am Thu, 19 Apr 2018 09:33:28 +0000 > > > > schrieb Jon Nettleton > >: > > > > > > > > > On Thu, Apr 19, 2018 at 11:19 AM Henning Schild > > > > > > > wrote: > > > > > > > > > > > Am Thu, 19 Apr 2018 00:32:21 -0700 > > > > > > schrieb >: > > > > > > > > > > > > > I am now building a custom debian package from our kernel > > > > > > > sources, the kernel compile goes fine. The deb-pkg is > > > > > > > failing because the number of files passed to xarg is too > > > > > > > long. > > > > > > > > > > > > > > Error message is. > > > > > > > > > > > > > > 2018-04-19 07:11:17 - INFO - | Using default > distribution > > > > > > > of 'unstable' in the changelog > > > > > > > 2018-04-19 07:11:17 - INFO - | Install lsb-release or > set > > > > > > > $KDEB_CHANGELOG_DIST explicitly > > > > > > > 2018-04-19 07:11:17 - INFO - | /usr/bin/xargs: md5sum: > > > > > > > Argument list too long > > > > > > > 2018-04-19 07:11:17 - INFO - | > > > > > > > scripts/package/Makefile:90: recipe for target 'deb-pkg' > > > > > > > failed 2018-04-19 07:11:17 - INFO - | make[1]: *** > > > > > > > [deb-pkg] Error 126 2018-04-19 07:11:17 - INFO - | > > > > > > > Makefile:1347: recipe for target 'deb-pkg' failed > > > > > > > 2018-04-19 07:11:17 - INFO - | make: *** [deb-pkg] > > Error 2 > > > > > > > 2018-04-19 07:11:17 - INFO - | WARNING: exit code 2 > > from a > > > > > > > shell command. > > > > > > > > > > > > > > looks like on large kernel builds the file lists will > need to > > > > > > > be broken up. > > > > > > > > > > > > > > > > > > > I have seen that before. It happens in buildchroot when > using > > > > > > qemu-arm-static binfmt magic. Something in that chain seems > to > > > > > > cause problems for very long argument lists. > > > > > > In my case it was a "make clean" and i removed the files > from > > > > > > outside the buildchroot. But since it now happened again it > is > > > > > > probably something worth looking into. > > > > > > > > > > > > Henning > > > > > > > > > > > > > > > > Oh interesting. I wonder if this has something to do with the > > > > > binfmt support in CentOS vs Debian. I will look into it and > > > > > report back. > > > > > > > > I saw it on Gentoo building in a debian docker container. So i > > guess > > > > the problem might be related to the binfmt wrapping in general, > not > > > > distro specific. > > > > > > > > Henning > > > > > > > > > > > It looks like that was the problem. I just went through the pain > of > > > building qemu 2.9.1 for Centos7...and all the dependencies that > were > > > needed by it. That has fixed the custom kernel build issues. > > > Thanks for all the pointers. > > > > > > I would say for now if anyone asks you can consider Centos 7 a no > > > go. If there is interest I may add a build to Copr for other > users. > > > Fedora 26 and newer should be fine. > > > > Isar calls "random" sudos all over the place. Someone actually > allowing > > this on a productive system surprises me ... to say the least. > > > > My advise it to use a VM or container to run Isar in, and in that > case > > going for Debian9 is easy. One example, used by many of us, is > > https://hub.docker.com/r/kasproject/kas-isar/ > > > > Henning > > > > > > Yes that is what I am using to build with. I can only imagine that the > > newer build of qemu brings in a configuration to the host os that is > > required for things to build properly. > > > > My host OS is Fedora for many years, so I use chroot to work with Debian > environment (for Isar as well): > > $ sudo debootstrap jessie debian8-isar/ http://ftp.debian.org/debian > $ sudo chroot debian8-isar > > This also could be an option. > > Alex > > yes very true, thanks. I am specifically interested in using docker containers to build images so I can bring up a build farm for customers that want to build production images. My main builder is x86_64 however I am looking forward to comparing the performance of that machine vs our "new" ARM64 server boards. Of course I can run run debootstrap within the container first, but since CIP is using Kas I also want to use that infrastructure. -Jon --000000000000260e45056a348f9f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Ap= r 19, 2018 at 4:35 PM Alexander Smirnov <asmirnov@ilbers.de> wrote:
On 04/19/2018 05:26 PM, Jon Nettleton wrote:
>
> On Thu, Apr 19, 2018 at 3:47 PM Henning Schild
> <he= nning.schild@siemens.com <mailto:henning.schild@siemens.com>> wrote:<= br> >
>=C2=A0 =C2=A0 =C2=A0Am Thu, 19 Apr 2018 13:27:36 +0000
>=C2=A0 =C2=A0 =C2=A0schrieb Jon Nettleton <jon@solid-run.com <mailto:jon@solid-run.com>>: >
>=C2=A0 =C2=A0 =C2=A0 > On Thu, Apr 19, 2018 at 12:38 PM Henning Schi= ld
>=C2=A0 =C2=A0 =C2=A0 > <henning.schild@siemens.com <mailto:henning.schild@siemen= s.com>>
>=C2=A0 =C2=A0 =C2=A0wrote:
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > > Am Thu, 19 Apr 2018 09:33:28 +0000
>=C2=A0 =C2=A0 =C2=A0 > > schrieb Jon Nettleton <jon@solid-run.com
>=C2=A0 =C2=A0 =C2=A0<mailto:jon@solid-run.com>>:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > > On Thu, Apr 19, 2018 at 11:19 AM He= nning Schild
>=C2=A0 =C2=A0 =C2=A0 > > > <henning.schild@siemens.com
>=C2=A0 =C2=A0 =C2=A0<mailto:henning.schild@siemens.com>> wrote:
>=C2=A0 =C2=A0 =C2=A0 > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > Am Thu, 19 Apr 2018 00:32:21 -= 0700
>=C2=A0 =C2=A0 =C2=A0 > > > > schrieb <jon@solid-run.com <mailto:jon@solid-run.com>= >:
>=C2=A0 =C2=A0 =C2=A0 > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > > I am now building a custo= m debian package from our kernel
>=C2=A0 =C2=A0 =C2=A0 > > > > > sources, the kernel compi= le goes fine.=C2=A0 The deb-pkg is
>=C2=A0 =C2=A0 =C2=A0 > > > > > failing because the numbe= r of files passed to xarg is too
>=C2=A0 =C2=A0 =C2=A0 > > > > > long.
>=C2=A0 =C2=A0 =C2=A0 > > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > > Error message is.
>=C2=A0 =C2=A0 =C2=A0 > > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > > 2018-04-19 07:11:17 - INF= O=C2=A0 =C2=A0 =C2=A0- | Using default distribution
>=C2=A0 =C2=A0 =C2=A0 > > > > > of 'unstable' in = the changelog
>=C2=A0 =C2=A0 =C2=A0 > > > > > 2018-04-19 07:11:17 - INF= O=C2=A0 =C2=A0 =C2=A0- | Install lsb-release or set
>=C2=A0 =C2=A0 =C2=A0 > > > > > $KDEB_CHANGELOG_DIST expl= icitly
>=C2=A0 =C2=A0 =C2=A0 > > > > > 2018-04-19 07:11:17 - INF= O=C2=A0 =C2=A0 =C2=A0- | /usr/bin/xargs: md5sum:
>=C2=A0 =C2=A0 =C2=A0 > > > > > Argument list too long >=C2=A0 =C2=A0 =C2=A0 > > > > > 2018-04-19 07:11:17 - INF= O=C2=A0 =C2=A0 =C2=A0- |
>=C2=A0 =C2=A0 =C2=A0 > > > > > scripts/package/Makefile:= 90: recipe for target 'deb-pkg'
>=C2=A0 =C2=A0 =C2=A0 > > > > > failed 2018-04-19 07:11:1= 7 - INFO=C2=A0 =C2=A0 =C2=A0- | make[1]: ***
>=C2=A0 =C2=A0 =C2=A0 > > > > > [deb-pkg] Error 126 2018-= 04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- |
>=C2=A0 =C2=A0 =C2=A0 > > > > > Makefile:1347: recipe for= target 'deb-pkg' failed
>=C2=A0 =C2=A0 =C2=A0 > > > > > 2018-04-19 07:11:17 - INF= O=C2=A0 =C2=A0 =C2=A0- | make: *** [deb-pkg]
>=C2=A0 =C2=A0 =C2=A0Error 2
>=C2=A0 =C2=A0 =C2=A0 > > > > > 2018-04-19 07:11:17 - INF= O=C2=A0 =C2=A0 =C2=A0- | WARNING: exit code 2
>=C2=A0 =C2=A0 =C2=A0from a
>=C2=A0 =C2=A0 =C2=A0 > > > > > shell command.
>=C2=A0 =C2=A0 =C2=A0 > > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > > looks like on large kerne= l builds the file lists will need to
>=C2=A0 =C2=A0 =C2=A0 > > > > > be broken up.
>=C2=A0 =C2=A0 =C2=A0 > > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > I have seen that before. It ha= ppens in buildchroot when using
>=C2=A0 =C2=A0 =C2=A0 > > > > qemu-arm-static binfmt magic. = Something in that chain seems to
>=C2=A0 =C2=A0 =C2=A0 > > > > cause problems for very long a= rgument lists.
>=C2=A0 =C2=A0 =C2=A0 > > > > In my case it was a "make= clean" and i removed the files from
>=C2=A0 =C2=A0 =C2=A0 > > > > outside the buildchroot. But s= ince it now happened again it is
>=C2=A0 =C2=A0 =C2=A0 > > > > probably something worth looki= ng into.
>=C2=A0 =C2=A0 =C2=A0 > > > >
>=C2=A0 =C2=A0 =C2=A0 > > > > Henning
>=C2=A0 =C2=A0 =C2=A0 > > > >
>=C2=A0 =C2=A0 =C2=A0 > > >
>=C2=A0 =C2=A0 =C2=A0 > > > Oh interesting.=C2=A0 I wonder if t= his has something to do with the
>=C2=A0 =C2=A0 =C2=A0 > > > binfmt support in CentOS vs Debian.= =C2=A0 I will look into it and
>=C2=A0 =C2=A0 =C2=A0 > > > report back.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > I saw it on Gentoo building in a debian = docker container. So i
>=C2=A0 =C2=A0 =C2=A0guess
>=C2=A0 =C2=A0 =C2=A0 > > the problem might be related to the binf= mt wrapping in general, not
>=C2=A0 =C2=A0 =C2=A0 > > distro specific.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Henning
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > It looks like that was the problem.=C2=A0 I j= ust went through the pain of
>=C2=A0 =C2=A0 =C2=A0 > building qemu 2.9.1 for Centos7...and all the= dependencies that were
>=C2=A0 =C2=A0 =C2=A0 > needed by it.=C2=A0 =C2=A0That has fixed the = custom kernel build issues.
>=C2=A0 =C2=A0 =C2=A0 > Thanks for all the pointers.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > I would say for now if anyone asks you can co= nsider Centos 7 a no
>=C2=A0 =C2=A0 =C2=A0 > go.=C2=A0 If there is interest I may add a bu= ild to Copr for other users.
>=C2=A0 =C2=A0 =C2=A0 > Fedora 26 and newer should be fine.
>
>=C2=A0 =C2=A0 =C2=A0Isar calls "random" sudos all over the pl= ace. Someone actually allowing
>=C2=A0 =C2=A0 =C2=A0this on a productive system surprises me ... to say= the least.
>
>=C2=A0 =C2=A0 =C2=A0My advise it to use a VM or container to run Isar i= n, and in that case
>=C2=A0 =C2=A0 =C2=A0going for Debian9 is easy. One example, used by man= y of us, is
>=C2=A0 =C2=A0 =C2=A0https://hub.docker.com/r/kaspro= ject/kas-isar/
>
>=C2=A0 =C2=A0 =C2=A0Henning
>
>
> Yes that is what I am=C2=A0 using to build with.=C2=A0 I can only imag= ine that the
> newer build of qemu brings in a configuration to the host os that is <= br> > required for things to build properly.
>

My host OS is Fedora for many years, so I use chroot to work with Debian environment (for Isar as well):

$ sudo debootstrap jessie debian8-isar/ http://ftp.debian.org/debian=
$ sudo chroot debian8-isar

This also could be an option.

Alex


yes very true, thanks.=C2=A0 I= am specifically interested in using docker containers to build images so I= can bring up a build farm for customers that want to build production imag= es.=C2=A0 My main builder is x86_64 however I am looking forward to compari= ng the performance of that machine vs our "new" ARM64 server boar= ds.=C2=A0 Of course I can run run debootstrap within the container first, b= ut since CIP is using Kas I also want to use that infrastructure.

-Jon
--000000000000260e45056a348f9f--