Arch Linux User Repository

Got some building error when tring to install this package, btw I use cachyos with arch official repo.

==> 正在开始 prepare()...
patching file CMakeLists.txt
patching file deps.json
patching file plugins/CMakeLists.txt
    Updating crates.io index
    Updating git repository `https://github.com/waywallen/waywallen-display`
     Locking 320 packages to latest compatible versions
      Adding env_logger v0.10.2 (available: v0.11.10)
      Adding generic-array v0.14.7 (available: v0.14.9)
      Adding libloading v0.8.9 (available: v0.9.0)
      Adding lua-src v547.0.0 (available: v547.1.0)
      Adding luajit-src v210.5.12+a4f56a4 (available: v210.7.1+18b087c)
      Adding mlua v0.10.5 (available: v0.11.6)
      Adding nix v0.29.0 (available: v0.31.3)
      Adding prost v0.13.5 (available: v0.14.3)
      Adding prost-build v0.13.5 (available: v0.14.3)
      Adding tokio-tungstenite v0.24.0 (available: v0.29.0)
      Adding toml v0.8.23 (available: v1.1.2+spec-1.1.0)
      Adding zbus v4.4.0 (available: v5.15.0)
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/ice/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --target host-tuple --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg -Wwarnings` (exit status: 1)
  --- stderr
  error: error loading target specification: could not find specification for target "host-tuple"
    |
    = help: run `rustc --print target-list` for a list of built-in targets

==> 错误： 在 prepare() 中发生一个错误。
    正在放弃...
错误： 未能构建 'waywallen-0.1.4-1': 
错误： 未能构建的软件包：waywallen-0.1.4-1

@Sterophonick

I have the same problem

@Sterophonick @mr_nuub

I believe your problems are the same. But I cannot reproduce on my vanilla archlinux, my help maybe very limited. I ran pkgctl build on my PKGBUILD repository just now and it still succeeds. As 0.1.1 builds while later versions fails, the most notable changes related to qmlmaterai is that I replace aur/qmlmaterial with a bundled one, because aur/qmlmaterial is not new enough. You may consider using pkgctl build to build this in an isolated chroot environment. @mr_nuub uses opt-level=3 in rust flags while using -O2 in c++ part, I am not sure if this is related to the problems you faced either. Maybe you can unify opt level to 2 on both parts? If that failed, you may consider creating an issue at upstream repository.

Unable to be compiled,

_deps/qml_material-build/CMakeFiles/qml_materialplugin_init.dir/./qml_materialplugin_init_autogen/mocs_compilation.cpp.o: file not recognized: file format not recognized

I used rustup because I wanted to develop some software. The more I used rust, the less I liked it. So now I switched to system rust. I removed everything using rustup uninstall before I switched. As I said previously, I can build version 0.1.1, but as soon as I want to build something newer, it fails.

I think the switch from system qmlmaterial to source qmlmaterial broke it.

Build log of PKGBUILD commit 10bf40f635a4: https://paste.cachyos.org/p/33c213a.txt

Build log of PKGBUILD commit a5e52c3226fe: https://paste.cachyos.org/p/ec6e56a.txt

Here 's the output of cat /etc/makepkg.conf.d/*: https://paste.cachyos.org/p/070cc07.txt

EDIT: I removed system qmlmaterial and the outcome didn't change.

@mr_nuub

[986/1268] cd /home/mrnuub/.cache/paru/clone/waywallen/src/waywallen && /usr/bin/cmake -E env CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_LINKER=/usr/bin/clang CC_x86_64-unknown-linux-gnu=/usr/bin/clang CXX_x86_64-unknown-linux-gnu=/usr/bin/clang++ AR_x86_64-unknown-linux-gnu=/usr/bin/llvm-ar CORROSION_BUILD_DIR=/home/mrnuub/.cache/paru/clone/waywallen/src/build CARGO_BUILD_RUSTC=/home/mrnuub/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc /home/mrnuub/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/cargo rustc --bin=waywallen_display_demo --target=x86_64-unknown-linux-gnu --package waywallen --manifest-path /home/mrnuub/.cache/paru/clone/waywallen/src/waywallen/Cargo.toml --target-dir /home/mrnuub/.cache/paru/clone/waywallen/src/build/cargo/waywallen_33bf2 --release -- -Cdefault-linker-libraries=yes

This seems not right, the linker should be lld instead clang? But I really have not checked about this.

Besides, according to your log, you are using rust 1.92 from rustup, you may consider using rust from repository, which has been 1.95 now. The more important, I build this package by using rust from repository.

Not only makepkg.conf, but also the drop-in files in makepkg.conf.d/*.conf can change your flags.

To overcome all problems mentioned above, while keep least changes to your system, you can build this package in a chroot environment by using pkgctl build after you installed devtools.

I simply cannot build this anymore. I have already tried commenting out CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS, LTOFLAGS, MAKEFLAGS, NINJAFLAGS, DEBUG_CFLAGS and DEBUG_CXXFLAGS in makepkg.conf. I tried a fresh git clone and makepkg -si. The result is the same, every time.

This is my makepkg.conf: https://paste.cachyos.org/p/cf702ec.txt

This is the log of paru -Syu makepkg: https://paste.cachyos.org/p/3716627.txt

UPDATE: new build log with stderr

@mr_nuub I cannot reproduce this on my machine even replace my CXXFLAGS to -march=native -O3 like yours. As I only got parts of your build log, I guess this is because that you mixed your compiler during building by accident. You may build this package in a chroot environment to avoid this.

Hi! I am unable to build this PKGBUILD since 0.1.2. 0.1.3 is affected, too. 0.1.1 worked like a charm. The system is updated at a daily basis. Here's the log: https://paste.cachyos.org/p/39053e6.txt