Arch Linux User Repository

@Lehmeier: The Wayfire package already uses -Duse_system_wfconfig=enabled, as you can see here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wayfire&id=a70ec100a6a9c186578efd3f729d09157c1c0a69#n20

The issue seems to be with something in your system, as two packages “own” the same file. Could you try removing all Wayfire packages and reinstalling?

Hello! For a few days now, the system has been trying to install wf-config and keeps crashing with an error message:

wf-config 0.9.0-2 0.10.0-1 -0,03 MiB

Gesamtgröße der installierten Pakete: 0,48 MiB Größendifferenz der Aktualisierung: -0,03 MiB

:: Installation fortsetzen? [J/n] (1/1) Schlüssel im Schlüsselbund werden geprüft [-----------------------------------------------------------------------------------------] 100% (1/1) Paket-Integrität wird überprüft [-----------------------------------------------------------------------------------------] 100% (1/1) Paket-Dateien werden geladen [-----------------------------------------------------------------------------------------] 100% (1/1) Auf Dateikonflikte wird geprüft [-----------------------------------------------------------------------------------------] 100% Fehler: Der Vorgang konnte nicht durchgeführt werden (In Konflikt stehende Dateien) wf-config: /usr/include/wayfire/nonstd/safe-list.hpp existiert im Dateisystem (gehört zu wayfire) Fehler sind aufgetreten, keine Pakete wurden aktualisiert. -> error installing: [/home/ralf/.cache/yay/wf-config/wf-config-0.10.0-1-x86_64.pkg.tar.zst] - exit status 1 error installing: [/home/ralf/.cache/yay/wf-config/wf-config-0.10.0-1-x86_64.pkg.tar.zst] - exit status 1

After inquiring at https://github.com/WayfireWM/wf-config/issues/82#issuecomment-3238330914, I received this response: "It sounds like a packaging issue, in that case. If wf-config and wayfire are packaged separately, the wayfire package must be built with -Duse_system_wfconfig=enabled or else it will build wf-config as a subproject and include the files with wayfire installation."

Could something have gone wrong when creating the package?

Thank you in advance.

Best regards, R. Lehmeier

@Strit: Good find, thanks for the heads up! The patch is now included in the build :)

@MooZonkey and @adi1090x: Seems this package requires https://github.com/WayfireWM/wf-config/commit/af1bddc9d7191b9902edcb4c74572eac65577806 for building with GCC 14.

@aperez: Can you include this patch?

Same issue as @MooZonkey

I currently have this error when running makepkg -si . I manually verified all dependencies were installed. At a complete loss.

  [1/10] Compiling C++ object libwf-config.so.0.8.0.p/src_file.cpp.o
FAILED: libwf-config.so.0.8.0.p/src_file.cpp.o 
c++ -Ilibwf-config.so.0.8.0.p -I. -I../wf-config-0.8.0 -Iinclude -I../wf-config-0.8.0/include -I/usr/include/libevdev-1.0 -I/usr/include -I/usr/include/libxml2 -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++17 -Wno-deprecated-declarations -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -fPIC -MD -MQ libwf-config.so.0.8.0.p/src_file.cpp.o -MF libwf-config.so.0.8.0.p/src_file.cpp.o.d -o libwf-config.so.0.8.0.p/src_file.cpp.o -c ../wf-config-0.8.0/src/file.cpp
../wf-config-0.8.0/src/file.cpp: In lambda function:
../wf-config-0.8.0/src/file.cpp:419:25: error: ‘any_of’ is not a member of ‘std’
  419 |             return std::any_of(
      |                         ^~~~~~
[9/10] Compiling C++ object libwf-config.so.0.8.0.p/src_xml.cpp.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...  

Hi, coud you also add cmake to makedepends? If I build both doctest and wf-config in clean chroots, the latter fails as meson cannot find doctest via cmake:

Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency doctest found: NO (tried pkgconfig)

doctest should be listed as a make dependency. Build fails without it

@librewish: GLM is only needed at build time, if you check which libraries libwf-config.so needs at run time... it does not appear listed:

% readelf -d pkg/wf-config/usr/lib/libwf-config.so.0.5.0|grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libevdev.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libxml2.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
%

Using nm -D on the library also does not show any unresolved symbols from GLM.

@aperez add glm as dep

In addition to make dep