Your message dated Sat, 21 Oct 2023 12:37:51 +0200 with message-id <20231021103751.qix8l...@breakpoint.cc> and subject line Re: Bug#1054180: openssl: FTBFS on loong64 has caused the Debian Bug report #1054180, regarding openssl: FTBFS on loong64 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.) -- 1054180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: openssl Version: 3.1.2-1 Severity: wishlist Tags: ftbfs User:debian-de...@lists.debian.org Usertags: loongarch64 OpenSSL 3.1.x in experimental FTBFS on loong64: |crypto/aes/vpaes-loongarch64.S: Assembler messages: |crypto/aes/vpaes-loongarch64.S:24: Error: no match insn: vori.b $vr1,$vr9,0 |crypto/aes/vpaes-loongarch64.S:26: Error: no match insn: vld $vr2,$r12,0 |crypto/aes/vpaes-loongarch64.S:27: Error: no match insn: vandn.v $vr1,$vr1,$vr0 … Latest build log https://buildd.debian.org/status/fetch.php?pkg=openssl&arch=loong64&ver=3.1.3-1&stamp=1695145526&raw=0 My guess is that either binutils support is missing or a flag/ CPU switch is missing to recognise the vector opcodes. Sebastian
--- End Message ---
--- Begin Message ---On 2023-10-21 13:17:33 [+0800], WANG Xuerui wrote: > Also the binutils instruction set support is actually complete and released > in 2.41, so a custom build isn't necessary either: we'd only have to wait So why all the fuzz instead of looking at what is important? binutils 2.41 is alread in Debian. I just gave the openssl package back and it built. Sebastian
--- End Message ---
