Your message dated Fri, 14 Aug 2020 00:04:38 +0200 with message-id <[email protected]> and subject line Re: Bug#968377: libplacebo FTBFS: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared has caused the Debian Bug report #968377, regarding libplacebo FTBFS: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 968377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968377 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: libplacebo Version: 1.29.1+dfsg1-2 Severity: serious Tags: ftbfs libplacebo fails to build from source in unstable. A build log ends with: | /usr/bin/mips64el-linux-gnuabi64-gcc -Isrc/libplacebo.so.29.p -Isrc -I../src -I../src/include -I../subprojects/xtalloc/include -I../subprojects/bstr/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -Wall -Wundef -Wshadow -Wparentheses -Wpointer-arith -D_ISOC99_SOURCE -D_GNU_SOURCE -D_XOPEN_SOURCE=700 -U__STRICT_ANSI__ -fvisibility=hidden -Wmissing-prototypes -Wno-pointer-sign -Werror=implicit-function-declaration -Werror=incompatible-pointer-types -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -pthread -MD -MQ src/libplacebo.so.29.p/vulkan_context.c.o -MF src/libplacebo.so.29.p/vulkan_context.c.o.d -o src/libplacebo.so.29.p/vulkan_context.c.o -c ../src/vulkan/context.c | ../src/vulkan/context.c: In function ‘pl_vulkan_choose_device’: | ../src/vulkan/context.c:391:10: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared (first use in this function); did you mean ‘VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM’? | 391 | [VK_PHYSICAL_DEVICE_TYPE_END_RANGE+1] = {0}, | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM | ../src/vulkan/context.c:391:10: note: each undeclared identifier is reported only once for each function it appears in | ../src/vulkan/context.c:391:10: error: array index in initializer not of integer type | ../src/vulkan/context.c:391:10: note: (near initialization for ‘types’) | ninja: build stopped: subcommand failed. | dh_auto_build: error: cd obj-mips64el-linux-gnuabi64 && LC_ALL=C.UTF-8 ninja -j1 -v returned exit code 1 | make: *** [debian/rules:7: binary-arch] Error 25 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Reproducible by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libplacebo_1.29.1+dfsg1-2.rbuild.log.gz Also seen by crossqa: http://crossqa.debian.net/build/libplacebo_1.29.1+dfsg1-2_mipsel_20200710170355.log Helmut
--- End Message ---
--- Begin Message ---Version: 2.72.0-1 On 2020-08-13 23:48:59 +0200, Helmut Grohne wrote: > Source: libplacebo > Version: 1.29.1+dfsg1-2 > Severity: serious > Tags: ftbfs > > libplacebo fails to build from source in unstable. A build log ends > with: > > | /usr/bin/mips64el-linux-gnuabi64-gcc -Isrc/libplacebo.so.29.p -Isrc > -I../src -I../src/include -I../subprojects/xtalloc/include > -I../subprojects/bstr/include -fdiagnostics-color=always -pipe > -D_FILE_OFFSET_BITS=64 -std=c99 -Wall -Wundef -Wshadow -Wparentheses > -Wpointer-arith -D_ISOC99_SOURCE -D_GNU_SOURCE -D_XOPEN_SOURCE=700 > -U__STRICT_ANSI__ -fvisibility=hidden -Wmissing-prototypes -Wno-pointer-sign > -Werror=implicit-function-declaration -Werror=incompatible-pointer-types > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC -pthread -MD > -MQ src/libplacebo.so.29.p/vulkan_context.c.o -MF > src/libplacebo.so.29.p/vulkan_context.c.o.d -o > src/libplacebo.so.29.p/vulkan_context.c.o -c ../src/vulkan/context.c > | ../src/vulkan/context.c: In function ‘pl_vulkan_choose_device’: > | ../src/vulkan/context.c:391:10: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ > undeclared (first use in this function); did you mean > ‘VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM’? > | 391 | [VK_PHYSICAL_DEVICE_TYPE_END_RANGE+1] = {0}, > | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > | | VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM > | ../src/vulkan/context.c:391:10: note: each undeclared identifier is > reported only once for each function it appears in > | ../src/vulkan/context.c:391:10: error: array index in initializer not of > integer type > | ../src/vulkan/context.c:391:10: note: (near initialization for ‘types’) > | ninja: build stopped: subcommand failed. > | dh_auto_build: error: cd obj-mips64el-linux-gnuabi64 && LC_ALL=C.UTF-8 > ninja -j1 -v returned exit code 1 > | make: *** [debian/rules:7: binary-arch] Error 25 > | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit > status 2 > > Reproducible by reproducible builds: > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libplacebo_1.29.1+dfsg1-2.rbuild.log.gz > > Also seen by crossqa: > http://crossqa.debian.net/build/libplacebo_1.29.1+dfsg1-2_mipsel_20200710170355.log Fixed in 2.72.0. Cheers -- Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
