From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6546059049526362112 X-Received: by 10.167.133.11 with SMTP id v11mr968302pfn.27.1524125893332; Thu, 19 Apr 2018 01:18:13 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.101.99.205 with SMTP id n13ls1557027pgv.22.gmail; Thu, 19 Apr 2018 01:18:12 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/Qhm2ftXFvLUEALvG4fhFg0PqBJxzqtg2IvvoXbjM3nG926cggkfT+YGm3MgIpPoDR88sR X-Received: by 10.98.171.2 with SMTP id p2mr944403pff.6.1524125892877; Thu, 19 Apr 2018 01:18:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524125892; cv=none; d=google.com; s=arc-20160816; b=XCwYrL4c0wppt5cGdtJpIooQiU5Q8z+VvxB+dwQ+xwKKiX9qnBQl6cVJCxS28SZo3a BD7JfeC4Bf9+YmKn5/pwBcdIgwOAfzP3zmWM2prZfKUJhJ4UdePG0/HwdDKLgKboNs1q 83MFdqd98xqxSecy06i5gBaXZvlvSJq718o86rjYO+f8e86Xsz6QVvL+NBOhtMRWbBrv SFAfYfJgmpDMGTSRfLNvRRdIeb7oY0k4vVEu3q9BEhNQcTWweSviiAtntYIemBOzmYvm 4O+m9O4M5DpSm47kzuGMdei45f98t6KJzSuBmEYQ6eT/YBeFlLU2Sq5mjxlDscIH3ssZ x6Lw== 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=7FE0x6o1RlO1mKVfZhevJIdI1YeQmyTQpYnfgMey2GQ=; b=frj43ZdYiwmSVaDRJzBW2WK6GB+nGR4A/cSHd9xMMIRQHLs0+9uT6s57SvCrbxTDJ3 ldH74kKuZdrBthIQY71F5Z/kRu0CsUBLFJuUb1dtD1lFmkNIm923N/n31CaG5ihpG4lA kjHWsXBrzxpv6oBtfrX7VNcrG97DzNiYA/3C6Y4KxflzToGP+Z6TVdQLvgWlvOSGGVNO 91SrS2grIpnOv7jABKzqVBYN9JtKjgBfnOWXWAkftViYFpE+6kwsLiIf1VblyLDvWP+q taumXBxlER5O29MV4xs36xzqigNNeSVVgxhlU3mM2om/eSoyPAISv7vpShK2e9MKXkQ2 TIvQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@solid-run-com.20150623.gappssmtp.com header.s=20150623 header.b=MDAwyL/G; spf=pass (google.com: domain of jon@solid-run.com designates 2607:f8b0:4001:c06::232 as permitted sender) smtp.mailfrom=jon@solid-run.com Return-Path: Received: from mail-io0-x232.google.com (mail-io0-x232.google.com. [2607:f8b0:4001:c06::232]) by gmr-mx.google.com with ESMTPS id y10si259569pfn.3.2018.04.19.01.18.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Apr 2018 01:18:12 -0700 (PDT) Received-SPF: pass (google.com: domain of jon@solid-run.com designates 2607:f8b0:4001:c06::232 as permitted sender) client-ip=2607:f8b0:4001:c06::232; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@solid-run-com.20150623.gappssmtp.com header.s=20150623 header.b=MDAwyL/G; spf=pass (google.com: domain of jon@solid-run.com designates 2607:f8b0:4001:c06::232 as permitted sender) smtp.mailfrom=jon@solid-run.com Received: by mail-io0-x232.google.com with SMTP id c26-v6so5615229iob.3 for ; Thu, 19 Apr 2018 01:18:12 -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=7FE0x6o1RlO1mKVfZhevJIdI1YeQmyTQpYnfgMey2GQ=; b=MDAwyL/G2e/ez+kKHqGFSRSuRY053njfFbdSYDFJM9uy1CVTv+N9d79X3x2BsZGcHF GYlWajy/NXSq48mN6geAVUCWmBaI9Djb/ACrtbdvipQCw9oAwZKNXTRKc/BKi6LkpAQ1 fkNRL9T3pThKr0LOTrFz20oJNsOHTMskjJ9s7NkBJ6j0rGj+dpqSbKOaxZ7oGtRX4B3O ixrqPOFeM9QvQd1Pxer1EdhfMphATwLUOI0r44MdDQ1DAyjSfj6EXTwh4Kig9zncPNIC zw4xNgAwEs22o3oEx26ryYlLRYgiskYQJYTAuscG7L2y7xUCF2/FYalM5K7ZPaG5IiQr AbMw== 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=7FE0x6o1RlO1mKVfZhevJIdI1YeQmyTQpYnfgMey2GQ=; b=eEmZECgxyx4EoPipBNSlvQzazy3HqKATiKtzMqU0SaILqVS+JYq/RyAAJkirXBjSES uSzmX3CMkoimI410Xc/c96F1yqLvdZw0BuCFv/BLjk71Xcoh7uU8hmuAKiqnD4EcHofG tEE1s5Qp06ylqDfDkFCEzwRCR5ooDUiaLl3n9rwgXV2/dwynkntsL9e1PhdW0udE2z19 rRumEknOkQs9S+S99wSxPjpK3pYnLQT75pk0J0edWHH2NZScn1H1OAEZmpr5ABjJPys9 0DiSl352mr+R5LrsgN07mhDZ4X8ReWkz4lVncPXS40yaRTEiRC8ebWrg5OVkdk6xOw25 MOzQ== X-Gm-Message-State: ALQs6tDmL8HnAKSvBZ8WvahItaDd0d36alqTolPJ9mYrMuMl4o2a+IMO kXviuOGn1SljzF5UXlayEq6C0GpxCmO3/CgxNe7zzQ== X-Received: by 2002:a6b:da18:: with SMTP id x24-v6mr5695485iob.165.1524125892446; Thu, 19 Apr 2018 01:18:12 -0700 (PDT) MIME-Version: 1.0 References: <01699424-086e-5688-d768-a23cbf16c7a7@siemens.com> <0b505160-6736-0550-eee4-dcb53a5dd29e@siemens.com> <0d5631bf-4777-0fc3-c6c7-2410011b4859@siemens.com> In-Reply-To: From: Jon Nettleton Date: Thu, 19 Apr 2018 08:18:01 +0000 Message-ID: Subject: Re: building custom kernel fails To: Jan Kiszka Cc: isar-users Content-Type: multipart/alternative; boundary="00000000000069a231056a2f361d" X-TUID: b8Gnt+XesfFF --00000000000069a231056a2f361d Content-Type: text/plain; charset="UTF-8" On Thu, Apr 19, 2018 at 10:12 AM Jan Kiszka wrote: > On 2018-04-19 10:05, Jon Nettleton wrote: > > On Thu, Apr 19, 2018 at 9:57 AM Jan Kiszka > > wrote: > > > > On 2018-04-19 09:56, Jon Nettleton wrote: > > > On Thu, Apr 19, 2018 at 9:52 AM Jan Kiszka > > > > >> > > wrote: > > > > > > On 2018-04-19 09:47, Jon Nettleton wrote: > > > > > > > > On Thu, Apr 19, 2018 at 9:40 AM Jan Kiszka > > > > > >> > > > > > > >>> > > > wrote: > > > > > > > > On 2018-04-19 09:32, 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. > > As we are also building older kernels with that rules (4.4-cip namely), > I suspect the problem either comes from the config or BSP-specific > changes. Hope, NXP was not touching stuff again they shouldn't change... > > Jan > We have no problems building packages from within a fakeroot build method. This seems to be more of a specific environment problem. I know that CentOS isn't officially supported, but that is my server platform of choice. That is why building from within a debianized container is a great solution moving forward. I notice that the kernel is being built and packaged with the root user? Is there a specific reason for this? Jon --00000000000069a231056a2f361d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Ap= r 19, 2018 at 10:12 AM Jan Kiszka <jan.kiszka@siemens.com> wrote:
On 2018-04-19 10:05, Jon Nettleton wrote:
> On Thu, Apr 19, 2018 at 9:57 AM Jan Kiszka <jan.kiszka@siemens.com
> <mailto:jan.kiszka@siemens.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0On 2018-04-19 09:56, Jon Nettleton wrote:
>=C2=A0 =C2=A0 =C2=A0> On Thu, Apr 19, 2018 at 9:52 AM Jan Kiszka <= ;jan.kiszka@sie= mens.com
>=C2=A0 =C2=A0 =C2=A0<mailto:jan.kiszka@siemens.com>
>=C2=A0 =C2=A0 =C2=A0> <mailto:jan.kiszka@siemens.com <mailto:jan.kiszka@siemens.com&= gt;>>
>=C2=A0 =C2=A0 =C2=A0wrote:
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0On 2018-04-19 09:47, Jon Ne= ttleton wrote:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> On Thu, Apr 19, 2018 a= t 9:40 AM Jan Kiszka
>=C2=A0 =C2=A0 =C2=A0<jan.kiszka@siemens.com <mailto:jan.kiszka@siemens.com>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0<mailto:jan.kiszka@siemens.com <= mailto:jan.kisz= ka@siemens.com>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> <mailto:jan.kiszka@siemens.com=
>=C2=A0 =C2=A0 =C2=A0<mailto:jan.kiszka@siemens.com> <mailto:jan.kiszka@siemens.com >=C2=A0 =C2=A0 =C2=A0<mailto:jan.kiszka@siemens.com>>>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0wrote:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0On = 2018-04-19 09:32, jo= n@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<mailto:jon@solid-run.com <mailto:jon@solid-run.com&g= t;>
>=C2=A0 =C2=A0 =C2=A0<mailto:jon@solid-run.com <mailto:jon@solid-run.com>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0<mailto:jon@solid-run.com <mailto:jon@solid-run.com&g= t;>> wrote:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; I am now building a custom debian package from our kernel
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0sources, the
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; kernel compile goes fine.=C2=A0 The deb-pkg is failing
>=C2=A0 =C2=A0 =C2=A0because the
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0num= ber of
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; files passed to xarg is too long.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ;
>=C2=A0 =C2=A0 =C2=A0>=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>=C2=A0 =C2=A0 =C2=A0>= ;
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | Using default
>=C2=A0 =C2=A0 =C2=A0distribution of
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 'unstable' in the changelog
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | Install lsb-release
>=C2=A0 =C2=A0 =C2=A0or set
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; $KDEB_CHANGELOG_DIST explicitly
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | /usr/bin/xargs: md5sum:=
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Arg= ument list
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; too long
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- |
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0scripts/package/Makefile:90= : recipe
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; for target 'deb-pkg' failed
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | make[1]: *** [deb-pkg]<= br> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Error 126
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | Makefile:1347:
>=C2=A0 =C2=A0 =C2=A0recipe for
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0target
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 'deb-pkg' failed
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | make: *** [deb-pkg]
>=C2=A0 =C2=A0 =C2=A0Error 2
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; 2018-04-19 07:11:17 - INFO=C2=A0 =C2=A0 =C2=A0- | WARNING: exit code
>=C2=A0 =C2=A0 =C2=A02 from
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0a shell
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; command.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ;
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>= ; looks like on large kernel builds the file lists will
>=C2=A0 =C2=A0 =C2=A0need to be
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0bro= ken up.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Whe= re exactly is this argument list passed? What exactly is
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0your setup
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0(ho= st, target distro, kernel version etc.)?
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0BTW= , you can find a working custom kernel build here e.g.:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0
>=C2=A0 =C2=A0 =C2=A0=C2=A0=C2=A0https://github.com/siemens/jailhouse-images/tree/master/recipes= -kernel/linux
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0The= re is an ARM64 version of that as well, just waiting for
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0cross-build
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0sup= port to be available.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Jan=
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> =C2=A0Yes I have used = your recipe as a reference.=C2=A0 It is a 4.9.y
>=C2=A0 =C2=A0 =C2=A0lts kernel
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> with the NXP BSP merge= d for our hardware.
>=C2=A0 =C2=A0 =C2=A0https://www.solid-run.com
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> I am attempting to use= the default make deb-pkg in that LTS
>=C2=A0 =C2=A0 =C2=A0kernel.=C2=A0 I
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> am running this in a k= as-isar container on a CentOS 7 host.=C2=A0 My
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0guess is
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> ulimit my possibly be = getting in the way.=C2=A0 I will do a
>=C2=A0 =C2=A0 =C2=A0minimal kernel
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> config build and then = move up from there.
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Are you using our recipes-k= ernel/linux/linux-custom.inc or
>=C2=A0 =C2=A0 =C2=A0your own
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0rules?
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Jan
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> Correct
>
>=C2=A0 =C2=A0 =C2=A0Err, there was an "or" in my question...<= br> >
>=C2=A0 =C2=A0 =C2=A0If your "correct" applied to option 2, I = would recommend option 1.
>
>=C2=A0 =C2=A0 =C2=A0Jan
>
>
> Sorry was a bit distracted.=C2=A0 I am using your rules, option 1.=C2= =A0

As we are also building older kernels with that rules (4.4-cip namely),
I suspect the problem either comes from the config or BSP-specific
changes. Hope, NXP was not touching stuff again they shouldn't change..= .

Jan=C2=A0
=C2=A0

We have no problems building packages from within a fa= keroot build method.=C2=A0 This seems to be more of a specific environment = problem.=C2=A0 I know that CentOS isn't officially supported, but that = is my server platform of choice.=C2=A0 That is why building from within a d= ebianized container is a great solution moving forward.

I notice that the kernel is being built and packaged with the root us= er?=C2=A0 Is there a specific reason for this?

Jon=
--00000000000069a231056a2f361d--