My interest in this is that I'm stress testing migrating snaps to core 22/snapcraft 7 as part of the update for the Snapcraft 101 course, and when I asked my team for an example of a snap that would be challenging to migrate, one of them immediately suggested chromium, so that's why I'm working on this. So far, the necessary changes were fairly minimal, until this issue, which I don't know what to do with.
Perhaps one should create a core 22 branch where I can submit my changes. In terms of getting more output, with Snapcraft 7, I'm running "snapcraft --verbosity=trace" for tons of output. Anyway, this wl_proxy* stuff is the current bottleneck. On Fri, Aug 19, 2022 at 7:25 AM Nathan Teodosio <1986...@bugs.launchpad.net> wrote: > For a matter of fact, wl_proxy_marshal_flags is declared in wayland- > client-core.h, provided by libwayland-dev, which is specified in the > build-packages of chromium in snapcraft.yaml. As long as it is version > >=1.20, I'd think it should work, but reality shows otherwise. > > I'm trying to build the snap too so I can see full logs, but weirdly > they are much less verbose than what I'm used to (e.g. > > https://launchpadlibrarian.net/618908242/buildlog_snap_ubuntu_jammy_amd64_chromium- > browser-core22_BUILDING.txt.gz > <https://launchpadlibrarian.net/618908242/buildlog_snap_ubuntu_jammy_amd64_chromium-browser-core22_BUILDING.txt.gz>), > and I don't want to believe that would > be caused by a mere switch to core22. > > > P.S. Thanks for your patience with all of this. > > No such thing, it's a pleasure :). This is both useful and a great > chance to better understand snaps. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1986925 > > Title: > [snap] Trying to build chromium snap for core22: pkg-config fails. > > Status in chromium-browser package in Ubuntu: > New > > Bug description: > I checked out the "dev" branch of chromium-browser from launchpad and > did what seemed necessary to update snapcraft.yaml to build with > snapcraft 7 for core22. The only change of any significance was to > change the extension from "gnome-3-38" to the core22-specific "gnome" > extension. I started the build and it ran for quite some time (in a > persistent 22.04 LXD container) until: > > 2022-08-18 09:11:00.869 :: + OUT=out/Release > > 2022-08-18 09:11:00.869 :: + mkdir -p out/Release > > 2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/ > args.gn out/Release/ > 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' > > 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' > > 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig > > 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc > > 2022-08-18 09:11:00.935 :: + cd - > > 2022-08-18 09:11:00.935 :: > /root/snaps/snap-from-source/parts/chromium/build > > 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release > > 2022-08-18 09:11:07.112 :: ERROR at > //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit > code. > > 2022-08-18 09:11:07.112 :: pkgresult = > exec_script(pkg_config_script, args, "value") > 2022-08-18 09:11:07.113 :: ^---------- > > 2022-08-18 09:11:07.113 :: Current dir: > /root/snaps/snap-from-source/parts/chromium/build/out/Release/ > 2022-08-18 09:11:07.113 :: Command: python3 > /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py > -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb > > 2022-08-18 09:11:07.113 :: Returned 1. > > 2022-08-18 09:11:07.113 :: stderr: > > 2022-08-18 09:11:07.113 :: > > 2022-08-18 09:11:07.113 :: Could not run pkg-config. > > 2022-08-18 09:11:07.113 :: > > 2022-08-18 09:11:07.113 :: See > //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called. > 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") { > > 2022-08-18 09:11:07.113 :: ^---------------------- > > 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file > to be included. > 2022-08-18 09:11:07.114 :: > "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan", > 2022-08-18 09:11:07.114 :: > ^----------------------------------------------------------- > 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with > code 1. > Review the scriptlet and make sure it's correct. > > I verified that the pkg-config utility is installed in the container; > I can only suspect that this error is related to switching to the > core22 gnome extension. I am open to suggestions. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions > > -- 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/1986925 Title: [snap] Trying to build chromium snap for core22: pkg-config fails. Status in chromium-browser package in Ubuntu: New Bug description: I checked out the "dev" branch of chromium-browser from launchpad and did what seemed necessary to update snapcraft.yaml to build with snapcraft 7 for core22. The only change of any significance was to change the extension from "gnome-3-38" to the core22-specific "gnome" extension. I started the build and it ran for quite some time (in a persistent 22.04 LXD container) until: 2022-08-18 09:11:00.869 :: + OUT=out/Release 2022-08-18 09:11:00.869 :: + mkdir -p out/Release 2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 09:11:00.935 :: + cd - 2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release 2022-08-18 09:11:07.112 :: ERROR at //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code. 2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script, args, "value") 2022-08-18 09:11:07.113 :: ^---------- 2022-08-18 09:11:07.113 :: Current dir: /root/snaps/snap-from-source/parts/chromium/build/out/Release/ 2022-08-18 09:11:07.113 :: Command: python3 /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb 2022-08-18 09:11:07.113 :: Returned 1. 2022-08-18 09:11:07.113 :: stderr: 2022-08-18 09:11:07.113 :: 2022-08-18 09:11:07.113 :: Could not run pkg-config. 2022-08-18 09:11:07.113 :: 2022-08-18 09:11:07.113 :: See //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called. 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") { 2022-08-18 09:11:07.113 :: ^---------------------- 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be included. 2022-08-18 09:11:07.114 :: "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan", 2022-08-18 09:11:07.114 :: ^----------------------------------------------------------- 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. I verified that the pkg-config utility is installed in the container; I can only suspect that this error is related to switching to the core22 gnome extension. I am open to suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+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
