public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jon Nettleton <jon@solid-run.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: building custom kernel fails
Date: Thu, 19 Apr 2018 09:52:21 +0200	[thread overview]
Message-ID: <0b505160-6736-0550-eee4-dcb53a5dd29e@siemens.com> (raw)
In-Reply-To: <CABdtJHvZNo4+wNPBVpyWxG_VuujTYYdh2nBy_-KS8_Z=ZbxVCQ@mail.gmail.com>

On 2018-04-19 09:47, Jon Nettleton wrote:
> 
> On Thu, Apr 19, 2018 at 9:40 AM Jan Kiszka <jan.kiszka@siemens.com
> <mailto:jan.kiszka@siemens.com>> wrote:
> 
>     On 2018-04-19 09:32, jon@solid-run.com <mailto:jon@solid-run.com> wrote:
>     > 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.
> 
>     Where exactly is this argument list passed? What exactly is your setup
>     (host, target distro, kernel version etc.)?
> 
>     BTW, you can find a working custom kernel build here e.g.:
>     https://github.com/siemens/jailhouse-images/tree/master/recipes-kernel/linux
>     There is an ARM64 version of that as well, just waiting for cross-build
>     support to be available.
> 
>     Jan
> 
> 
>  Yes I have used your recipe as a reference.  It is a 4.9.y lts kernel
> with the NXP BSP merged for our hardware. https://www.solid-run.com
> 
> I am attempting to use the default make deb-pkg in that LTS kernel.  I
> am running this in a kas-isar container on a CentOS 7 host.  My guess is
> ulimit my possibly be getting in the way.  I will do a minimal kernel
> config build and then move up from there.

Are you using our recipes-kernel/linux/linux-custom.inc or your own rules?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-04-19  7:52 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 [this message]
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
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=0b505160-6736-0550-eee4-dcb53a5dd29e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jon@solid-run.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