This upstream bug seems relevant:
https://bugs.chromium.org/p/chromium/issues/detail?id=1340181

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1987137

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 ::         callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::                    ^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 ::         registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::                    ^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 ::         id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 20:15:05.810 ::              ^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 ::         id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,

  and lots more of the same; it seems pretty clear that the relevant
  wayland library is simply not new enough, and I don't know what to
  add/modify to add core22 support to the mix, so I am open to
  suggestions.

  I do notice the file
  parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
  which contains package version manifests for various distros, but not
  Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
  that's just a guess.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to