From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [85.220.165.71]) by mail.openembedded.org (Postfix) with ESMTP id 55F9260111 for ; Wed, 26 Jun 2019 12:29:12 +0000 (UTC) Received: from dude.hi.pengutronix.de ([2001:67c:670:100:1d::7]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hg733-0004xD-3w; Wed, 26 Jun 2019 14:29:13 +0200 Received: from uol by dude.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1hg731-0001En-6h; Wed, 26 Jun 2019 14:29:11 +0200 User-agent: mu4e 1.1.0; emacs 26.1 From: Ulrich =?utf-8?Q?=C3=96lmann?= To: openembedded-devel@lists.openembedded.org Date: Wed, 26 Jun 2019 14:29:11 +0200 Message-ID: <6ry31owmw8.fsf@pengutronix.de> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::7 X-SA-Exim-Mail-From: uol@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: openembedded-devel@lists.openembedded.org Cc: Maksim Sisov , Raphael Kubo da Costa , Denis Carikli , Eric =?utf-8?Q?B=C3=A9nard?= , =?utf-8?Q?S=C3=B8ren?= Andersen Subject: [meta-browser] host leaking wayland-scanner? X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2019 12:29:12 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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-unstab= le-v1.xml --src-root ../../ --root-gen-dir gen --cmd /usr/bin/wayland-scann= er FAILED: gen/third_party/wayland-protocols/src/unstable/linux-dmabuf/linux= -dmabuf-unstable-v1-protocol.c gen/third_party/wayland-protocols/src/unstab= le/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/w= ayland-protocols/src/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml --s= rc-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, i= n main(sys.argv) File "../../third_party/wayland/wayland_scanner_wrapper.py", line 40, i= n main generate_code(cmd, "code", protocol_path, out_base_name + "-protocol.= c") File "../../third_party/wayland/wayland_scanner_wrapper.py", line 18, i= n generate_code ret =3D subprocess.call([wayland_scanner_cmd, code_type, path_in, pat= h_out]) File "/build/YOCTO.BSP/tmp/work/cortexa9hf-neon-pmc-l= inux-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 "/build/YOCTO.BSP/tmp/work/cortexa9hf-neon-pmc-l= inux-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 "/build/YOCTO.BSP/tmp/work/cortexa9hf-neon-pmc-l= inux-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/+/a64f758399d26a1c80ab0d= 3dfecee3abf0714305 a64f758399d2 ("Run wayland-scanner as part of build") [3] https://chromium.googlesource.com/chromium/src/+/a64f758399d26a1c80ab0d= 3dfecee3abf0714305/third_party/wayland/features.gni#12 [4] https://gn.googlesource.com/gn/ [5] https://github.com/OSSystems/meta-browser/blob/master/recipes-browser/c= hromium/chromium-ozone-wayland_75.0.3770.100.bb --=20 Pengutronix e.K. | Ulrich =C3=96lmann = | 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 |