Re: building custom kernel fails

[Jan Kiszka <jan.kiszka@siemens.com>]

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:
> 
>     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>
>     > <mailto: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>>
>     >     > <mailto: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>>
>     <mailto: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. 

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

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