Question regarding docker and sumo

Dear All,

I do port yocto/OE from 2.3 to 2.5.1

For packagegroups-foo-common I do see following error

cd <workdir>/packagegroup-foo-common/1.0-r0/sstate-build-package/

as expected, there are needed directories: package packages-split pkgdata

The problem is in sstate_create_package () at
poky/meta/classes/sstate.bbclass

To be precise in:
tar: tar -czf temporary.tgz.XXXXXXX package packages-split pkgdata

tar (child): gzip: Cannot exec: Invalid argument tar (child): Error is not recoverable: exiting now

Tar version tar (GNU tar) 1.28 (the same for both versions on host). Also 'env' command shows 'unlimited' size for pipes.

ls -alh <install>/poky/build-lwn/tmp/hosttools and there is a link tar -> /bin/tar

The sumo runs inside docker container (with recommended ubuntu). The only change is from pyro to sumo.

To be even more strange - the sumo version of BSP builds correctly when run natively on Debian 9

The problem seems to be with sumo and docker.

| rt_sigprocmask(SIG_SETMASK, [], NULL, 8) =
0 | write(4, "packages-split/packagegroup-lwn-"..., 10240) = -1 EPIPE (Broken pipe) | --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=15063, si_uid=1000} --- | +++ killed by SIGPIPE
+++

Any idea on how to solve (or debug) this issue further? Apparently something is closing the pipe between tar and gzip...

Thanks in advance for any hints :-)

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]

It looks like tar tries to run gzip but the exec call returns "Invalid argument". According to the execve manpage, that means:

EINVAL The new process image file has the appropriate permission and
has a recognized executable binary format, but the system does not support execution of a file with this format.

So, first find which gzip binary tar will use (ie check PATH) and then try to figure out why that gzip binary can't be executed.