From: Lukasz Majewski <lukma@denx.de>
To: <openembedded-core@lists.openembedded.org>
Subject: Question regarding docker and sumo
Date: Fri, 17 Aug 2018 22:58:11 +0200 [thread overview]
Message-ID: <20180817225811.53b55f2d@jawa> (raw)
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
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: wd@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next reply other threads:[~2018-08-17 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 20:58 Lukasz Majewski [this message]
2018-08-18 1:37 ` Question regarding docker and sumo Andre McCurdy
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=20180817225811.53b55f2d@jawa \
--to=lukma@denx.de \
--cc=openembedded-core@lists.openembedded.org \
/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