public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jon Nettleton <jon@solid-run.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: building custom kernel fails
Date: Thu, 19 Apr 2018 13:27:36 +0000	[thread overview]
Message-ID: <CABdtJHtTtbFdebaBYhLMcuE9cPN-GRZHskpgLubzTeW+bXFFWA@mail.gmail.com> (raw)
In-Reply-To: <20180419123812.7c8f9a0f@mmd1pvb1c.ad001.siemens.net>

[-- Attachment #1: Type: text/plain, Size: 2610 bytes --]

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.

Jon

[-- Attachment #2: Type: text/html, Size: 3673 bytes --]

  reply	other threads:[~2018-04-19 13:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19  7:32 jon
2018-04-19  7:37 ` Claudius Heine
2018-04-19  7:40 ` Jan Kiszka
2018-04-19  7:47   ` Jon Nettleton
2018-04-19  7:52     ` Jan Kiszka
2018-04-19  7:56       ` Jon Nettleton
2018-04-19  7:57         ` Jan Kiszka
2018-04-19  8:05           ` Jon Nettleton
2018-04-19  8:12             ` Jan Kiszka
2018-04-19  8:18               ` Jon Nettleton
2018-04-19 14:01                 ` Jan Kiszka
2018-04-19  9:19 ` Henning Schild
2018-04-19  9:33   ` Jon Nettleton
2018-04-19 10:38     ` Henning Schild
2018-04-19 13:27       ` Jon Nettleton [this message]
2018-04-19 13:47         ` Henning Schild
2018-04-19 14:26           ` Jon Nettleton
2018-04-19 14:35             ` Alexander Smirnov
2018-04-19 14:40               ` Jon Nettleton
2018-04-19 14:57                 ` Jan Kiszka

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=CABdtJHtTtbFdebaBYhLMcuE9cPN-GRZHskpgLubzTeW+bXFFWA@mail.gmail.com \
    --to=jon@solid-run.com \
    --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