Bug#1003219: vulkan-loader: FTBFS on i386: numbered symbols disappeared
Source: vulkan-loader Version: 1.2.198.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=vulkan-loader&arch=i386&ver=1.2.198.1-1&stamp=1641378736&raw=0 > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libvulkan1/DEBIAN/symbols doesn't match > completely debian/libvulkan1.symbols.i386 ... > +#MISSING: 1.2.198.1-1# vkPhysDevExtTermin177@Base 1.2.131.2 ... > +#MISSING: 1.2.198.1-1# vkdev_ext200@Base 1.2.131.2 (and many other numbered symbols) I think this is because changes to the build system resulted in some x86-specific code no longer being built on x86. Patches on the way when I have tested them. smcv
Processed: Re: Bug#1003219: vulkan-loader: FTBFS on i386: numbered symbols disappeared
Processing control commands: > forwarded -1 https://github.com/KhronosGroup/Vulkan-Loader/issues/783 Bug #1003219 [src:vulkan-loader] vulkan-loader: FTBFS on i386: numbered symbols disappeared Set Bug forwarded-to-address to 'https://github.com/KhronosGroup/Vulkan-Loader/issues/783'. > tags -1 + patch Bug #1003219 [src:vulkan-loader] vulkan-loader: FTBFS on i386: numbered symbols disappeared Added tag(s) patch. -- 1003219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003219: vulkan-loader: FTBFS on i386: numbered symbols disappeared
Control: forwarded -1 https://github.com/KhronosGroup/Vulkan-Loader/issues/783
Control: tags -1 + patch
On Thu, 06 Jan 2022 at 14:07:40 +, Simon McVittie wrote:
> I think this is because changes to the build system resulted in some
> x86-specific code no longer being built on x86. Patches on the way when
> I have tested them.
Please see attached.
You might also want to make debian/libvulkan1.symbols.aarch64 a symlink to
libvulkan1.symbols.amd64, now that aarch64 is treated similarly to x86.
smcv
From: Simon McVittie
Date: Thu, 6 Jan 2022 14:00:45 +
Subject: loader: Check for processor of compiler,
not processor of build system
If we are cross-compiling, for example for aarch64 on x86, then the
compiler we care about here is the machine we are compiling *for*,
e.g. aarch64 (the "target" in CMake terminology, the "host system" in
Autotools/Meson) rather than the machine we are compiling *on*, e.g. x86
(the "host" in CMake terminology, the "build system" in Autotools/Meson).
Signed-off-by: Simon McVittie
Bug: https://github.com/KhronosGroup/Vulkan-Loader/issues/783
Bug-Debian: https://bugs.debian.org/1003219
Forwarded: https://github.com/KhronosGroup/Vulkan-Loader/pull/784
---
loader/CMakeLists.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/loader/CMakeLists.txt b/loader/CMakeLists.txt
index c33858d..e85fef6 100644
--- a/loader/CMakeLists.txt
+++ b/loader/CMakeLists.txt
@@ -224,12 +224,12 @@ else(UNIX AND NOT APPLE) # i.e.: Linux
set(CMAKE_ASM_FLAGS "${CMAKE_C_FLAGS}")
set(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)
-if (${CMAKE_HOST_SYSTEM_PROCESSOR} STREQUAL "aarch64")
+if (${CMAKE_SYSTEM_PROCESSOR} STREQUAL "aarch64")
try_compile(ASSEMBLER_WORKS ${CMAKE_CURRENT_BINARY_DIR} ${CMAKE_CURRENT_SOURCE_DIR}/asm_test_aarch64.S)
if(ASSEMBLER_WORKS)
set(OPT_LOADER_SRCS ${OPT_LOADER_SRCS} unknown_ext_chain_gas_aarch64.S)
endif()
-elseif(${CMAKE_HOST_SYSTEM_PROCESSOR} STREQUAL "x86_64" OR ${CMAKE_HOST_SYSTEM_PROCESSOR} STREQUAL "x86")
+elseif(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64" OR ${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86")
check_include_file("cet.h" HAVE_CET_H)
if(HAVE_CET_H)
set_property(DIRECTORY APPEND PROPERTY COMPILE_DEFINITIONS HAVE_CET_H)
@@ -249,7 +249,7 @@ else(UNIX AND NOT APPLE) # i.e.: Linux
add_custom_target(loader_asm_gen_files DEPENDS gen_defines.asm)
else()
if(USE_GAS)
-message(WARNING "Could not find working ${CMAKE_HOST_SYSTEM_PROCESSOR} GAS assembler\n${ASM_FAILURE_MSG}")
+message(WARNING "Could not find working ${CMAKE_SYSTEM_PROCESSOR} GAS assembler\n${ASM_FAILURE_MSG}")
else()
message(WARNING "Assembly sources have been disabled\n${ASM_FAILURE_MSG}")
endif()
From: Simon McVittie
Date: Thu, 6 Jan 2022 14:03:40 +
Subject: loader: Compile x86-specific code on x86 Linux
Unfortunately, the taxonomy used for CMAKE_SYSTEM_PROCESSOR is
OS-specific: on Windows, IA32 is identified as x86, but on Linux,
it can be identified as i386, i486, i586 or i686.
Signed-off-by: Simon McVittie
Bug: https://github.com/KhronosGroup/Vulkan-Loader/issues/783
Bug-Debian: https://bugs.debian.org/1003219
Forwarded: https://github.com/KhronosGroup/Vulkan-Loader/pull/784
---
loader/CMakeLists.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/loader/CMakeLists.txt b/loader/CMakeLists.txt
index e85fef6..d7a876e 100644
--- a/loader/CMakeLists.txt
+++ b/loader/CMakeLists.txt
@@ -229,7 +229,7 @@ else(UNIX AND NOT APPLE) # i.e.: Linux
if(ASSEMBLER_WORKS)
set(OPT_LOADER_SRCS ${OPT_LOADER_SRCS} unknown_ext_chain_gas_aarch64.S)
endif()
-elseif(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64" OR ${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86")
+elseif(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64" OR ${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86" OR ${CMAKE_SYSTEM_PROCESSOR} MATCHES "^i.86$")
check_include_file("cet.h" HAVE_CET_H)
if(HAVE_CET_H)
set_property(DIRECTORY APPEND PROPERTY COMPILE_DEFINITIONS HAVE_CET_H)
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 997611 xutils-dev
Bug #997611 [src:wnn6-sdk] wnn6-sdk: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:wnn6-sdk' to 'xutils-dev'.
No longer marked as found in versions wnn6-sdk/1.0.0-18.
Ignoring request to alter fixed versions of bug #997611 to the same values
previously set
> reassign 997621 xutils-dev
Bug #997621 [src:fvwm1] fvwm1: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:fvwm1' to 'xutils-dev'.
No longer marked as found in versions fvwm1/1.24r-57.
Ignoring request to alter fixed versions of bug #997621 to the same values
previously set
> reassign 997622 xutils-dev
Bug #997622 [src:kinput2] kinput2: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:kinput2' to 'xutils-dev'.
No longer marked as found in versions kinput2/3.1-13.
Ignoring request to alter fixed versions of bug #997622 to the same values
previously set
> reassign 997643 xutils-dev
Bug #997643 [src:ctwm] ctwm: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:ctwm' to 'xutils-dev'.
No longer marked as found in versions ctwm/3.7-5.
Ignoring request to alter fixed versions of bug #997643 to the same values
previously set
> forcemerge 997615 997611 997621 997622 997643
Bug #997615 {Done: Timo Aaltonen } [xutils-dev] troffcvt:
FTBFS: ar: libdeps specified more than once
Bug #994276 {Done: Timo Aaltonen } [xutils-dev]
xutils-dev: imake shouldn't pass l to ar
Bug #997628 {Done: Samuel Thibault } [xutils-dev] imake:
uses “ar clq” by default, which recent binutils broke in an incompatible way
Bug #997636 {Done: Timo Aaltonen } [xutils-dev] koules:
FTBFS: ar: libdeps specified more than once
Bug #997638 {Done: Samuel Thibault } [xutils-dev] nas:
FTBFS: ar: libdeps specified more than once
Bug #997641 {Done: Timo Aaltonen } [xutils-dev] knews:
FTBFS: ar: libdeps specified more than once
Bug #997650 {Done: Timo Aaltonen } [xutils-dev] xtel:
FTBFS: ar: libdeps specified more than once
Bug #997622 [xutils-dev] kinput2: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997622 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #997643 [xutils-dev] ctwm: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997643 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #997611 [xutils-dev] wnn6-sdk: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997611 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #997621 [xutils-dev] fvwm1: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997621 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #994276 {Done: Timo Aaltonen } [xutils-dev]
xutils-dev: imake shouldn't pass l to ar
Bug #997628 {Done: Samuel Thibault } [xutils-dev] imake:
uses “ar clq” by default, which recent binutils broke in an incompatible way
Bug #997636 {Done: Timo Aaltonen } [xutils-dev] koules:
FTBFS: ar: libdeps specified more than once
Bug #997638 {Done: Samuel Thibault } [xutils-dev] nas:
FTBFS: ar: libdeps specified more than once
Bug #997641 {Done: Timo Aaltonen } [xutils-dev] knews:
FTBFS: ar: libdeps specified more than once
Bug #997650 {Done: Timo Aaltonen } [xutils-dev] xtel:
FTBFS: ar: libdeps specified more than once
Merged 994276 997611 997615 997621 997622 997628 997636 997638 997641 997643
997650
> affects 997615 src:wnn6-sdk src:fvwm1 src:kinput2 src:ctwm
Bug #997615 {Done: Timo Aaltonen } [xutils-dev] troffcvt:
FTBFS: ar: libdeps specified more than once
Bug #994276 {Done: Timo Aaltonen } [xutils-dev]
xutils-dev: imake shouldn't pass l to ar
Bug #997611 {Done: Timo Aaltonen } [xutils-dev] wnn6-sdk:
FTBFS: ar: libdeps specified more than once
Bug #997621 {Done: Timo Aaltonen } [xutils-dev] fvwm1:
FTBFS: ar: libdeps specified more than once
Bug #997622 {Done: Timo Aaltonen } [xutils-dev] kinput2:
FTBFS: ar: libdeps specified more than once
Bug #997628 {Done: Samuel Thibault } [xutils-dev] imake:
uses “ar clq” by default, which recent binutils broke in an incompatible way
Bug #997636 {Done: Timo Aaltonen } [xutils-dev] koules:
FTBFS: ar: libdeps specified more than once
Bug #997638 {Done: Samuel Thibault } [xutils-dev] nas:
FTBFS: ar: libdeps specified more than once
Bug #997641 {Done: Timo Aaltonen } [xutils-dev] knews:
FTBFS: ar: libdeps specified more than once
Bug #997643 {Done: Timo Aaltonen } [xutils-dev] ctwm:
FTBFS: ar: libdeps specified more than once
Bug #997650 {Done: Timo Aalton
Bug#1003264: mesa: Build-Dependency cycle between mesa and libglvnd
Source: mesa Version: 21.3.3-1 Severity: important Hello, Looks like there is still a build-dependency loop between mesa and libglvnd mesa build-depends on: - libglvnd-dev:kfreebsd-amd64 (>= 1.3.2) libglvnd-dev depends on: - libglx-dev:kfreebsd-amd64 (>= 1.3.0-1) libglx-dev depends on: - libglx0:kfreebsd-amd64 (= 1.4.0-1) libglx0 depends on missing: - libglx-mesa0:kfreebsd-amd64 In #979976 you have reintroduced the libglvnd-core-dev package, but it seems that mesa is still BD on libglvnd-dev instead Could you please switch the build-dependency from libglvnd-dev to libglvnd-core-dev? Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
