i'm having the same EXACT issue as @JohnWeak, i don't know what to do to make it build. same errors, same env variables in said errors, i don't know what they mean by 'full cleanup' so i'm just stuck and can't build it.
EDIT: had to manually install sharp's dependencies
it builds fine on my system and in a clean chroot with libfmt 12 from official repos installed
getting long errors in build(), posted it to a pastebin: https://0x0.st/PQCf.txt
the error line ignoring all the spew:
warning: openssl-sys@0.9.111: gcc: error while loading shared libraries: libfmt.so.11: cannot open shared object file: No such file or directory
error: failed to run custom build command for `openssl-sys v0.9.111
manually installing libfmt at version 11.2 allowed the package to work for me, I posted fmt11 to the aur if you'd like to use that as a make dependency
what are you using to try and install it? what is LocalFileSigLevel set to in your pacman.conf? it's unsigned and doesnt need to be since you build it locally.
error: '/home/xxx/.cache/paru/clone/deadlock-modmanager/deadlock-modmanager-0.14.1-1-x86_64.pkg.tar.zst': package missing required signature
@yobson something was wrong with my npm environment, I did a full cleanup and it built successfully
it builds in a clean chroot, there's something wrong with your environment. unsure if it's related but i notice you're getting warnings about your env from npm. i don't get any such warnings in a clean chroot or my systems own regular environment. @JohnWeak
==> Starting prepare()...
Scope: all 25 workspace projects
../.. | +1986 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
../.. | Progress: resolved 1986, reused 1964, downloaded 0, added 1986, done
../../node_modules/.pnpm/sharp@0.34.5/node_modules/sharp: Running install script, failed in 179ms
.../sharp@0.34.5/node_modules/sharp install$ node install/check.js || npm run build
│ npm warn Unknown env config "npm-globalconfig". This will stop working in the next major version of npm.
│ npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
│ npm warn Unknown env config "_jsr-registry". This will stop working in the next major version of npm.
│ npm warn Unknown env config "catalog". This will stop working in the next major version of npm.
│ > sharp@0.34.5 build
│ > node install/build.js
│ sharp: Attempting to build from source via node-gyp
│ sharp: See https://sharp.pixelplumbing.com/install#building-from-source
│ sharp: Found node-addon-api
│ sharp: Please add node-gyp to your dependencies
└─ Failed in 180ms at /home/john/.cache/yay/deadlock-modmanager/src/deadlock-modmanager/node_modules/.pnpm/sharp@0.34.5/node_modules/sharp
ELIFECYCLE Command failed with exit code 1.
==> ERROR: A failure occurred in prepare().
Aborting...
-> error making: deadlock-modmanager-exit status 4
-> Failed to install the following packages. Manual intervention is required:
deadlock-modmanager - exit status 4
missing dependency: gst-plugins-good
without it, the application starts but is not interactable. corresponding terminal output:
GStreamer element autoaudiosink not found. Please install it
(WebKitWebProcess:36051): GLib-GObject-CRITICAL **: 00:40:01.345: invalid (NULL) pointer instance
(WebKitWebProcess:36051): GLib-GObject-CRITICAL **: 00:40:01.345: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
after installing gst-plugins-good it works fine :)
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
Hello,
You can remove the
options=(!lto)from this PKGBUILD by settingexport CFLAGS+=" -ffat-lto-objects"&export CXXFLAGS+= -ffat-lto-objects. This is something that has to be done with Rust packages, but for some reason, is missing from the Wiki pagage on Rust Package Guidelines. Maybe I'll make an edit…Another thing is, you don't need to specify
-C linker-args=-fuse-ld=lldanymore. Ever since Rust 1.90, LLD is the default linker for Rust on Linux.I built the package with my changes applied in a clean chroot (
extra-x86-64-build -c) , and reading the binary, you can see LLD was used by default without specifying it nor installing thelldpackage (plus, you don't need to specifygccsince it's a part ofbase-devel). This is because rust automatically bundles its own version of LLD.This package is also missing
glibc,libgcc,libstdc++, anddbusfromdepends().I also recommend these changes for
deadlock-modmanager-git, so I will leave a comment there.