From: Jon Nettleton <jon@solid-run.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: building custom kernel fails
Date: Thu, 19 Apr 2018 08:05:20 +0000 [thread overview]
Message-ID: <CABdtJHtz5fafdYc0EDc8-Ft1HYP+zPmqsFQNAWoTf6-YG-tNJw@mail.gmail.com> (raw)
In-Reply-To: <0d5631bf-4777-0fc3-c6c7-2410011b4859@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 3365 bytes --]
On Thu, Apr 19, 2018 at 9:57 AM Jan Kiszka <jan.kiszka@siemens.com> wrote:
> On 2018-04-19 09:56, Jon Nettleton wrote:
> > On Thu, Apr 19, 2018 at 9:52 AM Jan Kiszka <jan.kiszka@siemens.com
> > <mailto:jan.kiszka@siemens.com>> wrote:
> >
> > 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>
> > > <mailto: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> <mailto: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
> >
> >
> > Correct
>
> Err, there was an "or" in my question...
>
> If your "correct" applied to option 2, I would recommend option 1.
>
> Jan
>
Sorry was a bit distracted. I am using your rules, option 1.
[-- Attachment #2: Type: text/html, Size: 5510 bytes --]
next prev parent reply other threads:[~2018-04-19 8:05 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 [this message]
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=CABdtJHtz5fafdYc0EDc8-Ft1HYP+zPmqsFQNAWoTf6-YG-tNJw@mail.gmail.com \
--to=jon@solid-run.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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