Your message dated Sat, 19 Nov 2022 15:36:25 +0000 with message-id <e1owptj-004qf5...@fasolo.debian.org> and subject line Bug#1000941: Removed package(s) from unstable has caused the Debian Bug report #992349, regarding libclang-common-11-dev: Cannot install amd64 and armhf together 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 ow...@bugs.debian.org immediately.) -- 992349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libclang-common-11-dev Version: 1:11.0.1-2~bpo10+1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Try to install both packages. apt install clang-11/buster-backports * What exactly did you do (or not do) that was effective (or ineffective)? Manually extract files from armhf pacakge and copy it * What was the outcome of this action? I cannot install amd64 and armhf version together. It's a problem for cross-compilation with clang because you cannot link against compiler-rt. For example I have issue with m4 (libm4), m4 can be compiled with gcc and linked against libgcc, also it can be compiled with clang and linked against compiler-rt, but it cannot be compiled with clang and linked against libgcc. It leads to: /usr/bin/arm-linux-gnueabihf-ld: symtab.o: in function `symtab_init': symtab.c:(.text+0x34): undefined reference to `__mulodi4' /usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(clean-temp.o): in function `create_temp_dir': clean-temp.c:(.text+0x9c): undefined reference to `__mulodi4' /usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(fatal-signal.o): in function `at_fatal_signal': fatal-signal.c:(.text+0x190): undefined reference to `__mulodi4' /usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(xmalloc.o): in function `xnmalloc': xmalloc.c:(.text+0x30): undefined reference to `__mulodi4' /usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(xmalloc.o): in function `xnrealloc': xmalloc.c:(.text+0xe4): undefined reference to `__mulodi4' /usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(xmalloc.o):xmalloc.c:(.text+0x334): more undefined references to `__mulodi4' follow Briefly speaking it leads to missing /usr/lib/llvm-11/lib/clang/11.0.1/lib/linux/libclang_rt.builtins-armhf.a * What outcome did you expect instead? I didn't expect conflict between multiarch packages. -- System Information: Debian Release: 10.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.19.0-17-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libclang-common-11-dev depends on: ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libllvm11 1:11.0.1-2~bpo10+1 ii libstdc++6 8.3.0-6 libclang-common-11-dev recommends no packages. libclang-common-11-dev suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1:11.1.0-6+rm Dear submitter, as the package llvm-toolchain-11 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1000941 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
