Am Thu, 19 Apr 2018 13:27:36 +0000
schrieb Jon Nettleton <jon@solid-run.com>:

> On Thu, Apr 19, 2018 at 12:38 PM Henning Schild
> <henning.schild@siemens.com> wrote:
>
> > Am Thu, 19 Apr 2018 09:33:28 +0000
> > schrieb Jon Nettleton <jon@solid-run.com>:
> > 
> > > On Thu, Apr 19, 2018 at 11:19 AM Henning Schild
> > > <henning.schild@siemens.com> wrote:
> > > 
> > > > Am Thu, 19 Apr 2018 00:32:21 -0700
> > > > schrieb <jon@solid-run.com>:
> > > > 
> > > > > 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