From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: openembedded-devel@lists.openembedded.org
Cc: "Maksim Sisov" <msisov@igalia.com>,
"Raphael Kubo da Costa" <raphael.kubo.da.costa@intel.com>,
"Denis Carikli" <denis@eukrea.com>,
"Eric Bénard" <eric@eukrea.com>, "Søren Andersen" <san@skov.dk>
Subject: [meta-browser] host leaking wayland-scanner?
Date: Wed, 26 Jun 2019 14:29:11 +0200 [thread overview]
Message-ID: <6ry31owmw8.fsf@pengutronix.de> (raw)
Hi developers of meta-browser,
while building meta-browser's latest chromium-ozone-wayland recipe (my
meta-browser's current state is [1], integrated into a customer's thud
based Yocto-BSP) I faced the following problem (excerpt from log.do_com-
pile)
[9109/37430] python ../../third_party/wayland/wayland_scanner_wrapper.py third_party/wayland-protocols/src/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml --src-root ../../ --root-gen-dir gen --cmd /usr/bin/wayland-scanner
FAILED: gen/third_party/wayland-protocols/src/unstable/linux-dmabuf/linux-dmabuf-unstable-v1-protocol.c gen/third_party/wayland-protocols/src/unstable/linux-dmabuf/linux-dmabuf-unstable-v1-client-protocol.h gen/third_party/wayland-protocols/src/unstable/linux-dmabuf/linux-dmabuf-unstable-v1-server-protocol.h
python ../../third_party/wayland/wayland_scanner_wrapper.py third_party/wayland-protocols/src/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml --src-root ../../ --root-gen-dir gen --cmd /usr/bin/wayland-scanner
Traceback (most recent call last):
File "../../third_party/wayland/wayland_scanner_wrapper.py", line 48, in <module>
main(sys.argv)
File "../../third_party/wayland/wayland_scanner_wrapper.py", line 40, in main
generate_code(cmd, "code", protocol_path, out_base_name + "-protocol.c")
File "../../third_party/wayland/wayland_scanner_wrapper.py", line 18, in generate_code
ret = subprocess.call([wayland_scanner_cmd, code_type, path_in, path_out])
File "<UNDISCLOSED_PATH>/build/YOCTO.BSP/tmp/work/cortexa9hf-neon-pmc-linux-gnueabi/chromium-ozone-wayland/75.0.3770.100-r0/recipe-sysroot-native/usr/lib/python2.7/subprocess.py", line 172, in call
return Popen(*popenargs, **kwargs).wait()
File "<UNDISCLOSED_PATH>/build/YOCTO.BSP/tmp/work/cortexa9hf-neon-pmc-linux-gnueabi/chromium-ozone-wayland/75.0.3770.100-r0/recipe-sysroot-native/usr/lib/python2.7/subprocess.py", line 394, in __init__
errread, errwrite)
File "<UNDISCLOSED_PATH>/build/YOCTO.BSP/tmp/work/cortexa9hf-neon-pmc-linux-gnueabi/chromium-ozone-wayland/75.0.3770.100-r0/recipe-sysroot-native/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
which seems to come from my build host not providing '/usr/bin/wayland-
scanner' and which suggests that we have a host tool leakage here. This
all originally results from Chromium's commit [2], particularly [3].
Unfortunately up to now I am not familiar with Google's build tool 'GN'
(see [4]), so I can't present a solution straightaway. But I would like
to start working on a patch now, hence my questions are:
- did anyone notice the same issue?
- is my analysis correct that [3] has to be patched somehow and the
recipe [5] lacks a dependency on wayland-native?
Best regards
Ulrich
P.S.: Sending this message a second time as I have not been subscribed
to the oe-devel list before so that the original mail got rejected.
[1] e0d1e299d691 ("chromium: fix "pure virtual method called" problem.")
[2] https://chromium.googlesource.com/chromium/src/+/a64f758399d26a1c80ab0d3dfecee3abf0714305
a64f758399d2 ("Run wayland-scanner as part of build")
[3] https://chromium.googlesource.com/chromium/src/+/a64f758399d26a1c80ab0d3dfecee3abf0714305/third_party/wayland/features.gni#12
[4] https://gn.googlesource.com/gn/
[5] https://github.com/OSSystems/meta-browser/blob/master/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.100.bb
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next reply other threads:[~2019-06-26 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 12:29 Ulrich Ölmann [this message]
[not found] ` <2e2b5dcd2a5c204a1cd2b7aa7c462091@igalia.com>
2019-06-26 13:05 ` [meta-browser] host leaking wayland-scanner? Ulrich Ölmann
2019-06-26 13:29 ` Ulrich Ölmann
2019-06-26 17:53 ` Otavio Salvador
2019-06-26 23:23 ` [meta-browser][PATCH] README: update list of maintainers Ulrich Ölmann
2019-06-27 15:56 ` Ulrich Ölmann
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=6ry31owmw8.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=denis@eukrea.com \
--cc=eric@eukrea.com \
--cc=msisov@igalia.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raphael.kubo.da.costa@intel.com \
--cc=san@skov.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.