Arch Linux User Repository

@SunRed; Thanks for the heads-up. Looks like CVE-2022-24765 prevented the system from replicating the change into the AUR repository. Since the .SRCINFO file is generated on-the-fly it did not suffer from the same problem. Sadly this means that the actual change did not end up on the AUR and the generated file did, resulting in a partial upload. I'll fix this in a bit.

@missingSleepDeps; Don't flag out of date when things aren't actually out of date. B5.0.1 is still the latest official/stable versioned release.

Please only update the pkgrel in the PKGBUILD file and generate the .SRCINFO using makepkg --printsrcinfo > .SRCINFO (make yourself an alias) instead of updating it in the .SRCINFO file directly to avoid makepkg building a different/older version than is being displayed on the AUR and AUR helpers always thinking there is a new version available.

getting the same error now as artafinde

Heads up, this fails with the incoming package testing/linux 5.18.0-arch1-1 https://paste.artafinde.me/pleasant-corgi.log

Omar007:

pacman -Q | grep gdb
gdb --version

Both show 11.2-1. Not sure how or why yay (or me?) uses 10.1. It appears it's only this package. But you are correct in that it uses gdb 10.1 for some reason. And it only fails on the host, the client compiles fine. whereis gdb only shows one binary. I'll see if I can reproduce the issue on my laptop or something. Extremely weird.

I ended up figuring out the issue however it was a lazy fix I just used looking-glass-git package which worked I sort of panicked at first and thought something broke for everyone sorry

@Torxed: It looks like you're for some reason building with a custom build environment instead of making a clean build. In this case, it's seems you're building with a 10.1 version of GDB living in your home directory? Please build in an up-to-date Arch environment (and preferably a clean one, e.g. use a chroot or something), otherwise you're on your own.

Used yay, but I doubt that's the issue.

/usr/bin/ld: /usr/local/lib/libbfd.a(plugin.o): in function `try_load_plugin':
/home/anton/builds/gdb-10.1/bfd/plugin.c:274: undefined reference to `dlopen'
/usr/bin/ld: /home/anton/builds/gdb-10.1/bfd/plugin.c:354: undefined reference to `dlclose'
/usr/bin/ld: /home/anton/builds/gdb-10.1/bfd/plugin.c:312: undefined reference to `dlsym'
/usr/bin/ld: /home/anton/builds/gdb-10.1/bfd/plugin.c:274: undefined reference to `dlopen'
/usr/bin/ld: /home/anton/builds/gdb-10.1/bfd/plugin.c:281: undefined reference to `dlerror'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/looking-glass-host.dir/build.make:135: looking-glass-host] Error 1
make[1]: *** [CMakeFiles/Makefile2:248: CMakeFiles/looking-glass-host.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I get this error when running makepkg:

==> Starting build()...
mkdir: cannot create directory ‘client/build’: File exists
==> ERROR: A failure occurred in build().
    Aborting...

Fix:

From 2157d0bc3a3a0ee454ebb81983dd7eda8e460b85 Mon Sep 17 00:00:00 2001
From: lemmarathon <37196124+lemmarathon@users.noreply.github.com>
Date: Fri, 31 Dec 2021 09:27:29 -0800
Subject: [PATCH] Fix "cannot create directory" build error.

---
 PKGBUILD | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PKGBUILD b/PKGBUILD
index 3e2ee84..92f276b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -22,7 +22,7 @@ _lgdir="${pkgbase}-${pkgver}"
 build() {
        cd "${srcdir}/${_lgdir}"
        for b in {client,host,obs}/build; do
-               mkdir "${b}"
+               mkdir -p "${b}"
                pushd "${b}"
                cmake -DCMAKE_INSTALL_PREFIX=/usr ..
                make
-- 
2.34.1

Change source URL to https://looking-glass.io/artifact/stable/source