Package Details: lavalauncher 1.7.1-1

Git Clone URL: https://aur.archlinux.org/lavalauncher.git (read-only, click to copy)
Package Base: lavalauncher
Description: A simple launcher panel for Wayland
Upstream URL: https://git.sr.ht/~leon_plickat/lavalauncher
Licenses: GPL3
Conflicts: lavalauncher-git
Provides: lavalauncher
Submitter: leonplickat
Maintainer: leonplickat
Last Packager: leonplickat
Votes: 3
Popularity: 0.88
First Submitted: 2020-01-11 23:37
Last Updated: 2020-05-15 12:23

Latest Comments

PedroHLC commented on 2020-05-15 12:35

:smile: both worked now.

Not using AUR helpers, just pacstrap ++ systemd-nspawn ++ makepkg -scC --sign --noconfirm

leonplickat commented on 2020-05-15 12:25

I also just backported the fix for the building issue.

leonplickat commented on 2020-05-15 12:11

Fixed the issue preventing lavalauncher-git from building in master.

Are you using an AUR helper? Because I got curious and just tried it with one (trizen) and could now actually reproduce the build error for lavalauncher. However when building manually with makepkg the build succeeds.

PedroHLC commented on 2020-05-15 11:44

As I said "clean chroot", so it's a container with just "base-devel" that was created only for this building, the only thing I changed is "-j 20", but this doesn't look like a race condition.

Don't worry, I'll wait the release, I was just asked to add this to my repo. (lavalauncher-git has a warning in src/parser.c:407:9 and all warnings being treated as errors)

leonplickat commented on 2020-05-15 07:45

Hmm... I can not reproduce this on both of my computers. Have you messed with the compiler defaults? Because while there definitely is an issue with the code (the *_listener structs in input.h should be extern), this should not cause a build error. I have fixed that issue on git master, but since I am already quite a few commits into working on the next release, I won't bother back porting this unless absolutely necessary.

Alternatively, you could also try the lavalauncher-git package.

PedroHLC commented on 2020-05-14 23:58

Failing to build in a clean chroot:

[24/24] Linking target lavalauncher
FAILED: lavalauncher 
cc  -o lavalauncher 'lavalauncher@exe/src_lavalauncher.c.o' 'lavalauncher@exe/src_config.c.o' 'lavalauncher@exe/src_draw.c.o' 'lavalauncher@exe/src_buffer.c.o' 'lavalauncher@exe/src_command.c.o' 'lavalauncher@exe/src_input.c.o' 'lavalauncher@exe/src_layersurface.c.o' 'lavalauncher@exe/src_seat.c.o' 'lavalauncher@exe/src_output.c.o' 'lavalauncher@exe/src_registry.c.o' 'lavalauncher@exe/src_cursor.c.o' 'lavalauncher@exe/src_button.c.o' -Wl,--as-needed -Wl,--no-undefined -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--start-group protocol/liblavalauncher_protocols.a /usr/lib/libwayland-client.so /usr/lib/libwayland-cursor.so /usr/lib/libcairo.so -lrt -Wl,--end-group '-Wl,-rpath,$ORIGIN/protocol' -Wl,-rpath-link,/home/main-builder/pkgwork/src/lavalauncher/build/protocol
/usr/sbin/ld: lavalauncher@exe/src_seat.c.o:/home/main-builder/pkgwork/src/lavalauncher/build/../src/input.h:24: multiple definition of `pointer_listener'; lavalauncher@exe/src_input.c.o:/home/main-builder/pkgwork/src/lavalauncher/build/../src/input.c:141: first defined here
/usr/sbin/ld: lavalauncher@exe/src_seat.c.o:/home/main-builder/pkgwork/src/lavalauncher/build/../src/input.h:23: multiple definition of `touch_listener'; lavalauncher@exe/src_input.c.o:/home/main-builder/pkgwork/src/lavalauncher/build/../src/input.c:232: first defined here
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...

leonplickat commented on 2020-02-17 21:51

Ah yes... Since I am the developer, I always have the latest dev-build installed, so I kinda forgot about this AUR package, sorry. Some time ago I switched from make to meson, which broke this package. I corrected that and bumped the package to version 1.6, which has many improvements but also some breaking changes.

simona commented on 2020-02-17 20:10

patch bug?