Package Details: looking-glass-host 2:B6-9

Git Clone URL: https://aur.archlinux.org/looking-glass.git (read-only, click to copy)
Package Base: looking-glass
Description: Linux host application for pushing frame data to the LookingGlass IVSHMEM device
Upstream URL: https://looking-glass.io/
Licenses: GPL2
Submitter: Omar007
Maintainer: Omar007
Last Packager: Omar007
Votes: 37
Popularity: 0.64
First Submitted: 2017-12-22 16:49 (UTC)
Last Updated: 2024-08-07 11:00 (UTC)

Latest Comments

1 2 3 4 5 6 .. 10 Next › Last »

Omar007 commented on 2024-08-14 12:22 (UTC)

@tannisroot: it does not. You need to properly configure your system/chroot. Please see https://wiki.archlinux.org/title/Arch_User_Repository, specifically section 2.1

tannisroot commented on 2024-08-14 08:45 (UTC)

The package should have pkgconfig as a make dependency, it fails to compile otherwise

CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:707 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPkgConfig.cmake:873 (_pkg_check_modules_internal)
  audiodevs/PipeWire/CMakeLists.txt:5 (pkg_check_modules)

Jogging5055 commented on 2024-08-08 03:45 (UTC)

It looks like it had been updated, so I tried it again and was able to build it. Thank you!

Jogging5055 commented on 2024-08-06 16:28 (UTC)

I'm experiencing the same error as Lili1228.

cparish commented on 2024-08-05 16:06 (UTC)

I'm also having the same build issue as Lili1228 from a fully updated and clean build env. I don't immediately see anything wrong with the sources, but I know in the past GCC struggled with maybe-uninitialized false positives after unused paths were optimized out.

Omar007 commented on 2024-07-30 12:07 (UTC) (edited on 2024-07-30 12:19 (UTC) by Omar007)

A fully updated clean chroot? Before being pushed to the AUR this PKGBUILD has gone through 2 builds; one updated clean chroot on a native Arch Linux system as well as an Arch Linux container based build, of which neither failed 🤔

The message in @Lili1228's message seems to suggest the old hacky work-around I had in the PKGBUILD would still be needed but based on the above, it shouldn't be.

@Algebro's problem is something completely different and has nothing to do with the PKGBUILD. Idk what's going on there.

Kalinda commented on 2024-07-30 11:35 (UTC)

Am getting the same error as Lili1228 when I try to build. Doing it in a chroot.

Lili1228 commented on 2024-07-30 09:18 (UTC)

Doesn't build for me:

In file included from /usr/lib/glib-2.0/include/glibconfig.h:9,
                 from /usr/include/glib-2.0/glib/gtypes.h:34,
                 from /usr/include/glib-2.0/glib/galloca.h:34,
                 from /usr/include/glib-2.0/glib.h:32,
                 from /usr/include/glib-2.0/gobject/gbinding.h:30,
                 from /usr/include/glib-2.0/glib-object.h:24,
                 from /usr/include/glib-2.0/gio/gioenums.h:30,
                 from /usr/include/glib-2.0/gio/giotypes.h:30,
                 from /usr/include/glib-2.0/gio/gio.h:28,
                 from /home/lili/.cache/yay/looking-glass/src/looking-glass-B6/host/platform/Linux/capture/pipewire/src/portal.c:27:
In function ‘glib_autoptr_clear_GVariant’,
    inlined from ‘glib_autoptr_cleanup_GVariant’ at /usr/include/glib-2.0/glib/glib-autocleanups.h:96:1,
    inlined from ‘portal_createScreenCastSession’ at /home/lili/.cache/yay/looking-glass/src/looking-glass-B6/host/platform/Linux/capture/pipewire/src/portal.c:201:23:
/usr/include/glib-2.0/glib/glib-autocleanups.h:96:1: error: ‘response’ may be used uninitialized [-Werror=maybe-uninitialized]
   96 | G_DEFINE_AUTOPTR_CLEANUP_FUNC(GVariant, g_variant_unref)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors

VoodaGod commented on 2024-07-30 06:28 (UTC)

@algebro the patch now got added to tha PKGBUILD, see if you can build now

algebro commented on 2024-07-28 16:56 (UTC)

@VoodaGod thanks, I tried this patch but I'm getting the following error with makepkg:

ld.lld: error: target emulation unknown: -m or at least one .o file required
ld.lld: error: target emulation unknown: -m or at least one .o file required
ld.lld: error: target emulation unknown: -m or at least one .o file required

Any idea what's going on there?

1 2 3 4 5 6 .. 10 Next › Last »