Arch Linux User Repository

There is something preventing me from building this outside of a chroot. The errors happen when ninja tries to link the executables near the end of the build. If you run into this, build in a chroot:

paru -S snapd-glib --chroot

If you know what's causing this and can suggest a fix, let me know. i've already tried disabling LTO in options and in the meson command with no effect.

Today, I successfully installed snapd-glib package using yay.
I'm happy.

I'm getting the same issue as jimnong

I don't have Paru installed nor do I want to install it.

mammo0 Thanks, your fix worked for me.


cd /tmp

git clone https://aur.archlinux.org/snapd-glib.git

cd snapd-glib

nano PKGBUILD


Edit the line that starts:

git apply ../8aeca34f583174357595f72936bc0960f3c9a2f6.patch

So that it reads:

patch -p1 < ../8aeca34f583174357595f72936bc0960f3c9a2f6.patch

ctrl+o Enter ctrl+x

makepkg -si

It compiled and installed for me

Hello, the command git apply in the prepare() method is not working when you're not in a git directory. See https://stackoverflow.com/a/27283285.

It works with patch -p1 < ../8aeca34f583174357595f72936bc0960f3c9a2f6.patch.

It's seem to me that the patch https://github.com/canonical/snapd-glib/pull/199/commits/d1e9d5d23004456cec1505c4eea668370869086a.patch is not apply with this PKGBUILD I could achieve compiling by using master git where applying the patch was possible. But I don't understand why...

@username227, paru -S snapd-glib --chroot worked like a charm. Thanks alot!

Please run the command in the pinned comment. If you don't have paru installed, first install it from the AUR. Building in a chroot will likely solve the problem since I also got a linker error when i built in the standard way. When I tried to build in a chroot i got a different error, and came here to report it and saw that it had been orphaned so I adopted and fixed myself. But i don't know yet how to fix the linker error. Therefore, build in a chroot following the pinned commands. After you try this, if you still have problems, let me know. thanks.

yay -Syu.
But error is occured.
I don't know what to do. Please help me.

/usr/src/debug/snapd-glib/snapd-glib-9af6ed6d7cce8965e30e4165982cdb21ccb663db/build/../tests/test-qt.cpp:6574:(.text+0x6b95): undefined reference to `QSnapdAlias::name() const'

/usr/bin/ld: /tmp/ccJm9gwp.ltrans12.ltrans.o:/usr/src/debug/snapd-glib/snapd-glib-9af6ed6d7cce8965e30e4165982cdb21ccb663db/build/../tests/test-qt.cpp:6574: more undefined references to `QSnapdAlias::name() const' follow

/usr/bin/ld: tests/test-qt6: protected symbol `_ZNK15QSnapdInterface9slotCountEv' isn't defined
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
[213/213] Generating doc/documentation with a custom command

INFO: Copying file /usr/lib/python3.13/site-packages/gidocgen/templates/basic/SourceCodePro-Semibold.ttf.woff: doc/snapd-glib/SourceCodePro-Semibold.ttf.woff
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...
-> error making: snapd-glib-exit status 4
-> Failed to install the following packages. Manual intervention is required:
snapd-glib - exit status 4

@khalyst0 have you tried building in a chroot?

that error is just the exit error, would need more info from the error in the build to give any assistance.

Got an error today trying to update this package:

error making: snapd-glib-exit status 4

any suggestions?

There is something preventing me from building this outside of a chroot. The errors happen when ninja tries to link the executables near the end of the build. If you run into this, build in a chroot:

paru -S snapd-glib --chroot

If you know what's causing this and can suggest a fix, let me know. i've already tried disabling LTO in options and in the meson command with no effect.