mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Thomas Pfahl <tpf@thorsis.com>
Subject: [ptxdist] kernel compile fail with icecc, IKCONFIG set, and kernel v5.0 or later
Date: Tue, 20 Aug 2019 16:23:47 +0200	[thread overview]
Message-ID: <2123970.gCTCJ976mJ@ada> (raw)

Hei hei,

while upgrading different BSPs to kernel v5.2.x I came accross a special build 
error. Affected is the kernel.compile stage. This happens with different 
ptxdist versions (tested with 2018.05.0, 2019.01.0, 2019.07.0, 2019.08.0) and 
at least with kernel v5.1 and v5.2 (IIRC kernels at least up to v4.19 were not 
affected) and CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC set (as in DistroKit 
master). 

We use icecc here, my host system is still Debian GNU/Linux 9 (stretch) with 
icecc version 1.0.1. If one of those three things is not present, this build 
error does not occur: kernel, icecc, that config option. I could reproduce 
this with a recent DistroKit BSP and kernels v5.1 and v5.2. Like this:

* checkout recent distrokit
* select platform v7a
* activate icecc (ptxdist setup)
* `ptxdist compile kernel`

At least the first build run fails, later runs might succeed at random. Output 
is like this:


----------------------
target: kernel.compile
----------------------

make[1]: Entering directory '/home/adahl/Work/bsp/isNet_Lite_phoenix-contact/
platform-pc/build-target/linux-5.2.9'
  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  CHK     include/generated/compile.h
  CC      kernel/configs.o
{standard input}: Assembler messages:
{standard input}:136: Error: file not found: kernel/config_data.gz
ICECC[21465] 16:13:52: Compiled on 192.168.10.72
scripts/Makefile.build:278: recipe for target 'kernel/configs.o' failed
make[2]: *** [kernel/configs.o] Error 1
Makefile:1073: recipe for target 'kernel' failed
make[1]: *** [kernel] Error 2


Or this (with `ptxdist -q go`):


{standard input}: Assembler messages:
{standard input}:136: Error: file not found: kernel/config_data.gz
ICECC[27588] 16:19:30: Compiled on 192.168.10.70
make[2]: *** [kernel/configs.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [kernel] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [/home/adahl/Work/bsp/isNet_Lite_phoenix-contact/platform-pc/state/
kernel.compile] Error 2
make: *** Waiting for unfinished jobs....


The remote build node which fails is not always the same. To build this kernel 
make target 'gzip' is needed, which according to my colleague is installed on 
those build nodes failing.

Build succeeds if I turn off icecc _or_ deactivate that kernel config option 
_or_ go back to v4.19. Currently I'm opting for second, but I'm not amused.

Any help and hints appreciated!

Greets
Alex


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2019-08-20 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 14:23 Alexander Dahl [this message]
2019-08-21  5:40 ` Michael Olbrich
2019-08-21  7:36   ` Robert Schwebel

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=2123970.gCTCJ976mJ@ada \
    --to=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    --cc=tpf@thorsis.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