search

lutris / dxvk

Lutris' DXVK repository for providing custom DXVK versions
zlib License
25 stars 3 forks source link

error: ‘cv_status’ in namespace ‘std’ does not name a type #12

Closed digi4care closed 2 years ago

digi4care commented 2 years ago

While compiling the dxvk i am getting this error

ERROR

../../../src/util/thread.h:285:10: error: ‘cv_status’ in namespace ‘std’ does not name a type 285 std::cv_status wait_until(std::unique_lock& lock, const std::chrono::time_point<Clock, Duration>& time) {

System information

-CPU : AMD Ryzen Threadripper 2970WX 24-Core Processor Memory : 32767MB Operating System : Debian GNU/Linux 11 (bullseye) -Display Resolution : 8800x1440 pixels -GPU : NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2

./package-release.sh master build --no-package The Meson build system Version: 0.63.2 Source dir: /home/digi4care/Development/Github/Drivers/dxvk Build dir: /home/digi4care/Development/Github/Drivers/dxvk/build/dxvk-master/build.64 Build type: cross build Project name: dxvk Project version: v1.10.3 C compiler for the host machine: x86_64-w64-mingw32-gcc (gcc 10.0.0 "x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110") C linker for the host machine: x86_64-w64-mingw32-gcc ld.bfd 2.35.2 C++ compiler for the host machine: x86_64-w64-mingw32-g++ (gcc 10.0.0 "x86_64-w64-mingw32-g++ (GCC) 10-win32 20210110") C++ linker for the host machine: x86_64-w64-mingw32-g++ ld.bfd 2.35.2 C compiler for the build machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 20210110") C linker for the build machine: cc ld.bfd 2.35.2 C++ compiler for the build machine: c++ (gcc 10.2.1 "c++ (Debian 10.2.1-6) 10.2.1 20210110") C++ linker for the build machine: c++ ld.bfd 2.35.2 Build machine cpu family: x86_64 Build machine cpu: x86_64 Host machine cpu family: x86_64 Host machine cpu: x86_64 Target machine cpu family: x86_64 Target machine cpu: x86_64 Compiler for C++ supports arguments -DNOMINMAX: YES Compiler for C++ supports arguments -D_WIN32_WINNT=0xa00: YES Compiler for C++ supports arguments -msse: YES Compiler for C++ supports arguments -msse2: YES Compiler for C++ supports arguments -msse3: YES Compiler for C++ supports arguments -mfpmath=sse: YES Compiler for C++ supports arguments -Wimplicit-fallthrough: YES Compiler for C++ supports arguments -Wno-unused-private-field: NO Compiler for C++ supports arguments -Wno-microsoft-exception-spec: NO Compiler for C supports arguments -DNOMINMAX: YES Compiler for C supports arguments -D_WIN32_WINNT=0xa00: YES Compiler for C supports arguments -msse: YES Compiler for C supports arguments -msse2: YES Compiler for C supports arguments -msse3: YES Compiler for C supports arguments -mfpmath=sse: YES Compiler for C supports arguments -Wimplicit-fallthrough: YES Compiler for C supports arguments -Wno-unused-private-field: NO Compiler for C supports arguments -Wno-microsoft-exception-spec: NO Compiler for C++ supports link arguments -static: YES Compiler for C++ supports link arguments -static-libgcc: YES Compiler for C++ supports link arguments -static-libstdc++: YES Compiler for C++ supports link arguments -Wl,--file-alignment=4096: YES Compiler for C supports link arguments -static: YES Compiler for C supports link arguments -static-libgcc: YES Compiler for C supports link arguments -static-libstdc++: YES Compiler for C supports link arguments -Wl,--file-alignment=4096: YES Library vulkan-1 found: YES Library d3d9 found: YES Library d3d11 found: YES Library dxgi found: YES Library d3dcompiler_43 found: YES Library d3dcompiler_47 found: YES Program glslangValidator found: YES (/usr/bin/glslangValidator) Program x86_64-w64-mingw32-windres found: YES Run-time dependency threads found: YES Dependency threads found: YES unknown (cached) Build targets in project: 13 NOTICE: Future-deprecated features used:

dxvk v1.10.3

User defined options Cross files : /home/digi4care/Development/Github/Drivers/dxvk/build-win64.txt bindir : x64 buildtype : release libdir : x64 prefix : /home/digi4care/Development/Github/Drivers/dxvk/build/dxvk-master strip : True build_id : false enable_tests: false

digi4care commented 2 years ago

Nevermind i found the solution about this problem in your Troubleshooting area