** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
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
Ok, thanks.
On Fri, Aug 19, 2022 at 8:10 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> > Perhaps one should create a core 22 branch where I can submit my
> changes.
>
> I think that is only possible with a team. See if you can push to
> https://code.launchpad.net/~chromium-core22/+git/
> Perhaps one should create a core 22 branch where I can submit my
changes.
I think that is only possible with a team. See if you can push to
https://code.launchpad.net/~chromium-core22/+git/chromium-core22. If
yes, just force push your current work to it.
--
You received this bug notification b
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
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 sn
Last comment for the day ... from what little I've seen, it seems like it
might require defining a lengthy list of packages relative to 22.04 to
migrate this snap to 22.04. Or maybe I'm misreading it. In any event, I'd
still like to make this happen.
On Thu, Aug 18, 2022 at 3:56 PM Robert Day
wro
Actually, another part of my grep search produced the following, which
seems to suggest that an older version of libwayland-client0 is being used:
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
https://snapshot.debian.org/archive/debian/20220331T153654Z
A comprehensive grep includes the lines:
parts/launcher/state/build: - libwayland-client0=1.20.0-1
parts/va-drivers/state/build: - libwayland-client0=1.20.0-1
parts/pipewire/state/build: - libwayland-client0=1.20.0-1
parts/chromium-build/state/build: - libwayland-client0=1.20.0-1
parts/manpage
What is libwayland-client0 version in your logs? Focal has 1.18.0, but
wayland-1.21.0/debian/libwayland-client0.symbols:
wl_proxy_marshal_flags@Base 1.20.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
h
This appears to describe precisely this issue:
https://github.com/libsdl-org/SDL/pull/5092
On Thu, Aug 18, 2022 at 1:06 PM Robert Day
wrote:
> Yup, same errors ... lots of "wl "and "marshal" undefined references.
> Here's just a small sample:
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-
Yup, same errors ... lots of "wl "and "marshal" undefined references.
Here's just a small sample:
2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.646 :: callback =
wl_proxy_marshal
That's what I did, but that's also when I got the errors I included in my
previous comment. I'm rebuilding just to make sure those errors are
reproducible.
On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> > but that appears to be because this newer gnome does
> but that appears to be because this newer gnome does not supply such
an executable; there is no "pkg-config" under
/snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
under gnome-3-38.
Oh, so this time pkg-config in build-packages could solve it? Probably
you will have to remo
Just deleting that line seemed to allow the build to progress further,
but now I have a slew of errors; I'll post a snippet here, then must run
off but will be back in a bit:
2022-08-18 14:42:14.617 :: In file included from
../../third_party/angle/src/gpu_info_util/SystemInfo_vulkan.cpp:10:
I made that change, it still failed:
2022-08-18 14:31:54.099 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 14:31:54.099 :: Co
Yes, you will need to update build/args.gn where there's a hardcoded
path to the pkg-config binary (https://git.launchpad.net/~chromium-
team/chromium-browser/+git/snap-from-
source/tree/build/args.gn?h=stable#n39).
--
You received this bug notification because you are a member of Desktop
Package
OK, I'm trying that now, but I would be astonished if that was the solution
as pkg-config is already installed, either because I installed it manually
at some point, or maybe it was installed by an earlier snap, who knows? But
it's definitely there so adding it to "build-packages" should make no
di
Hang on, look at that hard-coded directory name: "/snap/gnome-3-38-2004".
Since the gnome extension under core 22 is named just "gnome", any
hardcoded names to the old extension should fail.
On Thu, Aug 18, 2022 at 10:15 AM Robert Day
wrote:
> Same result:
>
> 2022-08-18 14:13:31.315 :: + OUT=ou
Same result:
2022-08-18 14:13:31.315 :: + OUT=out/Release
2022-08-18 14:13:31.316 :: + mkdir -p out/Release
2022-08-18 14:13:31.335 :: + cp /root/snaps/snap-from-source/stage/build/
args.gn out/Release/
2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
2022-08-18 14:13:31.367 :: + '[' amd64 =
Thanks for the bug report, Robert.
My first attempt would be adding a pkg-config line to the build-packages
of chromium. Does it make sense to you? If yes, could you please try
that?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromi
Let me know if there's anything you want me to test; I have the
container sitting here, ready for further experimentation.
--
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
** Summary changed:
- Trying to build chromium snap for core22: pkg-config fails.
+ [snap] Trying to build chromium snap for core22: pkg-config fails.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification becaus
22 matches
Mail list logo