Package Details: alvr 20.11.1-1

Git Clone URL: https://aur.archlinux.org/alvr.git (read-only, click to copy)
Package Base: alvr
Description: Experimental Linux version of ALVR. Stream VR games from your PC to your headset via Wi-Fi.
Upstream URL: https://github.com/alvr-org/ALVR
Licenses: MIT
Conflicts: alvr
Provides: alvr
Submitter: m00nw4tch3r
Maintainer: m00nw4tch3r (alvrbot1)
Last Packager: m00nw4tch3r
Votes: 23
Popularity: 0.040598
First Submitted: 2021-09-23 21:53 (UTC)
Last Updated: 2024-10-02 06:31 (UTC)

Pinned Comments

m00nw4tch3r commented on 2024-09-03 10:22 (UTC)

Troubleshooting Guide: https://github.com/alvr-org/ALVR/wiki/Linux-Troubleshooting

DocMAX commented on 2024-09-01 10:41 (UTC)

Needs PRESSURE_VESSEL_FILESYSTEMS_RO="/usr/lib/steamvr/alvr/" to make it work. Please include this.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

rvasilev commented on 2023-04-07 18:22 (UTC)

Patched layer.h builds without errors.

I wonder if PKGBUILD could be cleaned?

Remove pkgver(){} as stated earlier

Maybe remove sed -i 's:../../../lib64/libalvr_vulkan_layer.so:libalvr_vulkan_layer.so:' alvr/vulkan_layer/layer/alvr_x86_64.json and echo "[profile.release] lto=true" >> Cargo.toml from prepare(){}

Maybe remove all export VARIABLE from build(){}

Replace cargo build ... with cargo xtask build-server --release

With all the cleaning looks like the package builds and runs the same.

CaptainSolidus commented on 2023-04-07 15:49 (UTC)

I can confirm that codedwrench's patches allow the build to finish, and ALVR appears to work identically to the AppImage version.

codedwrench commented on 2023-04-07 12:45 (UTC) (edited on 2023-04-07 12:45 (UTC) by codedwrench)

Seems that patching layer.h to contain: #define VK_LAYER_EXPORT __attribute__((visibility("default")))

does work, but this is probably not the right solution. http://ix.io/4sSQ < here is the patch you would need to your PKGBUILD

And for completeness sake, the patch to the PKGBUILD as well http://ix.io/4sSS

danir.de commented on 2023-04-01 22:40 (UTC) (edited on 2023-04-01 22:41 (UTC) by danir.de)

It's failing for me as well, in the current build, same as what Wupwup is experiencing, a more detailed log:

running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-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" "-I" "/var/tmp/alvr/src/alvr/alvr/vulkan_layer" "-I" "/var/tmp/alvr/src/alvr/alvr/vulkan_layer/../server/cpp" "-I" "/usr/include" "-I" "/usr/include" "-std=c++17" "-Wno-unused-parameter" "-DVK_USE_PLATFORM_XLIB_XRANDR_EXT" "-o" "/var/tmp/alvr/src/alvr/target/release/build/alvr_vulkan_layer-2683da789fdafa36/out/./layer/surface_api.o" "-c" "./layer/surface_api.cpp"
cargo:warning=In Datei, eingebunden von ./layer/settings.cpp:9:
cargo:warning=./layer/layer.h:7:12: Fehler: »VK_LAYER_EXPORT« bezeichnet keinen Typ
cargo:warning=    7 | extern "C" VK_LAYER_EXPORT PFN_vkVoidFunction VKAPI_CALL wsi_layer_vkGetDeviceProcAddr(VkDevice device, const char *funcName);
cargo:warning=      |            ^~~~~~~~~~~~~~~
cargo:warning=./layer/layer.h:8:12: Fehler: »VK_LAYER_EXPORT« bezeichnet keinen Typ
cargo:warning=    8 | extern "C" VK_LAYER_EXPORT VKAPI_ATTR PFN_vkVoidFunction VKAPI_CALL wsi_layer_vkGetInstanceProcAddr(VkInstance instance, const char *funcName);
cargo:warning=      |            ^~~~~~~~~~~~~~~
exit status: 0
exit status: 0
exit status: 1
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-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" "-I" "/var/tmp/alvr/src/alvr/alvr/vulkan_layer" "-I" "/var/tmp/alvr/src/alvr/alvr/vulkan_layer/../server/cpp" "-I" "/usr/include" "-I" "/usr/include" "-std=c++17" "-Wno-unused-parameter" "-DVK_USE_PLATFORM_XLIB_XRANDR_EXT" "-o" "/var/tmp/alvr/src/alvr/target/release/build/alvr_vulkan_layer-2683da789fdafa36/out/./layer/swapchain_api.o" "-c" "./layer/swapchain_api.cpp"
exit status: 0

--- stderr


error occurred: Command "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-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" "-I" "/var/tmp/alvr/src/alvr/alvr/vulkan_layer" "-I" "/var/tmp/alvr/src/alvr/alvr/vulkan_layer/../server/cpp" "-I" "/usr/include" "-I" "/usr/include" "-std=c++17" "-Wno-unused-parameter" "-DVK_USE_PLATFORM_XLIB_XRANDR_EXT" "-o" "/var/tmp/alvr/src/alvr/target/release/build/alvr_vulkan_layer-2683da789fdafa36/out/./layer/settings.o" "-c" "./layer/settings.cpp" with args "c++" did not execute successfully (status code exit status: 1).

kusoneko commented on 2023-04-01 21:16 (UTC)

I'm having the same issue as Wupwup. It seems something in the newest commits to the AUR is causing the vulkan-layer part of the build to fail.

Also, as stated by artafinde, you should remove the pkgver function and manually put the version into the pkgver variable as it's not a VCS package. And while you're at it, you could get rid of the _tag variable and where it's used instead put v${pkgver} so that if the version updates you only need to update the source, pkgsums and pkgver variables. A non-vcs package doesn't need the .rx.commithash version info stuff at all.

Wupwup commented on 2023-04-01 16:11 (UTC)

The build is failing for me as well.


  error occurred: Command "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-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" "-I" "/home/wupwup/alvr/src/alvr/alvr/vulkan_layer" "-I" "/home/wupwup/alvr/src/alvr/alvr/vulkan_layer/../server/cpp" "-I" "/usr/include" "-I" "/usr/include" "-std=c++17" "-Wno-unused-parameter" "-DVK_USE_PLATFORM_XLIB_XRANDR_EXT" "-o" "/home/wupwup/alvr/src/alvr/target/release/build/alvr_vulkan_layer-62bada04649580ce/out/./layer/layer.o" "-c" "./layer/layer.cpp" with args "c++" did not execute successfully (status code exit status: 1).


warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...

Northcode commented on 2023-03-21 20:05 (UTC)

running cargo xtask prepare-deps makes the package require more dependencies, so cargo fetch must be run again before running cargo build otherwise it will give an error about missing dependency ab_glyph.

hcjl commented on 2023-02-21 17:44 (UTC)

m00nw4tch3r, thanks a lot for updating this. It would be great, if you could correct pkgrel.

roadnottaken commented on 2023-02-21 00:24 (UTC)

I ran into the same issue as D3SOX. yay -S yasm resolved it, but then the build errored out again with

$ rustup target add aarch64-linux-android
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: command not found: `rustup`', alvr/xtask/src/dependencies.rs:251:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
==> ERROR: A failure occurred in build().

Choosing rustup instead of rust to fulfill the cargo dependency replaced this error with

error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.
==> ERROR: A failure occurred in prepare().

After running rustup default stable, alvr built cleanly.

I'd recommend adding yasm as a make dependency and replacing the cargo dependency with rustup. As for the final error, I'm not familiar enough with the rust toolchain to know whether there's a way to automatically resolve it that doesn't potentially make unexpected changes to the user's environment.

D3SOX commented on 2023-02-19 22:21 (UTC)

Failed to build 19.1.0

nasm/yasm not found or too old. Use --disable-x86asm for a crippled build.

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: command exited with non-zero code `./configure --prefix=/home/nico/.cache/paru/clone/alvr/src/alvr/deps/linux/ffmpeg/alvr_build --enable-gpl --enable-version3 --enable-static --enable-shared --disable-programs --disable-doc --disable-avdevice --disable-avformat --disable-swresample --disable-postproc --disable-network --enable-lto --disable-everything --enable-encoder=h264_vaapi --enable-encoder=hevc_vaapi --enable-encoder=libx264 --enable-encoder=libx264rgb --enable-hwaccel=h264_vaapi --enable-hwaccel=hevc_vaapi --enable-filter=scale --enable-filter=scale_vaapi --enable-libx264 --enable-vulkan --enable-libdrm --enable-pic --enable-rpath`: 1', alvr/xtask/src/dependencies.rs:205:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace