Source: fftw3
Version: 3.3.10-1
Followup-For: Bug #1050691
X-Debbugs-Cc: wuruil...@loongson.cn

Dear Maintainer,

loongarch supports long double types, reference link: 
https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html. 
Currently not added due to the architecture of libfftw3-long3 loong64, causing 
cubature compilation to fail. Please merge into the attached patch

wuruilong

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: loong64 (loongarch64)

Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- fftw3-3.3.10/debian/control 2024-06-13 02:16:14.322661748 +0000
+++ fftw3/debian/control        2024-06-13 01:54:45.150536357 +0000
@@ -49,7 +49,7 @@
  libfftw3-dev. For documentation, see libfftw3-doc.
 
 Package: libfftw3-long3
-Architecture: amd64 arm64 hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 
mips64 mips64el powerpc powerpcspe ppc64el riscv64 s390 s390x sparc x32
+Architecture: amd64 arm64 hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 
loong64 mips64 mips64el powerpc powerpcspe ppc64el riscv64 s390 s390x sparc x32
 Multi-Arch: same
 Depends: ${misc:Depends},
          ${shlibs:Depends}
@@ -114,7 +114,7 @@
 Section: libdevel
 Depends: libfftw3-bin (=${binary:Version}),
          libfftw3-double3 (=${binary:Version}),
-         libfftw3-long3 (=${binary:Version}) [amd64 arm64 hurd-i386 i386 ia64 
kfreebsd-amd64 kfreebsd-i386 mips64 mips64el powerpc powerpcspe ppc64el riscv64 
s390 s390x sparc x32],
+         libfftw3-long3 (=${binary:Version}) [amd64 arm64 hurd-i386 i386 ia64 
kfreebsd-amd64 kfreebsd-i386 loong64 mips64 mips64el powerpc powerpcspe ppc64el 
riscv64 s390 s390x sparc x32],
          libfftw3-quad3 (=${binary:Version}) [amd64 hurd-i386 i386 
kfreebsd-amd64 kfreebsd-i386 x32],
          libfftw3-single3 (=${binary:Version}),
          ${misc:Depends}

Reply via email to