Bug#1071707: rustc: Add loong64 to the FAILURES_ALLOWED lists in d/rules

[zhangdandan]

Source: rustc
Version: 1.71.1+dfsg1-2
Severity: normal
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling rustc 1.71 based on llvm-toolchain-16 failed in the Debian 
loong64 Package Auto-Building environment.

The error log is as follows,
```
..
error: could not find native static library 
`/usr/lib/llvm-16/lib/clang/16/lib/linux/libclang_rt.profile-loongarch64.a`, 
perhaps an -L flag is missing?

Did not run successfully: exit status: 1
..
```
The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=rustc=1.71.1%2Bdfsg1-2=loong64.
Regarding the missing libclang_rt.profile-loongarch64.a file in the 
libclang-rt-16-dev package, our llvm team will add patches and commit 
bug for Debian llvm-toolchain-16.


Please note that Debian llvm support for loongarch is complete as of 
llvm-toolchain-17, for example,

```
root@localhost:/home# dpkg -c 
libclang-rt-16-dev_1%3a16.0.6-27_loong64.deb |grep 
libclang_rt.profile-loongarch64.a

root@localhost:/home#
root@localhost:/home# dpkg -c 
libclang-rt-17-dev_1%3a17.0.6-12_loong64.deb |grep 
libclang_rt.profile-loongarch64.a
-rw-r--r-- root/root    146744 2024-05-04 05:30 
./usr/lib/llvm-17/lib/clang/17/lib/linux/libclang_rt.profile-loongarch64.a
root@localhost:/home# dpkg -c 
libclang-rt-18-dev_1%3a18.1.6-1_loong64.deb |grep 
libclang_rt.profile-loongarch64.a
-rw-r--r-- root/root    150362 2024-05-19 07:27 
./usr/lib/llvm-18/lib/clang/18/lib/linux/libclang_rt.profile-loongarch64.a

```

Compiling rustc 1.71 based on llvm-toolchain-17 failed in our local 
loong64 ENV.
The error message is related to the number of failed test cases, for 
example,

```
..
Summary: exit code 1, counted 14 tests failed.
10 maximum allowed. Aborting the build.
..
```
We need to add loong64 to the FAILURES_ALLOWED lists in d/rules.
Please consider the patch (Signed-off-by: wang...@loongson.cn) I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff --git a/rules b/rules
index c7b0541..d9a423a 100755
--- a/rules
+++ b/rules
@@ -335,7 +335,7 @@ endif
 ifneq (,$(filter $(DEB_BUILD_ARCH), ppc64 s390x))
   FAILURES_ALLOWED = 40
 endif
-ifneq (,$(filter $(DEB_BUILD_ARCH), powerpc powerpcspe riscv64 sparc64 x32))
+ifneq (,$(filter $(DEB_BUILD_ARCH), powerpc powerpcspe riscv64 sparc64 x32 loong64))
   FAILURES_ALLOWED = 180
 endif
 FAILED_TESTS = grep "FAILED\|^command did not execute successfully" $(TEST_LOG) | grep -v '^test result: FAILED' | grep -v 'FAILED (allowed)'

Bug#1071606: ucx: FTBFS: add support for loongarch64

[zhangdandan]

Source: ucx
Version: 1.16.0+ds-5
Severity: normal
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the ucx failed for loong64 in my local ENV.

We need to add loong64 support in d/control.
And we need to add loongarch64 support in ucx source.

The debian ucx source package is pulling the upstream 1.16.x version.
The latest release version of ucx upstream is 1.17.x.
Support for the new architecture will be committed to the ucx upstream 
master branch.


Due to the large differences between the main branch and the 1.16.x 
version of the ucx code, I prioritized adding support for loongarch in 
the ucx 1.16.0+ds-5 source package.

Please consider the patch I attached.
Suggestion to consider adding the attached patch to the debian/patches.
For now, it is recommended that the attached patch be maintained in the 
debian ucx source package.
With the attached patch, the ucx source package was built successfully 
in my local ENV.

Execute the constructed binary and the output is normal, e.g.
```
root@localhost:/home/ucx/ucx-1.16.0+ds# ./debian/tmp/usr/bin/ucx_info -v
# Library version: 1.16.0
# Library path: 
/home/ucx/ucx-1.16.0+ds/debian/tmp/usr/lib/loongarch64-linux-gnu/libucs.so.0

# API headers version: 1.16.0
# Git branch '', revision 000
# Configured with: --build=loongarch64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include..

-enable-rc --enable-dc --enable-ud --with-mlx5-dv --enable-dm
```

In addition, I will add loongarch64 support to the ucx upstream master 
branch.
Future new upstream releases of the debian ucx source package will 
include support for the loongarch architecture.


Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru ucx-1.16.0+ds/debian/changelog ucx-1.16.0+ds/debian/changelog
--- ucx-1.16.0+ds/debian/changelog  2024-03-24 11:19:06.0 +
+++ ucx-1.16.0+ds/debian/changelog  2024-05-22 07:30:00.0 +
@@ -1,3 +1,9 @@
+ucx (1.16.0+ds-5+loong64) unreleased; urgency=medium
+
+  * Add support for loongarch64.
+
+ -- Dandan Zhang   Wed, 22 May 2024 15:30:00 +0800
+
 ucx (1.16.0+ds-5) unstable; urgency=medium
 
   * Fix FTBFS: Don't pass CFLAGS to C++ (cxxflags.patch). Closes: #1066543
diff -Nru ucx-1.16.0+ds/debian/control ucx-1.16.0+ds/debian/control
--- ucx-1.16.0+ds/debian/control2024-03-24 11:19:06.0 +
+++ ucx-1.16.0+ds/debian/control2024-05-22 07:26:40.0 +
@@ -4,13 +4,13 @@
 Maintainer: Debian Science Maintainers 

 Uploaders: Alastair McKinstry 
 Build-Depends: debhelper-compat (= 13),
- libibverbs-dev (>= 1.1.7) [amd64 arm64  riscv64 ppc64el s390x],
- libnuma-dev [amd64 arm64 riscv64 ppc64 s390x],
+ libibverbs-dev (>= 1.1.7) [amd64 arm64 loong64 riscv64 ppc64el s390x],
+ libnuma-dev [amd64 arm64 loong64 riscv64 ppc64 s390x],
  librdmacm-dev, 
  libibmad-dev,
  libibumad-dev,
  libfuse3-dev,
- libamdhip64-dev [!riscv64],
+ libamdhip64-dev [!riscv64 !loong64],
  doxygen,
  texlive-latex-base,
  lcov
@@ -20,7 +20,7 @@
 Homepage: https://www.openucx.org
 
 Package: ucx-utils
-Architecture: amd64 arm64 riscv64 ppc64el
+Architecture: amd64 arm64 loong64 riscv64 ppc64el
 Depends: libucx0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Description: Utilities for the UCX messaging library
  Unified Communication X (UCX) provides an optimized communication layer
@@ -32,7 +32,7 @@
 
 Package: libucx-dev
 Section: libdevel
-Architecture: amd64 arm64  riscv64 ppc64el
+Architecture: amd64 arm64 loong64 riscv64 ppc64el
 Multi-Arch: same
 Depends: libucx0 (= ${binary:Version}), ${misc:Depends}
 Description: Header files for UCX library
@@ -46,7 +46,7 @@
 Package: libucx0
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Architecture: amd64 arm64  riscv64 ppc64el
+Architecture: amd64 arm64 loong64 riscv64 ppc64el
 Multi-Arch: same
 Description: Unified Communication X libraries
  Unified Communication X (UCX) provides an optimized communication layer
diff -Nru ucx-1.16.0+ds/debian/patches/series 
ucx-1.16.0+ds/debian/patches/series
--- ucx-1.16.0+ds/debian/patches/series 2024-03-24 11:19:06.0 +
+++ ucx-1.16.0+ds/debian/patches/series 2024-05-22 07:24:44.0 +
@@ -4,3 +4,4 @@
 gcc-11.patch
 ptr-fix.patch
 cxxflags.patch
+ucx-add-loongarch64-support.patch
diff -Nru ucx-1.16.0+ds/debian/patches/ucx-add-loongarch64-support.patch 
ucx-1.16.0+ds/debian/patches/ucx-add-loongarch64-support.patch
--- ucx-1.16.0+ds/debian/patches/ucx-add-loongarch64-support.patch  
1970-01-01 00:00:00.0 +
+++ ucx-1.16.0+ds/debian/patches/ucx-add-loongarch64-support.patch  
2024-05-22 07:25:38.0 +
@@ -0,0 +1,601 @@
+Description: Add loongarch64 support 
+Signed-Off-By: lix...@loongson.cn, zhangdan...@loongson.cn
+Last-Update: 2024-05-22
+
+--- ucx-1.16.0+ds.orig/src/tools/info/sys_info.c
 ucx-1.16.0+ds/src/tools/info/sys_info.c
+@@ -41,6 +41,7 @@ static const char *cpu_model_names[] = {
+ 

Bug#1071205: pandoc: Use extra --ghc-options in d/rules on loong64

[zhangdandan]

Source: pandoc
Version: 3.1.3+ds-3
Severity: important
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64
X-Debbugs-Cc: wanghon...@loongson.cn, lix...@loongson.cn, 
fanp...@loongson.cn


Dear maintainers,

Compiling the pandoc failed for loong64 in the Debian Package 
Auto-Building environment.

The build error is still related to "relocation R_LARCH_B26 overflow..".
Please see the below error log,
```
Preprocessing executable 'pandoc' for pandoc-cli-0.1.1..
Building executable 'pandoc' for pandoc-cli-0.1.1..
[1 of 3] Compiling PandocCLI.Lua
[2 of 3] Compiling PandocCLI.Server
[3 of 3] Compiling Main
[4 of 4] Linking dist-ghc/build/pandoc/pandoc
/usr/bin/ld.bfd: 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2_thr.a(NonMovingMark.thr_o): 
relocation R_LARCH_B26 overflow 0xf62fb154

..
```
The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=pandoc=3.1.3%2Bds-3=loong64


There are three suggestions to solve "relocation R_LARCH_B26 overflow 
.." during static linking.

1.Add loong64 to the list of low-memory architectures.
2.Use "--enable-executable-dynamic" in d/rules to reduce binary size on 
loong64.
3.Add extra --ghc-options in d/rules on loong64 to increase 
jump-instructions' range.


It is recommended to use '--ghc-options="-optc-mcmodel=medium"' in 
d/rules for loong64.

Please consider the patch I attached.
- Add --ghc-options="-optc-mcmodel=medium" in d/rules for loong64.
- Remove loong64 from the list of low-memory architectures.

With the attached patch, the pandoc was built successfully in my local ENV.
And I have uploaded a native pandoc to debian ports.
```
..
dh_md5sums -ppandoc
dh_builddeb -ppandoc
dpkg-deb: building package 'pandoc' in '../pandoc_3.1.3+ds-3_loong64.deb'.
 dpkg-genbuildinfo -O../pandoc_3.1.3+ds-3_loong64.buildinfo
 dpkg-genchanges -O../pandoc_3.1.3+ds-3_loong64.changes
dpkg-genchanges: info: not including original source code in upload
 dpkg-source --after-build .
```

The end, the compilation order of the relevant packages are as follows,
- ghc
- haskell-isocline
- haskell-lua
- haskell-primitive
- haskell-splitmix
- haskell-zlib
- haskell-pandoc
- haskell-pandoc-lua-engine
- pandoc

Meanwhile, we have submitted bugs to the above 9 packages to suggest to 
use --ghc-options="-optc-mcmodel=medium".

Your opinions are welcome.

Thanks,
Dandan Zhang
diff -Nru pandoc-3.1.3+ds/debian/rules pandoc-3.1.3+ds/debian/rules
--- pandoc-3.1.3+ds/debian/rules2024-04-20 23:16:47.0 +
+++ pandoc-3.1.3+ds/debian/rules2024-04-20 23:16:47.0 +
@@ -50,10 +50,14 @@
 DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="+RTS -V0 -RTS"
 
 # Reduce compile-time memory utilization on low-memory architectures
-ifneq (,$(filter $(DEB_BUILD_ARCH),armel armhf hppa loong64 mips mipsel))
+ifneq (,$(filter $(DEB_BUILD_ARCH),armel armhf hppa mips mipsel))
 DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc--param 
-optcggc-min-expand=10 -O0"
 endif
 
+ifneq (,$(filter $(DEB_BUILD_ARCH),loong64))
+  DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc-mcmodel=medium"
+endif
+
 ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386))
 DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-O0"
 endif

Bug#1071173: haskell-pandoc-lua-engine: Use extra --ghc-options in d/rules on loong64

[zhangdandan]

Source: haskell-pandoc-lua-engine
Version: 0.2.0.1-1
Severity: important
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The haskell-pandoc-lua-engine is blocked from building by haskell-pandoc 
in the Debian Package Auto-Building environment.

Compiling the haskell-pandoc-lua-engine failed for loong64 in my local ENV.
The error message is consistent with haskel-pandoc, and both are related 
to "relocation R_LARCH_B26 overflow .." during static linking in the 
test-pandoc stage.
The build error log of haskell-pandoc-lua-engine from my local ENV is as 
follows,

```
[6 of 6] Linking 
dist-ghc/build/test-pandoc-lua-engine/test-pandoc-lua-engine
/usr/bin/ld.bfd: 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2.a(NonMovingMark.o): 
relocation R_LARCH_B26 overflow 0xf61da41c

Dump relocate record:
stack top        relocation name        symbol
at 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2.a(NonMovingMark.o)(.text+0xae4):

...
0x R_LARCH_B16    `.L172'
..
```

There are two suggestions to solve "relocation R_LARCH_B26 overflow 
.." during static linking.

1.Add build rules to reduce binary size.
2.Disable tests in d/rules on loong64.
3.Add extra --ghc-options in d/rules on loong64 to increase 
jump-instructions' range.


It is recommended to use --ghc-options="-optc-mcmodel=medium" in d/rules 
for loong64.

Please consider the patch I attached.
With the attached patch, the haskell-pandoc-lua-engine was built 
successfully in my local ENV.



Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru haskell-pandoc-lua-engine-0.2.0.1/debian/rules 
haskell-pandoc-lua-engine-0.2.0.1/debian/rules
--- haskell-pandoc-lua-engine-0.2.0.1/debian/rules  2024-01-04 
00:32:40.0 +
+++ haskell-pandoc-lua-engine-0.2.0.1/debian/rules  2024-01-04 
00:32:40.0 +
@@ -4,3 +4,8 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/hlibrary.mk
+
+ifneq (,$(filter $(DEB_BUILD_ARCH),loong64))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc-mcmodel=medium"
+endif
+

Bug#1069171: haskell-pandoc-lua-engine: Disable tests on loong64

[zhangdandan]

Close +1

Please close the bug.

On Wed, 17 Apr 2024 19:08:11 +0800 zhangdandan wrote:

> Source: haskell-pandoc-lua-engine
> Version: 0.2.0.1-1
> Severity: important
> Tags: ftbfs patch
> User: debian-loonga...@lists.debian.org
> Usertags: loong64
>
> Dear maintainers,
>
> The haskell-pandoc-lua-engine is blocked from building by haskell-pandoc
> in the Debian Package Auto-Building environment.
> Compiling the haskell-pandoc-lua-engine failed for loong64 in my 
local ENV.

> The error message is consistent with haskel-pandoc, and both are related
> to "relocation R_LARCH_B26 overflow .." during static linking in the
> test-pandoc stage.
> The build error log of haskell-pandoc-lua-engine from my local ENV is as
> follows,
> ```
> [6 of 6] Linking
> dist-ghc/build/test-pandoc-lua-engine/test-pandoc-lua-engine
> /usr/bin/ld.bfd:
> 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2.a(NonMovingMark.o): 


> relocation R_LARCH_B26 overflow 0xf61da41c
> Dump relocate record:
> stack top        relocation name        symbol
> at
> 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2.a(NonMovingMark.o)(.text+0xae4):

> ...
> 0x R_LARCH_B16    `.L172'
> ..
> ```
>
> There are two suggestions to solve "relocation R_LARCH_B26 overflow
> .." during static linking.
> 1.Add build rules to reduce binary size.
> 2.Disable tests in d/rules on loong64.
> The detailed information can be found from haskell-pandoc's Bug
> (#1069165) I just submitted.
>
> It is recommended to use "DEB_ENABLE_TESTS = no" in d/rules for loong64.
> Please consider the patch I attached.
> With the attached patch, the haskell-pandoc-lua-engine was built
> successfully in my local ENV.
> ```
> ..
> if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null;
> then dh_scour -plibghc-pandoc-lua-engine-prof ; fi
> dh_md5sums -plibghc-pandoc-lua-engine-prof
> dh_builddeb -plibghc-pandoc-lua-engine-prof
> dpkg-deb: building package 'libghc-pandoc-lua-engine-prof' in
> '../libghc-pandoc-lua-engine-prof_0.2.0.1-1_loong64.deb'.
>  dpkg-genbuildinfo
> -O../haskell-pandoc-lua-engine_0.2.0.1-1_loong64.buildinfo
>  dpkg-genchanges -O../haskell-pandoc-lua-engine_0.2.0.1-1_loong64.changes
> ```
>
> Your opinions are welcome.
>
> Thanks,
> Dandan Zhang

Bug#1071169: haskell-pandoc: Use extra --ghc-options and enable tests in d/rules on loong64

[zhangdandan]

Source: haskell-pandoc
Version: 3.1.3-2
Severity: important
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the haskell-pandoc failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
[58 of 58] Linking dist-ghc/build/test-pandoc/test-pandoc
/usr/bin/ld.bfd:
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2_thr.a(NonMovingMark.thr_o): 


relocation R_LARCH_B26 overflow 0xf5fec6a4
Dump relocate record:
stack top    relocation name    symbol
at
/usr/lib/gcc/loongarch64-linux-gnu/13/../../../loongarch64-linux-gnu/crt1.o(.text+0x0):
...
0x R_LARCH_NONE    `' + 3(0x3)
..
```

The Full log can be found at
https://buildd.debian.org/status/logs.php?pkg=haskell-pandoc=3.1.3-1=loong64.

The reason for the above error is that "relocation R_LARCH_B26 overflow
.." occurs during static linking in the test-pandoc stage.
Currently we have a verified method, don't need to skip test cases to 
solve "relocation R_LARCH_B26

overflow .." during static linking.
The verified method is as follows,
We need to add extra --ghc-options in d/rules on loong64 to reduce 
binary size.

```
diff --git 
a/home/pandoc-3/haskell-pandoc/again/haskell-pandoc-3.1.3/debian/rules 
b/debian/rules

index cacf45d..7542c81 100755
--- a/home/pandoc-3/haskell-pandoc/again/haskell-pandoc-3.1.3/debian/rules
+++ b/debian/rules
@@ -2,9 +2,8 @@

 DEB_ENABLE_TESTS = yes

-# Disable tests on loong64, see https://bugs.debian.org/1069165
-ifneq (,$(filter $(DEB_HOST_ARCH_CPU), loong64))
-DEB_ENABLE_TESTS = no
+ifneq (,$(filter $(DEB_BUILD_ARCH),loong64))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc-mcmodel=medium"
 endif
```

Meanwhile, you can also consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff --git a/again/haskell-pandoc-3.1.3/debian/rules 
b/haskell-pandoc-3.1.3/debian/rules
index cacf45d..7542c81 100755
--- a/again/haskell-pandoc-3.1.3/debian/rules
+++ b/haskell-pandoc-3.1.3/debian/rules
@@ -2,9 +2,8 @@
 
 DEB_ENABLE_TESTS = yes
 
-# Disable tests on loong64, see https://bugs.debian.org/1069165
-ifneq (,$(filter $(DEB_HOST_ARCH_CPU), loong64))
-DEB_ENABLE_TESTS = no
+ifneq (,$(filter $(DEB_BUILD_ARCH),loong64))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc-mcmodel=medium"
 endif
 
 include /usr/share/cdbs/1/rules/debhelper.mk

Bug#1071167: haskell-zlib: Use extra --ghc-options in d/rules on loong64

[zhangdandan]

Source: haskell-zlib
Version: 0.6.3.0-2
Severity: important
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the haskell-pandoc failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
[58 of 58] Linking dist-ghc/build/test-pandoc/test-pandoc
/usr/bin/ld.bfd:
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2_thr.a(NonMovingMark.thr_o): 


relocation R_LARCH_B26 overflow 0xf5fec6a4
Dump relocate record:
stack top    relocation name    symbol
at
/usr/lib/gcc/loongarch64-linux-gnu/13/../../../loongarch64-linux-gnu/crt1.o(.text+0x0):
...
0x R_LARCH_NONE    `' + 3(0x3)
..
```

The Full log can be found at
https://buildd.debian.org/status/logs.php?pkg=haskell-pandoc=3.1.3-1=loong64.

After analysis, we need to add extra --ghc-options in d/rules on loong64 
to increase jump-instructions' range.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru haskell-zlib-0.6.3.0/debian/rules haskell-zlib-0.6.3.0/debian/rules
--- haskell-zlib-0.6.3.0/debian/rules   2021-11-27 12:52:06.0 +
+++ haskell-zlib-0.6.3.0/debian/rules   2023-08-27 09:40:15.0 +
@@ -4,3 +4,8 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/hlibrary.mk
+
+ifneq (,$(filter $(DEB_BUILD_ARCH),loong64))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc-mcmodel=medium"
+endif
+

Bug#1070849: onetbb: FTBFS: Fix testcases failed on loong64

[zhangdandan]

Source: onetbb
Version: 2021.11.0-2
Severity: normal
Tags: FTBFS patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the onetbb failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
99% tests passed, 1 tests failed out of 137

Total Test time (real) = 233.63 sec

The following tests FAILED:
    133 - test_malloc_whitebox (Failed)
Errors while running CTest
FAILED: CMakeFiles/test.util
```
The full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=onetbb=2021.11.0-2=loong64.


For loongarch64, the size of the huge page I got from /proc/meminfo is 
32768 kB.

```
$ cat /proc/meminfo |grep Hugepagesize
Hugepagesize:  32768 kB
$ uname -m
loongarch64
```

I have adjusted the page size of HUGE_PAGE_SIZE for loongarch64 in 
onetbb package.

I have built successfully on my local ENV and test cases passed.
```
137/137 Test #137: test_malloc_new_handler .. Passed    
0.04 sec

100% tests passed, 0 tests failed out of 137
Total Test time (real) = 332.60 sec
```

The pull request for loongarch64 has been merged in onetbb upstream.
https://github.com/oneapi-src/oneTBB/pull/850/files.
https://github.com/oneapi-src/oneTBB/pull/1230/files.

Meanwhile, you can also consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Adjust HUGE_PAGE_SIZE size for loongarch64 
Last-Update: 2024-05-10

--- onetbb-2021.11.0.orig/src/tbbmalloc/tbbmalloc_internal.h
+++ onetbb-2021.11.0/src/tbbmalloc/tbbmalloc_internal.h
@@ -102,7 +102,11 @@ void suppress_unused_warning( const T& )
 /*
  * Default huge page size
  */
+#if defined __loongarch64
+static const size_t HUGE_PAGE_SIZE = 32 * 1024 * 1024;
+#else
 static const size_t HUGE_PAGE_SIZE = 2 * 1024 * 1024;
+#endif
 
 /** End of global default constants */
 
--- onetbb-2021.11.0.orig/test/tbbmalloc/test_malloc_whitebox.cpp
+++ onetbb-2021.11.0/test/tbbmalloc/test_malloc_whitebox.cpp
@@ -1257,7 +1257,11 @@ void TestTHP() {
 scalable_allocation_mode(USE_HUGE_PAGES, 1);
 REQUIRE_MESSAGE(hugePages.isEnabled, "Huge pages should be enabled via scalable_allocation_mode");
 
+#if defined __loongarch64
+const int HUGE_PAGE_SIZE = 32 * 1024 * 1024;
+#else
 const int HUGE_PAGE_SIZE = 2 * 1024 * 1024;
+#endif
 
 // allocCount transparent huge pages should be allocated
 const int allocCount = 10;

Bug#1070097: drawterm-9front: FTBFS: add support for loongarch64

[zhangdandan]

Source: drawterm-9front
Version: 1.15.1+dfsg-4.1
Severity: normal
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the drawterm-9front failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
make[3]: Leaving directory '/<>/libip'
arch=`uname -m | sed -e 's/i.86/386/' \
         -e 's/Power Macintosh/power/' \
         -e 's/x86_64/amd64/' \
         -e 's/armv[567].*/arm/' \
         -e 's/\(aarch64\|armv8l\)/arm64/'`; \
(cd posix-$arch &&  make)
/bin/sh: 6: cd: can't cd to posix-loongarch64
make[2]: *** [Make.unix:22: libmachdep.a] Error 2
..
```

The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=drawterm-9front=0%7Egit20220608.bee4db6-3=loong64.


I have added support for loongarch to drawterm-9front upstream and built 
successfully on my local ENV.
The pull request of the support for loongarch64, please see 
https://github.com/9fans/drawterm/pull/15.

Please review.

In addition, If you need a extra patch to Debian drawterm-9front 
package, you can contact me.

Your opinions are welcome.

Thanks,
Dandan Zhang

Bug#1069887: quickfix: FTBFS: add support for loongarch64

[zhangdandan]

Source: quickfix
Version: 1.15.1+dfsg-4.1
Severity: normal
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the quickfix failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
In file included from ./double-conversion/diy-fp.h:31,
 from double-conversion/diy-fp.cc:29,
 from FieldConvertors.cpp:37:
./double-conversion/utils.h:84:2: error: #error Target architecture was 
not detected as supported by Double-Conversion.
   84 | #error Target architecture was not detected as supported by 
Double-Conversion.

  |  ^
..
```

The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=quickfix=1.15.1%2Bdfsg-4.1=loong64.


I have added support for loongarch in quickfix package and built 
successfully on my local ENV.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add support for loongarch64 
Last-Update: 2024-04-26

--- quickfix-1.15.1+dfsg.orig/src/C++/double-conversion/utils.h
+++ quickfix-1.15.1+dfsg/src/C++/double-conversion/utils.h
@@ -69,7 +69,7 @@
 defined(__sparc__) || defined(__sparc) || defined(__s390__) || \
 defined(__SH4__) || defined(__alpha__) || \
 defined(_MIPS_ARCH_MIPS32R2) || \
-defined(__AARCH64EL__) || defined(__aarch64__)
+defined(__AARCH64EL__) || defined(__aarch64__) || defined(__loongarch64)
 #define DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS 1
 #elif defined(__mc68000__)
 #undef DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS

Bug#1059960: flash-kernel: Please add loong64 binary output for Loongarch

[zhangdandan]

Dear Maintainer,

On Thu, 4 Jan 2024 14:26:16 +0800 yalingfang wrote:

> Source: flash-kernel
> Version: 3.107
> Severity: wishlist
> Tags: patch
> User: debian-loonga...@lists.debian.org
> Usertags: loong64
>
>
> Dear Maintainer,
>      Currently no loong64 binary output for flash-kernel in Loongarch 
env.

> The buildd link is following:
> https://buildd.debian.org/status/package.php?p=flash-kernel=sid
>
> I have verified and compiled pass by adding loong64 to debian/control
> file in my local env.

We need to update the patch to support loongarch64.
Please consider the patch I attached.
Could you add the loongarch64 support in the next upload?

Thanks,
Dandan Zhang


diff -Nru flash-kernel-3.107/debian/control flash-kernel-3.107/debian/control
--- flash-kernel-3.107/debian/control   2023-04-19 21:02:35.0 +
+++ flash-kernel-3.107/debian/control   2023-04-19 21:12:53.0 +
@@ -11,7 +11,7 @@
 Rules-Requires-Root: no
 
 Package: flash-kernel
-Architecture: arm64 armel armhf riscv64
+Architecture: arm64 armel armhf riscv64 loong64
 Depends: ${misc:Depends},
  devio,
  initramfs-tools (>= 0.92f),
@@ -31,7 +31,7 @@
 Priority: standard
 Package-Type: udeb
 Build-Profiles: 
-Architecture: arm64 armel armhf riscv64
+Architecture: arm64 armel armhf riscv64 loong64
 XB-Subarchitecture: kirkwood orion5x s3c24xx mx5 generic
 Provides: bootable-system
 Depends: cdebconf-udeb, installed-base

Bug#1069824: paryfor: FTBFS: add support for loongarch64

[zhangdandan]

Source: paryfor
Version: 0.1-7
Severity: normal
Tags: FTBFS patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the paryfor failed (failed five times in the past) for loong64 
in the Debian Package Auto-Building environment.

The error log is as follows,
```
In file included from /<>/test.cpp:5:
/<>/paryfor.hpp:64:2: error: #error "Unknown CPU architecture."
   64 | #error "Unknown CPU architecture."
  |  ^
..
```

The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=paryfor=0.1-7=loong64.


I have added support for loongarch in paryfor package and built 
successfully on my local ENV.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add support for loongarch64 
Last-Update: 2024-04-25

--- paryfor-0.1.orig/paryfor.hpp
+++ paryfor-0.1/paryfor.hpp
@@ -60,6 +60,15 @@ static inline void spin_loop_pause() noe
 }
 } // namespace atomic_queue
 } // namespace paryfor
+#elif defined(__loongarch64)
+namespace paryfor {
+namespace atomic_queue {
+constexpr int CACHE_LINE_SIZE = 64;
+static inline void spin_loop_pause() noexcept {
+asm volatile ("nop" ::: "memory");
+}
+} // namespace atomic_queue
+} // namespace paryfor
 #else
 #error "Unknown CPU architecture."
 #endif

Bug#1069823: libmsv: FTBFS: update the outdated config.{guess,sub} to recognize the LoongArch

[zhangdandan]

Source: libmsv
Version: 1.1.1-4
Severity: normal
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the libmsv failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
UNAME_MACHINE = loongarch64
UNAME_RELEASE = 6.1.27
UNAME_SYSTEM  = Linux
UNAME_VERSION = #6 SMP PREEMPT Mon Jul 31 10:17:50 UTC 2023
configure: error: cannot guess build type; you must specify one
make: *** [debian/rules:31: stamp-build] Error 1
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned 
exit status 2

```

The Full log can be found at [1].

The version of config.guess and config.sub in the libmsv package are too 
old for the LoongArch architecture.
LoongArch architecture has been supported in config upstream [2] and 
autotools-dev source package [3].


Please consider the patch I have attached.
Your opinions are welcome.


[1]:https://buildd.debian.org/status/logs.php?pkg=libmsv=1.1.1-4=loong64
[2]:https://git.savannah.gnu.org/cgit/config.git/commit/?id=20403c5701973a4cbd7e0b4bbeb627fcd424a0f1
[3]:https://packages.debian.org/bookworm/autotools-dev


Thanks,
Dandan Zhang

diff -Nru libmsv-1.1.1/debian/rules libmsv-1.1.1/debian/rules
--- libmsv-1.1.1/debian/rules   2023-08-10 16:23:39.0 +
+++ libmsv-1.1.1/debian/rules   2023-08-10 16:23:39.0 +
@@ -28,6 +28,7 @@
 build-indep: build-arch
 build-arch: stamp-build
 stamp-build: configure
+   dh_update_autotools_config
./configure $(CONFARGS) --prefix=/usr CFLAGS="$(CFLAGS)" 
CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)"
$(MAKE)
doxygen libmsvdox.cfg

Bug#1069769: haskell-versions: Disable RTS -N on loong64

[zhangdandan]

Source: haskell-versions
Version: 6.0.2-1
Severity: normal
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the haskell-versions failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
Running 1 test suites...
Test suite versions-test: RUNNING...
versions-test: unknown RTS option: -N
versions-test:
versions-test: Usage:   [+RTS  | -RTS ] ... 
--RTS 

versions-test:
```

The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=haskell-versions=6.0.2-1=loong64.


We need to disable -with-rtsopts=-N option on loongarch64.
I have built haskell-versions successfully in my local ENV.
Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Disable RTS -N on loong64 
Last-Update: 2024-04-24

--- haskell-versions-6.0.2.orig/versions.cabal
+++ haskell-versions-6.0.2/versions.cabal
@@ -58,7 +58,7 @@ test-suite versions-test
   type:   exitcode-stdio-1.0
   main-is:Test.hs
   hs-source-dirs: test
-  if arch(arm) || arch(mips) || arch(s390x) || arch(i386) || arch(riscv64)
+  if arch(arm) || arch(mips) || arch(s390x) || arch(i386) || arch(riscv64) || arch(loongarch64)
 ghc-options:-threaded
   else
 ghc-options:-threaded -with-rtsopts=-N

Bug#1069718: ldc: add build support for loongarch64

[zhangdandan]

Source: ldc
Version: 1:1.36.0-2
Severity: normal
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

I have added build support for loongarch in ldc package.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff --git a/../org/ldc-1.36.0/debian/control b/debian/control
index ef38a72..c63b587 100644
--- a/../org/ldc-1.36.0/debian/control
+++ b/debian/control
@@ -27,7 +27,7 @@ Vcs-Git: https://salsa.debian.org/d-team/ldc.git
 Vcs-Browser: https://salsa.debian.org/d-team/ldc
 
 Package: ldc
-Architecture: amd64 arm64 armhf i386 riscv64
+Architecture: amd64 arm64 armhf i386 riscv64 loong64
 Provides: d-compiler,
   d-v2-compiler
 Depends: libphobos2-ldc-shared-dev (= ${binary:Version}),
@@ -42,7 +42,7 @@ Description: LLVM D Compiler
 
 Package: libphobos2-ldc-shared106
 Section: libs
-Architecture: amd64 arm64 armhf i386 riscv64
+Architecture: amd64 arm64 armhf i386 riscv64 loong64
 Multi-Arch: same
 Depends: ${misc:Depends},
  ${shlibs:Depends}
@@ -57,7 +57,7 @@ Description: LLVM D Compiler - Standard and runtime libraries
 
 Package: libphobos2-ldc-shared-dev
 Section: libdevel
-Architecture: amd64 arm64 armhf i386 riscv64
+Architecture: amd64 arm64 armhf i386 riscv64 loong64
 Depends: libphobos2-ldc-shared106 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}

Bug#1069717: dh-dlang: add build support for loongarch64

[zhangdandan]

Source: dh-dlang
Version: 0.6.6
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

I have added build support for loongarch in dh-dlang package.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru dh-dlang-0.6.6/debian/control dh-dlang-0.6.6/debian/control
--- dh-dlang-0.6.6/debian/control   2024-02-18 21:52:28.0 +
+++ dh-dlang-0.6.6/debian/control   2024-02-18 21:52:28.0 +
@@ -25,9 +25,9 @@
  for the current architecture.
 
 Package: default-d-compiler
-Architecture: amd64 arm64 i386 armhf s390x riscv64 ppc64el x32
+Architecture: amd64 arm64 i386 armhf s390x riscv64 loong64 ppc64el x32
 Depends: gdc (>= 4:12) [armhf s390x ppc64el x32],
- ldc (>= 1:1.36) [amd64 arm64 i386 riscv64],
+ ldc (>= 1:1.36) [amd64 arm64 i386 riscv64 loong64],
  ${misc:Depends}
 Description: Default D compiler (metapackage)
  This is a metapackage installing the default D compiler in Debian
diff -Nru dh-dlang-0.6.6/dlang-flags.mk dh-dlang-0.6.6/dlang-flags.mk
--- dh-dlang-0.6.6/dlang-flags.mk   2024-02-18 21:13:50.0 +
+++ dh-dlang-0.6.6/dlang-flags.mk   2024-02-18 21:52:28.0 +
@@ -24,7 +24,7 @@
 
 # set DC to the LDC compiler on platforms where we should use it,
 # and also set the right D flags on those architectures (since LDC uses 
different flag names)
-ifneq (,$(filter $(DEB_HOST_ARCH), amd64 arm64 i386 riscv64))
+ifneq (,$(filter $(DEB_HOST_ARCH), amd64 arm64 i386 riscv64 loong64))
 # only set LDC build flags if our compiler is LDC
 ifeq ($(DC_LDC_FOUND),yes)
 DC = ldc2

Bug#1069714: gcc-defaults: enable build gdc and gm2 for loong64

[zhangdandan]

Source: gcc-defaults
Version: 1.217
Severity: normal
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

For loong64, the D, Ada, Modula-2 modules have been supported in gcc-14 
14-20240330-1.
I duploaded the gdc-14, gnat-14 and other packages built from gcc-14 
14-20240330-1 that support the loong64 architecture for the first time 
to debian ports.


Due to "default to GCC 13" is used in gcc-defaults 1.214, we need to 
enable build gdc and gm2 for loong64 in gcc-defaults 1.217.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru gcc-defaults-1.217/debian/control gcc-defaults-1.217/debian/control
--- gcc-defaults-1.217/debian/control   2024-01-31 13:17:32.0 +
+++ gcc-defaults-1.217/debian/control   2024-01-31 13:17:32.0 +
@@ -2740,6 +2740,39 @@
  This is a dependency package providing the default GNU Fortran 95
  cross-compiler for the loong64 architecture.
 
+Package: gdc-loongarch64-linux-gnu
+Priority: optional
+Architecture: loong64 
+Multi-Arch: foreign
+Depends: cpp-loongarch64-linux-gnu (>= ${version:cpp}),
+  gdc-${pv:gdc}-loongarch64-linux-gnu ${reqv:gdc},
+  ${misc:Depends}
+Breaks: gdc (<< 4:13.2.0-3)
+Replaces: gdc (<< 4:13.2.0-3)
+Description: GNU D compiler (based on GCC) for the loong64 architecture
+ This is the GNU D compiler, which compiles D on platforms supported by
+ the gcc compiler. It uses the gcc backend to generate optimized code.
+ .
+ This is a dependency package providing the default GNU D cross-compiler
+ for the loong64 architecture.
+
+Package: gm2-loongarch64-linux-gnu
+Priority: optional
+Architecture: loong64 
+Multi-Arch: foreign
+Depends: cpp-loongarch64-linux-gnu (= ${version:cpp}),
+  gm2-${pv:gm2}-loongarch64-linux-gnu ${reqv:gm2},
+  ${misc:Depends}
+Breaks: gm2 (<< 4:13.2.0-3)
+Replaces: gm2 (<< 4:13.2.0-3)
+Description: GNU Modula-2 compiler (based on GCC) for the loong64 architecture
+ This is the GNU Modula-2 compiler, which compiles Modula-2 on platforms
+ supported by the gcc compiler. It uses the gcc backend to generate optimized
+ code.
+ .
+ This is a dependency package providing the default GNU Modula-2 cross-compiler
+ for the loong64 architecture.
+
 Package: cpp-powerpc-linux-gnu
 Priority: optional
 Architecture: powerpc
diff -Nru gcc-defaults-1.217/debian/rules gcc-defaults-1.217/debian/rules
--- gcc-defaults-1.217/debian/rules 2024-01-31 13:17:32.0 +
+++ gcc-defaults-1.217/debian/rules 2024-01-31 13:17:32.0 +
@@ -231,11 +231,11 @@
$(all_archs_mips)
 
 gcc13_archs =
-gcc14_archs  = alpha arc amd64 armel armhf arm64 hppa i386 ia64 m68k or1k 
powerpc ppc64 ppc64el riscv64 s390 s390x sh4 sparc sparc64 x32 hurd-amd64 
hurd-i386 kfreebsd-amd64 kfreebsd-i386 \
+gcc14_archs  = alpha arc amd64 armel armhf arm64 hppa i386 ia64 loong64 m68k 
or1k powerpc ppc64 ppc64el riscv64 s390 s390x sh4 sparc sparc64 x32 hurd-amd64 
hurd-i386 kfreebsd-amd64 kfreebsd-i386 \
 $(all_archs_mips)
 
 gnat13_archs  =
-gnat14_archs  = alpha amd64 armel armhf arm64 hppa i386 ia64 m68k or1k powerpc 
ppc64 ppc64el s390 s390x sh4 sparc sparc64 x32 hurd-amd64 hurd-i386 
kfreebsd-amd64 kfreebsd-i386 \
+gnat14_archs  = alpha amd64 armel armhf arm64 hppa i386 ia64 loong64 m68k or1k 
powerpc ppc64 ppc64el s390 s390x sh4 sparc sparc64 x32 hurd-amd64 hurd-i386 
kfreebsd-amd64 kfreebsd-i386 \
 $(all_archs_mips)
 
 # CV_XXX is the complete version number, including the release, without epoch
@@ -338,7 +338,7 @@
$(all_archs_mips) \
powerpc ppc64 ppc64el riscv64 s390 s390x sparc sparc64 x32
 
-d_archs = amd64 arm64 armel armhf i386 \
+d_archs = amd64 arm64 armel armhf i386 loong64 \
$(all_archs_mips) \
powerpc ppc64 ppc64el riscv64 s390x x32
 phobos_archs = $(filter-out powerpc ppc64 ppc64el, $(d_archs))
@@ -347,7 +347,7 @@
 
 d_multilib_archs = $(filter $(d_archs), $(filter-out armel sparc64, 
$(multilib_archs)))
 
-ada_archs = alpha amd64 arm64 armel armhf hppa i386 ia64 m68k \
+ada_archs = alpha amd64 arm64 armel armhf hppa i386 ia64 m68k loong64 \
$(all_archs_mips) \
powerpc ppc64 ppc64el riscv64 s390 s390x sh4 sparc sparc64 \
kfreebsd-amd64 kfreebsd-i386 hurd-amd64 hurd-i386
@@ -357,7 +357,7 @@
 
 hppa64_archs = amd64 hppa i386 x32
 
-m2_archs = alpha arc amd64 arm64 armel armhf i386 ia64 \
+m2_archs = alpha arc amd64 arm64 armel armhf i386 ia64 loong64 \
$(all_archs_mips) \
ppc64el riscv64 s390 s390x sparc64
 
@@ -368,6 +368,7 @@
   HOST_ARCHS_arm64 = amd64 i386 x32 ppc64el s390x
   HOST_ARCHS_armhf = amd64 i386 x32 arm64 ppc64el s390x
   HOST_ARCHS_i386 = amd64 arm64 ppc64el x32 s390x
+  HOST_ARCHS_loong64 = amd64 i386 x32 arm64 ppc64el s390x
   ifeq ($(vendor),Ubuntu)
 HOST_ARCHS_powerpc = amd64 arm64 i386 x32 ppc64el s390x
   endif
@@ -517,13 +518,11 @@
gccgo-multilib-arm-linux-gnueabihf \
gdc-alpha-linux-gnu \

Bug#1050994: xutils-dev: Please add support for loong64

[zhangdandan]

User: debian-loonga...@lists.debian.org
Usertags: loong64
X-Debbugs-Cc: 
debian-loonga...@lists.debian.org,zhangjial...@loongson.cn,zhangdan...@loongson.cn


Dear maintainers,

On Fri, 01 Sep 2023 10:07:02 +0200 John Paul Adrian Glaubitz wrote:

> Source: xutils-dev
> Version: 1:7.7+6.1
> Severity: normal
> User: debian-de...@lists.debian.org
> Usertags: loong64
> X-Debbugs-Cc: 
debian-de...@lists.debian.org,zhangjial...@loongson.cn,zhangdan...@loongson.cn

>
> Hi!
>
> Multiple X packages currently fail to build from source on loong64 due
> to missing architecture support in xutils-dev [1]:
>
> gcc: warning: LinuxMachineDefines: linker input file unused because 
linking not done
> gcc: error: LinuxMachineDefines: linker input file not found: No such 
file or directory

>
> This should be fixed in a similar fashion for loong64 as it has been 
done for
> riscv64 in [2]. I have CC'ed two engineers from Loongson to make them 
aware

> of the bug so they can work on a patch to add loong64 support.
>
> Thanks,
> Adrian
>
> > [1] 
https://buildd.debian.org/status/fetch.php?pkg=xaw3d=loong64=1.5%2BF-1.1=1693526902=0

> > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026002
>
For loong64, many packages[1] failed to compile and are currently in the 
"Build-Attempted" state in the Debian Package Auto-Building environment.

The error log is related to xutils-dev package.

LoongArch architecture has been supported in the xorg/util/cf upstream.
The merge-request can be found at 
https://gitlab.freedesktop.org/xorg/util/cf/-/commit/b6ece89e454a94c96e6f4592fe58ac6d534f16f3.

Signed-of-by: WANG Xuerui.

In addition, LoongArch architecture has been added in xutils-dev 
(1:7.7+7) version[2].


Would it be possible to update "1:7.7+7 UNRELEASED" to "untable" in the 
next upload?

Your opinions are welcome.

[1]: https://buildd.debian.org/status/architecture.php?a=loong64=sid
[2]: 
https://salsa.debian.org/xorg-team/app/xutils-dev/-/blob/debian-unstable/debian/changelog


Thanks,
Dandan Zhang

Bug#1069179: pandoc: use "--enable-executable-dynamic" in d/rules to reduce binary size on loong64

[zhangdandan]

Source: pandoc
Version: 3.1.3+ds-2
Severity: important
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64
X-Debbugs-Cc: wanghon...@loongson.cn, zhangjial...@loongson.cn, 
fanp...@loongson.cn


Dear maintainers,

The pandoc is blocked from building by haskell-pandoc and 
haskell-pandoc-lua-engine in the Debian Package Auto-Building environment.
I have built haskell-pandoc and haskell-pandoc-lua-engine locally, and 
then compiling pandoc for loong64 in my local ENV failed.


The error message is related to "relocation R_LARCH_B26 overflow .." 
during static linking when built pandoc binary.

The build error log of pandoc from my local ENV is as follows,
```
[4 of 4] Linking dist-ghc/build/pandoc/pandoc
/usr/bin/ld.bfd: 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2_thr.a(NonMovingMark.thr_o): 
relocation R_LARCH_B26 overflow 0xf62f45e4

Dump relocate record:
stack top        relocation name        symbol
at 
/usr/lib/gcc/loongarch64-linux-gnu/13/../../../loongarch64-linux-gnu/crt1.o(.text+0x0):

...
0x R_LARCH_NONE    `' + 3(0x3)
..
```

It is recommended to use "--enable-executable-dynamic" in d/rules to 
reduce binary size on loong64.
The parameter "--enable-executable-dynamic" means "enable dynamic 
linking of executable files".

Please consider the patch I attached.
With the attached patch, the pandoc was built successfully in my local ENV.
```
..
if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; 
then dh_scour -ppandoc ; fi

dh_md5sums -ppandoc
dh_builddeb -ppandoc
dpkg-deb: building package 'pandoc' in '../pandoc_3.1.3+ds-2_loong64.deb'.
 dpkg-genbuildinfo -O../pandoc_3.1.3+ds-2_loong64.buildinfo
 dpkg-genchanges -O../pandoc_3.1.3+ds-2_loong64.changes
```

Your opinions are welcome.
In addition, before the pandoc was built for loong64 in the Debian 
Package Auto-Building environment, could I dupload the pandoc compiled 
locally using "-enable-executable-dynamic" to the 
debian-ports/pool-loong64 repository?

Looking forward to your reply.

Thanks,
Dandan Zhang

diff -Nru pandoc-3.1.3+ds/debian/rules pandoc-3.1.3+ds/debian/rules
--- pandoc-3.1.3+ds/debian/rules2023-12-21 20:13:11.0 +
+++ pandoc-3.1.3+ds/debian/rules2024-01-07 00:52:39.0 +
@@ -58,6 +58,10 @@
 DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-O0"
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), loong64))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --enable-executable-dynamic 
+endif
+
 DEB_SETUP_GHC_CONFIGURE_ARGS += $(if $(filter 
nocheck,$(DEB_BUILD_OPTIONS)),,-ftests)
 
 DEB_INSTALL_DOCS_ALL += README.md

Bug#1069171: haskell-pandoc-lua-engine: Disable tests on loong64

[zhangdandan]

Source: haskell-pandoc-lua-engine
Version: 0.2.0.1-1
Severity: important
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The haskell-pandoc-lua-engine is blocked from building by haskell-pandoc 
in the Debian Package Auto-Building environment.

Compiling the haskell-pandoc-lua-engine failed for loong64 in my local ENV.
The error message is consistent with haskel-pandoc, and both are related 
to "relocation R_LARCH_B26 overflow .." during static linking in the 
test-pandoc stage.
The build error log of haskell-pandoc-lua-engine from my local ENV is as 
follows,

```
[6 of 6] Linking 
dist-ghc/build/test-pandoc-lua-engine/test-pandoc-lua-engine
/usr/bin/ld.bfd: 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2.a(NonMovingMark.o): 
relocation R_LARCH_B26 overflow 0xf61da41c

Dump relocate record:
stack top        relocation name        symbol
at 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2.a(NonMovingMark.o)(.text+0xae4):

...
0x R_LARCH_B16    `.L172'
..
```

There are two suggestions to solve "relocation R_LARCH_B26 overflow 
.." during static linking.

1.Add build rules to reduce binary size.
2.Disable tests in d/rules on loong64.
The detailed information can be found from haskell-pandoc's Bug 
(#1069165) I just submitted.


It is recommended to use "DEB_ENABLE_TESTS = no" in d/rules for loong64.
Please consider the patch I attached.
With the attached patch, the haskell-pandoc-lua-engine was built 
successfully in my local ENV.

```
..
if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; 
then dh_scour -plibghc-pandoc-lua-engine-prof ; fi

dh_md5sums -plibghc-pandoc-lua-engine-prof
dh_builddeb -plibghc-pandoc-lua-engine-prof
dpkg-deb: building package 'libghc-pandoc-lua-engine-prof' in 
'../libghc-pandoc-lua-engine-prof_0.2.0.1-1_loong64.deb'.
 dpkg-genbuildinfo 
-O../haskell-pandoc-lua-engine_0.2.0.1-1_loong64.buildinfo

 dpkg-genchanges -O../haskell-pandoc-lua-engine_0.2.0.1-1_loong64.changes
```

Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru haskell-pandoc-lua-engine-0.2.0.1/debian/rules 
haskell-pandoc-lua-engine-0.2.0.1/debian/rules
--- haskell-pandoc-lua-engine-0.2.0.1/debian/rules  2024-01-04 
00:32:40.0 +
+++ haskell-pandoc-lua-engine-0.2.0.1/debian/rules  2024-01-04 
00:32:40.0 +
@@ -1,6 +1,9 @@
 #!/usr/bin/make -f
 
 DEB_ENABLE_TESTS = yes
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), loong64))
+DEB_ENABLE_TESTS = no
+endif
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/hlibrary.mk

Bug#1069165: haskell-pandoc: Disable tests on loong64

[zhangdandan]

Source: haskell-pandoc
Version: 3.1.3-1
Severity: important
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the haskell-pandoc failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
[58 of 58] Linking dist-ghc/build/test-pandoc/test-pandoc
/usr/bin/ld.bfd: 
/usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2_thr.a(NonMovingMark.thr_o): 
relocation R_LARCH_B26 overflow 0xf5fec6a4

Dump relocate record:
stack top        relocation name        symbol
at 
/usr/lib/gcc/loongarch64-linux-gnu/13/../../../loongarch64-linux-gnu/crt1.o(.text+0x0):

...
0x R_LARCH_NONE    `' + 3(0x3)
..
```

The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=haskell-pandoc=3.1.3-1=loong64.


The reason for the above error is that "relocation R_LARCH_B26 overflow 
.." occurs during static linking in the test-pandoc stage.
Currently we have two suggestions to solve "relocation R_LARCH_B26 
overflow .." during static linking.


1.Add build rules to reduce binary size.
Use "DEB_SETUP_GHC_CONFIGURE_ARGS += --enable-executable-dynamic -O2" 
when compiling haskell-pandoc for loong64.

The parameters are explained as follows,
"--enable-executable-dynamic" means "Enable Executable dynamic linking".
"-O, --enable-optimization[=n]" means "Build with optimization (n is 
0--2, default is 1)".


2.Disable tests in d/rules on loong64.
The error "relocation R_LARCH_B26 overflow .." occurs during the 
testing stage.

It is recommended to use "DEB_ENABLE_TESTS = no" in d/rules for loong64.
The haskell-pandoc was built successfully in my local ENV.
About disable tests in d/rules on loong64, please consider the below patch,
```
diff --git a/debian/rules b/debian/rules
index 6fbf01d..385f58e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,10 @@
 #!/usr/bin/make -f

 DEB_ENABLE_TESTS = yes
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), loong64))
+DEB_ENABLE_TESTS = no
+endif
+
```

The haskel-pandoc blocks the construction of pandoc.
And pandoc blocks the compilation of 103 packages.

Please help us to choose 1 of the 2 solutions I provided above.
Or help us to solve "relocation R_LARCH_B26 overflow ..".
Looking forward to your reply.

Thanks,
Dandan Zhang

Bug#1069141: efitools: FTBFS: add build support for loongarch64

[zhangdandan]

Source: efitools
Version: 1.9.2-3
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling efitools package failed on my local loong64 rootfs environment.
I have added build support for loongarch in efitools package.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add build support for loongarch64
Last-Update: 2024-04-17

--- efitools-1.9.2.orig/Make.rules
+++ efitools-1.9.2/Make.rules
@@ -10,6 +10,8 @@ else ifeq ($(ARCH),aarch64)
 ARCH3264 =
 else ifeq ($(ARCH),riscv64)
 ARCH3264 =
+else ifeq ($(ARCH),loongarch64)
+ARCH3264 =
 else ifeq ($(ARCH),arm)
 ARCH3264 =
 else
@@ -63,6 +65,10 @@ ifeq ($(ARCH),riscv64)
   FORMAT = -O binary
 endif
 
+ifeq ($(ARCH),loongarch64)
+  LDFLAGS += --defsym=EFI_SUBSYSTEM=0x0a
+endif
+
 %.efi: %.so
 	$(OBJCOPY) -j .text -j .sdata -j .data -j .dynamic -j .dynsym \
 		   -j .rel -j .rela -j .rel.* -j .rela.* -j .rel* -j .rela* \

Bug#1069138: sbsigntool: FTBFS: add support for loongarch

[zhangdandan]

Source: sbsigntool
Version: 0.9.4-3.1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling sbsigntool package failed on my local loong64 rootfs environment.
I have added support for loongarch in sbsigntool package.
In addition, we should add build support for loongarch.

The sbsigntool was built successfully in my local ENV.
Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru sbsigntool-0.9.4/debian/control sbsigntool-0.9.4/debian/control
--- sbsigntool-0.9.4/debian/control 2021-09-14 06:39:01.0 +
+++ sbsigntool-0.9.4/debian/control 2022-06-04 11:37:27.0 +
@@ -17,7 +17,7 @@
 Standards-Version: 4.5.1
 
 Package: sbsigntool
-Architecture: any-amd64 any-i386 arm64 armhf any-riscv64
+Architecture: any-amd64 any-i386 arm64 armhf any-riscv64 any-loong64
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Multi-Arch: foreign
 Description: Tools to manipulate signatures on UEFI binaries and drivers
diff -Nru 
sbsigntool-0.9.4/debian/patches/add-support-for-LoongArch-images.patch 
sbsigntool-0.9.4/debian/patches/add-support-for-LoongArch-images.patch
--- sbsigntool-0.9.4/debian/patches/add-support-for-LoongArch-images.patch  
1970-01-01 00:00:00.0 +
+++ sbsigntool-0.9.4/debian/patches/add-support-for-LoongArch-images.patch  
2022-06-04 11:37:27.0 +
@@ -0,0 +1,36 @@
+Description: Add support for LoongArch images
+ .
+ sbsigntool (0.9.4-3.1+loong64) unreleased; urgency=medium
+ .
+   * Add support for LoongArch images.
+Author: Dandan Zhang 
+---
+Last-Update: 2024-04-17
+
+--- sbsigntool-0.9.4.orig/src/coff/pe.h
 sbsigntool-0.9.4/src/coff/pe.h
+@@ -133,6 +133,8 @@
+ #define IMAGE_FILE_MACHINE_EBC   0x0ebc
+ #define IMAGE_FILE_MACHINE_I386  0x014c
+ #define IMAGE_FILE_MACHINE_IA64  0x0200
++#define IMAGE_FILE_MACHINE_LOONGARCH32   0x6232
++#define IMAGE_FILE_MACHINE_LOONGARCH64   0x6264
+ #define IMAGE_FILE_MACHINE_M32R  0x9041
+ #define IMAGE_FILE_MACHINE_M68K  0x0268
+ #define IMAGE_FILE_MACHINE_MIPS160x0266
+--- sbsigntool-0.9.4.orig/src/image.c
 sbsigntool-0.9.4/src/image.c
+@@ -240,11 +240,13 @@ static int image_pecoff_parse(struct ima
+   case IMAGE_FILE_MACHINE_AMD64:
+   case IMAGE_FILE_MACHINE_AARCH64:
+   case IMAGE_FILE_MACHINE_RISCV64:
++  case IMAGE_FILE_MACHINE_LOONGARCH64:
+   rc = image_pecoff_parse_64(image);
+   break;
+   case IMAGE_FILE_MACHINE_I386:
+   case IMAGE_FILE_MACHINE_THUMB:
+   case IMAGE_FILE_MACHINE_RISCV32:
++  case IMAGE_FILE_MACHINE_LOONGARCH32:
+   rc = image_pecoff_parse_32(image);
+   break;
+   default:
diff -Nru sbsigntool-0.9.4/debian/patches/series 
sbsigntool-0.9.4/debian/patches/series
--- sbsigntool-0.9.4/debian/patches/series  2022-06-04 11:36:09.0 
+
+++ sbsigntool-0.9.4/debian/patches/series  2022-06-04 11:37:27.0 
+
@@ -2,3 +2,4 @@
 fix-efi-arch-detection.patch
 0001-sbsigntool-add-support-for-RISC-V-images.patch
 OpenSSL3.patch
+add-support-for-LoongArch-images.patch

Bug#1068751: haskell-lift-type: Disable RTS -N on loong64

[zhangdandan]

Source: haskell-lift-type
Version: 0.1.1.1-1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the haskell-lift-type failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
Running 1 test suites...
Test suite lift-type-test: RUNNING...
lift-type-test: unknown RTS option: -N
lift-type-test:
lift-type-test: Usage:   [+RTS  | -RTS ] ... 
--RTS 

```

The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=haskell-lift-type=0.1.1.1-1=loong64.


We need to disable -with-rtsopts=-N option on loongarch64.
I have built haskell-lift-type successfully on my local ENV.
Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru haskell-lift-type-0.1.1.1/debian/patches/no-rts-n-on-loong64.patch 
haskell-lift-type-0.1.1.1/debian/patches/no-rts-n-on-loong64.patch
--- haskell-lift-type-0.1.1.1/debian/patches/no-rts-n-on-loong64.patch  
1970-01-01 00:00:00.0 +
+++ haskell-lift-type-0.1.1.1/debian/patches/no-rts-n-on-loong64.patch  
2023-08-28 14:25:22.0 +
@@ -0,0 +1,14 @@
+Description: disable -with-rtsopts=-N option on loongarch64
+Last-Update: 2024-04-10
+
+--- haskell-lift-type-0.1.1.1.orig/lift-type.cabal
 haskell-lift-type-0.1.1.1/lift-type.cabal
+@@ -34,7 +34,7 @@ test-suite lift-type-test
+   main-is: Spec.hs
+   hs-source-dirs:
+   test
+-  if arch(arm) || arch(mips) || arch(s390x) || arch(i386) || arch(riscv64)
++  if arch(arm) || arch(mips) || arch(s390x) || arch(i386) || arch(riscv64) || 
arch(loongarch64)
+ ghc-options: -threaded -rtsopts
+   else
+ ghc-options: -threaded -rtsopts -with-rtsopts=-N
diff -Nru haskell-lift-type-0.1.1.1/debian/patches/series 
haskell-lift-type-0.1.1.1/debian/patches/series
--- haskell-lift-type-0.1.1.1/debian/patches/series 2022-09-03 
12:32:28.0 +
+++ haskell-lift-type-0.1.1.1/debian/patches/series 2023-08-28 
14:25:22.0 +
@@ -1 +1,2 @@
 no-rts-n
+no-rts-n-on-loong64.patch

Bug#1059262: trilinos: add loongarch64 support

[zhangdandan]

Hi maintainers,

On Fri, 29 Mar 2024 09:53:53 +0800 zhangdandan wrote:

>
> The trilinos itself blocks the compilation of many packages.
> Based on the attached patch, the trilinos package was compiled
> successfully on my local loong64 rootfs environment.
> I have built 132 binary packages from trilinos on local ENV.
>
I have generated a debdiff for loong64.
Please consider the patch I have attached.
Could you enable loong64 support in debian/control in the next upload.
Looking forward to your reply.

In addition, if I need to submit a merge-request to 
https://salsa.debian.org/science-team/trilinos, please contact me in time.


Thanks,
Dandan Zhang
diff -Nru trilinos-13.2.0/debian/control trilinos-13.2.0/debian/control
--- trilinos-13.2.0/debian/control  2023-09-04 12:17:04.0 +
+++ trilinos-13.2.0/debian/control  2023-09-04 16:41:09.0 +
@@ -35,7 +35,7 @@
 Vcs-Browser: https://salsa.debian.org/science-team/trilinos
 
 Package: trilinos-all-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${misc:Depends}, ${mydevpackages}
@@ -50,7 +50,7 @@
  This package depends on all Trilinos development packages.
 
 Package: trilinos-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${misc:Depends}
@@ -65,7 +65,7 @@
  This package contains the development header and some makefile templates.
 
 Package: libtrilinos-amesos-13.2
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -77,7 +77,7 @@
  This package contains the dynamic libraries.
 
 Package: libtrilinos-amesos-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libdevel
 # Manually add libtrilinos-trilinosss-dev as dependency until
@@ -92,7 +92,7 @@
  This package provides headers.
 
 Package: libtrilinos-amesos2-13.2
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -104,7 +104,7 @@
  This package contains the dynamic libraries.
 
 Package: libtrilinos-amesos2-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libdevel
 # Manually add libtrilinos-trilinosss-dev as dependency until
@@ -119,7 +119,7 @@
  This package provides headers.
 
 Package: libtrilinos-anasazi-13.2
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -134,7 +134,7 @@
  This package contains the dynamic libraries.
 
 Package: libtrilinos-anasazi-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libdevel
 Depends: libtrilinos-anasazi-13.2 (= ${binary:Version}), trilinos-dev, 
${misc:Depends}
@@ -150,7 +150,7 @@
  This package provides headers.
 
 Package: libtrilinos-aztecoo-13.2
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -164,7 +164,7 @@
  This package contains the dynamic libraries.
 
 Package: libtrilinos-aztecoo-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libdevel
 Depends: liblapack-dev, libtrilinos-aztecoo-13.2 (= ${binary:Version}), 
trilinos-dev, ${misc:Depends}
@@ -179,7 +179,7 @@
  This package provides headers.
 
 Package: libtrilinos-belos-13.2
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -193,7 +193,7 @@
  This package contains the dynamic libraries.
 
 Package: libtrilinos-belos-dev
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libdevel
 Depends: libtrilinos-belos-13.2 (= ${binary:Version}), trilinos-dev, 
${misc:Depends}
@@ -210,7 +210,7 @@
  This package provides headers.
 
 Package: libtrilinos-epetra-13.2
-Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 ppc64el s390x ppc64 riscv64 loong64
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -222,7 +222,7 @@
  This package contains the dynamic lib

Bug#1068690: rust-jemalloc-sys: FTBFS: add support for loongarch64

[zhangdandan]

Source: rust-jemalloc-sys
Version: 0.3.2-2
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the rust-jemalloc-sys failed for loong64 in the Debian Package 
Auto-Building environment.

The error log is as follows,
```
[jemalloc-sys 0.3.2] In file included from 
include/jemalloc/internal/size_classes.h:6,
[jemalloc-sys 0.3.2]  from 
../jemalloc/include/jemalloc/internal/tcache_types.h:4,
[jemalloc-sys 0.3.2]  from 
../jemalloc/include/jemalloc/internal/jemalloc_internal_includes.h:46,

[jemalloc-sys 0.3.2]  from ../jemalloc/src/bin.c:2:
[jemalloc-sys 0.3.2] 
../jemalloc/include/jemalloc/internal/jemalloc_internal_types.h:114:6: 
error: #error "Unknown minimum alignment for architecture; specify via "
[jemalloc-sys 0.3.2]   114 | #    error "Unknown minimum alignment for 
architecture; specify via "

[jemalloc-sys 0.3.2]   |  ^
```
The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=rust-jemalloc-sys=0.3.2-2=loong64.


I have added loongarch support in rust-jemalloc-sys package. Please 
consider the patch I attached.
In addition, the LoongArch architecture has been supported by jemalloc 
upstream, pelase see https://github.com/jemalloc/jemalloc.
Would it be possible to include the support for LoongArch in the next 
upload?

Your opinions are welcome.

Thanks,
Dandan Zhang
Description: Add loongarch support
Last-Update: 2024-04-09

--- rust-jemalloc-sys-0.3.2.orig/jemalloc/include/jemalloc/internal/jemalloc_internal_types.h
+++ rust-jemalloc-sys-0.3.2/jemalloc/include/jemalloc/internal/jemalloc_internal_types.h
@@ -110,6 +110,9 @@ typedef int malloc_cpuid_t;
 #  ifdef __le32__
 #define LG_QUANTUM		4
 #  endif
+#  ifdef __loongarch__
+#define LG_QUANTUM		4
+#  endif
 #  ifndef LG_QUANTUM
 #error "Unknown minimum alignment for architecture; specify via "
 	 "--with-lg-quantum"
--- rust-jemalloc-sys-0.3.2.orig/rep/include/jemalloc/internal/quantum.h
+++ rust-jemalloc-sys-0.3.2/rep/include/jemalloc/internal/quantum.h
@@ -61,6 +61,9 @@
 #  ifdef __le32__
 #define LG_QUANTUM		4
 #  endif
+#  ifdef __loongarch__
+#define LG_QUANTUM		4
+#  endif
 #  ifndef LG_QUANTUM
 #error "Unknown minimum alignment for architecture; specify via "
 	 "--with-lg-quantum"

Bug#1068685: tup: FTBFS on loong64

[zhangdandan]

Source: tup
Version: 0.7.11-4
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the tup failed for loong64 in the Debian Package Auto-Building 
environment.

The error log is as follows,
```
../src/tup/platform.c:70:2: error: #error Unsupported cpu architecture. 
Please add support in tup/platform.c
   70 | #error Unsupported cpu architecture. Please add support in 
tup/platform.c

  |  ^
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1
```
The Full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=tup=0.7.11-4=loong64.


I have added support for loongarch64 in tup package.
Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add support for LoongArch. 
Last-Update: 2024-04-09

--- tup-0.7.11.orig/src/tup/platform.c
+++ tup-0.7.11/src/tup/platform.c
@@ -66,6 +66,10 @@ const char *tup_arch = "hppa";
 const char *tup_arch = "riscv64";
 #elif (__riscv || __riscv__) && __riscv_xlen == 32
 const char *tup_arch = "riscv32";
+#elif __loongarch__ && __loongarch_grlen == 32
+const char *tup_arch = "loongarch32";
+#elif __loongarch__ && __loongarch_grlen == 64
+const char *tup_arch = "loongarch64";
 #else
 #error Unsupported cpu architecture. Please add support in tup/platform.c
 #endif
--- tup-0.7.11.orig/tup.1
+++ tup-0.7.11/tup.1
@@ -765,7 +765,7 @@ In this case, the @-variable "FOO" is ex
 TUP_PLATFORM is a special @-variable. If CONFIG_TUP_PLATFORM is not set in the tup.config file, it has a default value according to the platform that tup itself was compiled in. Currently the default value is one of "linux", "solaris", "macosx", "win32", "freebsd" or "netbsd".
 .TP
 .B @(TUP_ARCH)
-TUP_ARCH is another special @-variable. If CONFIG_TUP_ARCH is not set in the tup.config file, it has a default value according to the processor architecture that tup itself was compiled in. Currently the default value is one of "i386", "x86_64", "powerpc", "powerpc64", "ia64", "alpha", "sparc", "arm64", or "arm".
+TUP_ARCH is another special @-variable. If CONFIG_TUP_ARCH is not set in the tup.config file, it has a default value according to the processor architecture that tup itself was compiled in. Currently the default value is one of "i386", "x86_64", "powerpc", "powerpc64", "ia64", "alpha", "sparc", "loongarch32", "loongarch64", "arm64", or "arm".
 
 .SH "VARIANTS"
 Tup supports variants, which allow you to build your project multiple times with different configurations. Perhaps the most common case is to build a release and a debug configuration with different compiler flags, though any number of variants can be used to support whatever configurations you like. Each variant is built in its own directory distinct from each other and from the source tree. When building with variants, the in-tree build is disabled. To create a variant, make a new directory at the top of the tup hierarchy and create a "tup.config" file there. For example:

Bug#1068681: kquickcharts: Make the tests non-fatal on loong64

[zhangdandan]

Source: kquickcharts
Version: 5.107.0-1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the kquickcharts package failed for loong64 in the Debian 
Package Auto-Building environment, the error log is as follows:

```
..
The following tests FAILED:
      5 - tst_BarChart.qml (Subprocess aborted)
      6 - tst_LineChart.qml (Subprocess aborted)
      7 - tst_PieChart.qml (Subprocess aborted)
Errors while running CTest
```

The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=kquickcharts=5.107.0-1%2Bb1=loong64.


There is no architecture-related code in the kquickcharts source code.
Refer to the processing methods of other architectures, could you set 
the tests non-fatal on loong64?

Please consider the patch I have attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru kquickcharts-5.107.0/debian/rules kquickcharts-5.107.0/debian/rules
--- kquickcharts-5.107.0/debian/rules   2023-03-16 21:42:02.0 +
+++ kquickcharts-5.107.0/debian/rules   2023-06-18 14:08:49.0 +
@@ -5,7 +5,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-testsuite_failing_archs := alpha hppa hurd-i386 mips64el powerpc riscv64 x32
+testsuite_failing_archs := alpha hppa hurd-i386 loong64 mips64el powerpc 
riscv64 x32
 ifneq (,$(filter $(DEB_HOST_ARCH),$(testsuite_failing_archs)))
   fail_param := || true
 endif

Bug#1068234: efibootguard: FTBFS with gnu-efi 3.0.18-1

[zhangdandan]

Source: efibootguard
Version: 0.16-2
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The gnu-efi source package was updated from 3.0.15-1 to 3.0.18-1 on 25 
Mar 2024.
Based on Debian buildd gnu-efi 3.0.18-1, the build log for efibootguard 
on loong64 is the only and latest.
Based on gnu-efi 3.0.15-1, efibootguard built on other architectures 
were built 69 days ago.
Please see the built status (on 02 Apr 2024) from 
https://buildd.debian.org/status/package.php?p=efibootguard=sid.


Compiling the efibootguard package failed for loong64 in the Debian 
Package Auto-Building environment, the error is as follows,

```
kernel-stub/initrd.c: In function ‘initrd_load_file’:
kernel-stub/initrd.c:83:31: error: passing argument 2 of ‘CopyMem’ 
discards ‘const’ qualifier from pointer target type 
[-Werror=discarded-qualifiers]

   83 | CopyMem(buffer, loader->addr, loader->size);
  | ~~^~
In file included from kernel-stub/initrd.c:16:
..
```
The full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=efibootguard=0.16-2=loong64.


After analysis, I found the second parameter of the CopyMem interface 
provided by the /usr/include/efi/efilib.h file is not "const" type.
The /usr/include/efi/efilib.h header file is provided by the gnu-efi 
package.
The second parameter of the CopyMem interface in version 3.0.15 is "IN 
CONST VOID *Src", but the second parameter of the CopyMem interface in 
version 3.0.18 is "IN VOID *Src". For example,

```
VOID EFIAPI
CopyMem (
    IN VOID *Dest,
    IN VOID *Src,
    IN UINTN    len
    );
```
It is recommended to modify the parameter passing specification for 
calling the CopyMem interface in the efibootguard source code.

Maintainers are requested to pay attention to the above phenomena.
Your opinions are welcome.

Thanks,
Dandan Zhang

Bug#1068232: rust-target: FTBFS: add loongarch64 support

[zhangdandan]

Source: rust-target
Version: 2.0.0-1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the rust-target package failed for loong64 in the Debian 
Package Auto-Building environment, the error log is as follows:

```
error[E0308]: mismatched types
  --> src/lib.rs:23:18
   |
23 | pub fn arch() -> &'static str {
   |       expected ``, found `()`
   |    |
   |    implicitly returns `()` as its body has no tail or `return` 
expression


For more information about this error, try `rustc --explain E0308`.
```

The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=rust-target=2.0.0-1=loong64.


The support for LoongArch architecture has been included in rust-target 
upstream, please see https://github.com/casey/target/pull/14.

You can also consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add loongarch64 support 
Applied-Upstream: https://github.com/casey/target/pull/14 
Signed-Off-By: heiher
Last-Update: 2024-04-02

--- rust-target-2.0.0.orig/src/lib.rs
+++ rust-target-2.0.0/src/lib.rs
@@ -29,6 +29,7 @@ pub fn arch() -> &'static str {
 "avr",
 "hexagon",
 "le32",
+"loongarch64",
 "mips",
 "mips64",
 "msp430",

Bug#1068227: ruby-rbtrace: FTBFS on loong64

[zhangdandan]

Source: ruby-rbtrace
Version: 0.4.14-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the ruby-rbtrace package failed for loong64 in the Debian 
Package Auto-Building environment, the error log is as follows:

```
..
  -- env CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
LDFLAGS="-Wl,-z,relro" CC=nil
  -- ./configure --disable-dependency-tracking --disable-shared 
--with-pic 
--prefix=/<>/debian/ruby-rbtrace/usr/lib/loongarch64-linux-gnu/rubygems-integration/3.1.0/gems/rbtrace-0.4.14/ext/dst/ 
--host=loongarch64-linux-gnu --build=loongarch64-linux-gnu 
--libdir=/<>/debian/ruby-rbtrace/usr/lib/loongarch64-linux-gnu/rubygems-integration/3.1.0/gems/rbtrace-0.4.14/ext/dst/lib

*** extconf.rb failed ***
```

The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=ruby-rbtrace=0.4.14-1=loong64.


For modification ideas, please refer to the patch I attached.
The ruby-rbtrace package was compiled successfully on my local loong64 
rootfs environment.


For code standardization, maintainers can regenerate patches for loong64.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add the definition of loongarch64 
Last-Update: 2024-04-02

--- ruby-rbtrace-0.4.14.orig/ext/extconf.rb
+++ ruby-rbtrace-0.4.14/ext/extconf.rb
@@ -47,6 +47,10 @@ unless File.exist?("#{CWD}/dst/#{libdir}
   if buildstr == "riscv64-linux-gnu"
 buildstr = "riscv64-unknown-linux-gnu"
   end
+  #ifdef __loongarch64
+hoststr = "loongarch64-unknown-linux-gnu"
+buildstr = "loongarch64-unknown-linux-gnu"
+  #endif
   sys("./configure --disable-dependency-tracking --disable-shared --with-pic --prefix=#{CWD}/dst/ --host=#{hoststr} --build=#{buildstr} --libdir=#{CWD}/dst/#{libdir}")
   sys("make install")
 end

Bug#1068171: healpy: FTBFS: add loongarch64 support

[zhangdandan]

Source: healpy
Version: 1.16.6-1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling healpy package failed on my local loong64 rootfs environment.
I have added loongarch64 support in healpy package.

Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

Description: Add loongarch64 support 
Last-Update: 2024-04-01

--- healpy-1.16.6.orig/cfitsio/fitsio2.h
+++ healpy-1.16.6/cfitsio/fitsio2.h
@@ -151,6 +151,16 @@ extern int Fitsio_Pthread_Status;
 #error "can't handle long size given by __riscv_xlen"
 #  endif
 
+#elif defined(__loongarch__)
+#define BYTESWAPPED TRUE
+#  if __loongarch_grlen == 32
+#define LONGSIZE 32
+#  elif __loongarch_grlen == 64
+#define LONGSIZE 64
+#  else
+#error "can't handle long size given by __loongarch_grlen"
+#  endif
+
 /* == */
 /*  the following are all 32-bit byteswapped platforms*/
 

Bug#1068081: rust-dns-lookup: "lookup::test_rev_localhost' panicked at 'assertion failed" on loong64

[zhangdandan]

Source: rust-dns-lookup
Version: 1.0.8-4
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the rust-dns-lookup package failed for loong64 in the Debian 
Package Auto-Building environment, the error log is as follows:

```
test lookup::test_rev_localhost ... FAILED
failures:

 lookup::test_rev_localhost stdout 
thread 'lookup::test_rev_localhost' panicked at 'assertion failed: 
`(left == right)`

  left: `"loong64-loongson-03.local"`,
 right: `"localhost"`', src/lookup.rs:77:3
```

The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=rust-dns-lookup=1.0.8-4=loong64.


After analysis, I think the maintainer may need to improve the 
test_rev_localhost() test case in the 
rust-dns-lookup-1.0.8/src/lookup.rs file.

The reasons are as follows:
1. If the first line of the /etc/hosts file is "127.0.0.1 localhost", 
the test case is successful.

```
# cat /etc/hosts
127.0.0.1   localhost
127.0.0.1   loong64-loongson-03.local loong64-loongson-03
```
Based on the above configure in /etc/hosts, the rust-dns-lookup package 
was compiled successfully on my local loong64 rootfs environment.


2. On the contrary, if the first line's content of the /etc/hosts file 
is not "127.0.0.1 localhost", the test case fails.
Even if the /etc/hosts file contains "127.0.0.1 localhost" in other 
lines except the first line, the test case fails.

```
# cat /etc/hosts
127.0.0.1   loong64-loongson-03.local loong64-loongson-03
127.0.0.1   localhost
```

Alternatively, we could set the first line of the '/etc/hosts' file to 
'127.0.0.1 localhost' on the loong64 buildd machines.

Your opinions are welcome.
If you have any questions, you can contact me at any time.

Thanks,
Dandan Zhang

Bug#1068079: crash: FTBFS on loong64

[zhangdandan]

Source: crash
Version: 8.0.4-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the crash package failed for loong64 in the Debian Package 
Auto-Building environment.
The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=crash=8.0.4-1=loong64.


The LoongArch architecture has been supported in crash upstream [1].
Details of support for the LoongArch architecture can also be obtained 
from crash-utility's mailing list [2].


Would it be possible to include LoongArch support in the next upload?
Your opinions are welcome.
If you have any questions, you can contact me at any time.

[1]: https://github.com/crash-utility/crash/tree/master
[2]: 
https://listman.redhat.com/archives/crash-utility/2023-September/author.html


Thanks,
Dandan Zhang

Bug#1068061: kexec-tools: FTBFS on loong64

[zhangdandan]

Source: kexec-tools
Version: 1:2.0.27-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the kexec-tools failed for loong64 in the Debian Package 
Auto-Building environment.

```
kexec/arch/loongarch/crashdump-loongarch.c:21:10: fatal error: iomem.h: 
No such file or directory

   21 | #include "iomem.h"
  |  ^
compilation terminated.
```

The full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=kexec-tools=1%3A2.0.27-1=loong64.
After investigation, we have confirmed that upstream 2.0.27 version is 
missing the kexec/arch/loongarch/iomem.h header file.
This issue has been fixed in upstream 2.0.28 version, please get from 
https://mirrors.edge.kernel.org/pub/linux/utils/kernel/kexec/kexec-tools-2.0.28.tar.gz.


There are two options for reference.
1.Please consider the patch I have attached.
Apply the attached patch, the kexec-tools 1:2.0.27-1 package was 
compiled successfully on my local loong64 rootfs environment.

2.Please update to New upstream 2.0.28 release.

Could you fix the loong64 compilation error in the next upload?
Your suggestions are welcome.

Thanks,
Dandan Zhang

--- kexec-tools-2.0.27.orig/kexec/arch/loongarch/Makefile
+++ kexec-tools-2.0.27/kexec/arch/loongarch/Makefile
@@ -18,5 +18,6 @@ loongarch_VIRT_TO_PHYS =
 dist += kexec/arch/loongarch/Makefile $(loongarch_KEXEC_SRCS)			\
 	kexec/arch/loongarch/kexec-loongarch.h	\
 	kexec/arch/loongarch/image-header.h	\
+	kexec/arch/loongarch/iomem.h		\
 	kexec/arch/loongarch/crashdump-loongarch.h\
 	kexec/arch/loongarch/include/arch/options.h
--- /dev/null
+++ kexec-tools-2.0.27/kexec/arch/loongarch/iomem.h
@@ -0,0 +1,10 @@
+#ifndef IOMEM_H
+#define IOMEM_H
+
+#define SYSTEM_RAM		"System RAM\n"
+#define KERNEL_CODE		"Kernel code\n"
+#define KERNEL_DATA		"Kernel data\n"
+#define CRASH_KERNEL		"Crash kernel\n"
+#define IOMEM_RESERVED		"Reserved\n"
+
+#endif

Bug#1059262: trilinos: add loongarch64 support

[zhangdandan]

Hi maintainers,

On Fri, 22 Dec 2023 09:17:19 + Zhang Na wrote:

> Source: trilinos
> Version: 13.2.0-5
> Severity: normal
> X-Debbugs-Cc: zhan...@loongson.cn
>
> Dear Maintainer,
>
> Please add loong64 support in debian/control, thanks!

The trilinos itself blocks the compilation of many packages.
Based on the attached patch, the trilinos package was compiled 
successfully on my local loong64 rootfs environment.

I have built 132 binary packages from trilinos on local ENV.

Could you enable loong64 support in debian/control in the next upload?
Your suggestions are always welcome.

Thanks,
Dandan Zhang

Bug#1066962: wxwidgets3.2: 1 testsuite failed on loong64

[zhangdandan]

Hi,
   Thanks for your reply.
在 2024/3/22 上午10:45, Scott Talbert 写道:

On Sat, 16 Mar 2024 15:21:57 +0800 zhangdandan
 wrote:

Source: wxwidgets3.2
Version: 3.2.4+dfsg-3.1
Severity: serious
Tags: help
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The following test failed on the loongarch64 architecture, compiled
20 hours ago (March 16th).

./uris/url.cpp:89: FAILED:
     REQUIRE( in_stream )
with expansion:
     0

==

test cases: 312 | 311 passed | 1 failed
assertions: 1230238 | 1230237 passed | 1 failed

make[1]: *** [debian/rules:89: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess

Hello,

This particular test is supposed to be skipped if the build host
doesn't have network connectivity.  Does the loong64 buildd have
network connectivity (unlike the other buildd's)?


Printed in_stream and found a NULL pointer.
Analyzing the test case again, I found that the buildds environment 
could not access http://detectportal.firefox.com/ and the text provided 
by the link is "success".
I've asked my Network Administrator to turn on access to 
http://detectportal.firefox.com.
I can currently ping the corresponding link in the buildd environment, 
as follows:

root@loong64-loongson-06:~# ping detectportal.firefox.com
PING prod.detectportal.prod.cloudops.mozgcp.net (34.107.221.82) 56(84) 
bytes of data.
64 bytes from 82.221.107.34.bc.googleusercontent.com (34.107.221.82): 
icmp_seq=1 ttl=52 time=150 ms
64 bytes from 82.221.107.34.bc.googleusercontent.com (34.107.221.82): 
icmp_seq=2 ttl=52 time=150 ms


- The result of the discussion in the previous email.
# python3 -m httpbin.core & export HTTPBIN_PID=$!; RC=0; cd tests && 
WX_TEST_WEBREQUEST_URL="http://localhost:5000; ./test ~[.] 
~[special-file] || RC=1; kill -9 ${HTTPBIN_PID}; exit $RC

All tests passed (1248603 assertions in 312 test cases)  //on loong64 ENV

- In addition, it is important to focus on the other test case.
# cd tests && wxUSE_XVFB=1 xvfb-run -a . /test_gui ~[.] ~WebView 
~wxDC::GetPartialTextExtent ~TextCtrlTestCase

Need to add loong64 support in d/rules, as follows:
```
diff --git a/debian/rules b/debian/rules
index 36f4770..1fb1451 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@ TEST_GUI_FILTER = ~[.]
 ifneq (,$(filter $(DEB_HOST_ARCH), alpha loong64 mips64el riscv64 s390x))
 TEST_FILTER += ~[special-file]
 endif
-ifneq (,$(filter $(DEB_HOST_ARCH), alpha hppa mips64el ppc64 riscv64 
s390x sparc64 x32))
+ifneq (,$(filter $(DEB_HOST_ARCH), alpha hppa loong64 mips64el ppc64 
riscv64 s390x sparc64 x32))

 TEST_GUI_FILTER += ~WebView
 endif
 ifneq (,$(filter $(DEB_HOST_ARCH), i386))
```

Your suggestions are always welcome.
The wxwidgets3.2 itself blocks the compilation of 47 packages such as 
gnuplot.

And gnuplot blocks the compilation of 52 packages.
Please stay tuned for the build status of wxwidgets3.2 on loong64.
If you have any questions you can cantact me at any time.

Thanks,
Dandan Zhang

Bug#1066962: wxwidgets3.2: 1 testsuite failed on loong64

[zhangdandan]

Source: wxwidgets3.2
Version: 3.2.4+dfsg-3.1
Severity: serious
Tags: help
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The following test failed on the loongarch64 architecture, compiled 20 
hours ago (March 16th).

```
---
URLTestCase
  GetInputStream
---
./uris/url.cpp:37
...

./uris/url.cpp:89: FAILED:
  REQUIRE( in_stream )
with expansion:
  0

===
test cases: 312 | 311 passed | 1 failed
assertions: 1230238 | 1230237 passed | 1 failed

make[1]: *** [debian/rules:89: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned 
exit status 2

```
The full build log can be found at 
https://buildd.debian.org/status/package.php?p=wxwidgets3.2=sid.


I have reproduced the above testsuite issues on my local loong64 rootfs 
environment.
After analyzing, I don't think this error has anything to do with 
architecture.

So please focus on this test case failure.

thanks,
Dandan Zhang

Bug#1061371: gcc-14 ftbfs on loong64

[zhangdandan]

在 2024/3/12 下午12:55, Bo YU 写道:

Hi!

On Tue, Mar 12, 2024 at 11:03 AM zhangdandan  wrote:

Hi,
   Thanks for your feedback on loong64's compilation errors.


Package: src:gcc-14
Version: 14-20240121-1
Severity: important
Tags: sid trixie ftbfs
X-Debbugs-CC: debian-loonga...@lists.debian.org

gcc-14 ftbfs on loong64:
...

The remaining build failure is now:

https://buildd.debian.org/status/fetch.php?pkg=gcc-14=loong64=14-20240303-1=1709485913=0

...
dh_installdirs -plibgcc-s1 usr/share/doc/libgcc-s1 usr/lib/loongarch64-linux-gnu
mv debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1 
debian/libgcc-s1/usr/lib/loongarch64-linux-gnu/.
mv: cannot stat 'debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1': No 
such file or directory
make[1]: *** [debian/rules.d/binary-libgcc.mk:291: 
stamps/08-binary-stamp-libgcc] Error 1

- For the compilation error raised by Matthias Klose.
It is because the linux header file linux-libc-dev lacks loong64 support.
The Debian kernel-team has merged the loong64's patch, please see 
https://salsa.debian.org/kernel-team/linux/-/merge_requests/879.

- I have reproduced the gcc-14 compilation error locally from Adrian Bunk.
The compilation error is consistent with the feedback from Adrian Bunk.
For gcc-14, the loong64's multilib modification is not included in 
gcc-multilib-multiarch.
Please consider the following patch. If you have any questions, you can contact 
me at any time.
```
--- a/src/gcc/config/loongarch/t-linux
+++ b/src/gcc/config/loongarch/t-linux
@@ -16,9 +16,9 @@
  # along with GCC; see the file COPYING3.  If not see
  # <http://www.gnu.org/licenses/>.

-MULTIOSDIR_lp64d := ../lib64$(call if_multiarch,:loongarch64-linux-gnu)
-MULTIOSDIR_lp64f := ../lib64/f32$(call if_multiarch,:loongarch64-linux-gnuf32)
-MULTIOSDIR_lp64s := ../lib64/sf$(call if_multiarch,:loongarch64-linux-gnusf)
+MULTIOSDIR_lp64d := ../lib$(call if_multiarch,:loongarch64-linux-gnu)
+MULTIOSDIR_lp64f := ../lib/f32$(call if_multiarch,:loongarch64-linux-gnuf32)
+MULTIOSDIR_lp64s := ../lib/sf$(call if_multiarch,:loongarch64-linux-gnusf)

  # Don't define MULTILIB_OSDIRNAMES if multilib is disabled.
  ifeq ($(filter LA_DISABLE_MULTILIB,$(tm_defines)),)
```

Maybe debdiff should be attached here for GCC maintainer with conveniently.


Patch attached.

Thanks.


BTW, the gcc-14 source package was compiled successfully on my local loong64 
rootfs environment, for examples,
```
..
dh_installdirs -plibgcc-s1 usr/share/doc/libgcc-s1 usr/lib/loongarch64-linux-gnu
mv debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1 
debian/libgcc-s1/usr/lib/loongarch64-linux-gnu/.
debian/dh_doclink -plibgcc-s1 gcc-14-base
..
dpkg-deb: building package 'libgfortran-14-dev' in 
'../libgfortran-14-dev_14-20240201-3_loong64.deb'.
dpkg-deb: building package 'g++-14-loongarch64-linux-gnu' in 
'../g++-14-loongarch64-linux-gnu_14-20240201-3_loong64.deb'.
dpkg-deb: building package 'gccrs-14-loongarch64-linux-gnu-dbgsym' in 
'../gccrs-14-loongarch64-linux-gnu-dbgsym_14-20240201-3_loong64.deb'.
dpkg-deb: building package 'gcc-14-loongarch64-linux-gnu-dbgsym' in 
'../gcc-14-loongarch64-linux-gnu-dbgsym_14-20240201-3_loong64.deb'.
..
make[1]: Leaving directory '/home/zdd/gcc-14/gcc-14-14-20240201'
  dpkg-genbuildinfo --build=binary -O../gcc-14_14-20240201-3_loong64.buildinfo
  dpkg-genchanges --build=binary -O../gcc-14_14-20240201-3_loong64.changes
```

thanks,
Dandan Zhang



diff --git a/src/gcc/config/loongarch/t-linux b/src/gcc/config/loongarch/t-linux
index 23e1fb9..4475600 100644
--- a/src/gcc/config/loongarch/t-linux
+++ b/src/gcc/config/loongarch/t-linux
@@ -16,9 +16,9 @@
 # along with GCC; see the file COPYING3.  If not see
 # <http://www.gnu.org/licenses/>.
 
-MULTIOSDIR_lp64d := ../lib64$(call if_multiarch,:loongarch64-linux-gnu)
-MULTIOSDIR_lp64f := ../lib64/f32$(call if_multiarch,:loongarch64-linux-gnuf32)
-MULTIOSDIR_lp64s := ../lib64/sf$(call if_multiarch,:loongarch64-linux-gnusf)
+MULTIOSDIR_lp64d := ../lib$(call if_multiarch,:loongarch64-linux-gnu)
+MULTIOSDIR_lp64f := ../lib/f32$(call if_multiarch,:loongarch64-linux-gnuf32)
+MULTIOSDIR_lp64s := ../lib/sf$(call if_multiarch,:loongarch64-linux-gnusf)
 
 # Don't define MULTILIB_OSDIRNAMES if multilib is disabled.
 ifeq ($(filter LA_DISABLE_MULTILIB,$(tm_defines)),)

Bug#1054822: opam: FTBFS: sed: can't read opam.install: No such file or directory

[zhangdandan]

Hi,

On Fri, 27 Oct 2023 21:42:50 +0200 Lucas Nussbaum wrote:

> Source: opam
> Version: 2.1.5-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Actual targets:
> - _build/default/opam-installer.install
> - _build/default/opam.install
> Running[1]: (cd _build/default/src/client && /bin/sh -c 'git describe 
--exact HEAD || echo [dev]') > _build/default/src/client/git-describe 2> 
/dev/null
> Running[2]: (cd _build/default/src/client && /bin/sh -c 'git 
rev-parse --quiet --verify HEAD || echo .') > 
_build/default/src/client/git-sha 2> /dev/null

> sed -f process.sed opam.install > processed-opam.install
> sed: can't read opam.install: No such file or directory
> make[2]: *** [Makefile:166: processed-opam.install] Error 2

Compiling the opam failed for loong64 in the Debian Package 
Auto-Building environment.
In fact, there are compilation errors in riscv64, m68k, powerpc and 
other architectures.
If you compile opam again on amd64 and arm64 (compiled 190 days ago), 
there will be the same error.

The error log as the above report.

After analyzing, I can explain the reason for the compilation error by 
the following code,

```
From opam-2.1.5/Makefile

DUNE_PROMOTE_ARG =
DUNE_PROMOTE_ARG += --promote-install-files

ifeq ($(DUNE),)
  DUNE_EXE = src_ext/dune-local/dune.exe
  ifeq ($(shell command -v cygpath 2>/dev/null),)
    DUNE := $(DUNE_EXE)
  else
    DUNE := $(shell echo "$(DUNE_EXE)" | cygpath -f - -a)
  endif
else
  DUNE_EXE=
  # NB make does not export the PATH update in Makefile.config to 
$(shell ...)
  ifeq ($(shell PATH='$(PATH)' $(DUNE) build --root . --help=plain 
2>/dev/null \

  | grep -F -- '$(DUNE_PROMOTE_ARG) '),)  //Note that ti
    $(info DD-Pre-Var=$(DUNE_PROMOTE_ARG))
    //printf "--promote-install-files"
    DUNE_PROMOTE_ARG =
    $(info DD-After-Var=$(DUNE_PROMOTE_ARG))
    //printf " "
  endif
endif
```
- Case 1: "DUNE_PROMOTE_ARG = --promote-install-files"
The opam compiles fine in my local rootfs.
- Case 2: "DUNE_PROMOTE_ARG = "
Compiling opam fails with the same phenomenon as Debian Package 
Auto-Building.


Maybe the following error is related to the value of the parameter 
DUNE_PROMOTE_ARG in the Makefile file.

```
sed -f process.sed opam.install > processed-opam.install
sed: can't read opam.install: No such file or directory
make[2]: *** [Makefile:166: processed-opam.install] Error 2
```

BTW, the opam's build dependency is ocaml-dune.
Before 190 days, amd64 compiled opam fine, and the version of ocaml-dune 
is ocaml-dune (3.10.0-2).
Now, compiling opam fails, and the version of ocaml-dune is ocaml-dune 
(3.11.1-1).


Hopefully the above information will provide some help to maintainers.

Thanks,
Dandan Zhang

Bug#1066082: python-cpuinfo: Add support for loongarch64

[zhangdandan]

Source: python-cpuinfo
Version: 9.0.0-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the python-cpuinfo successed for loong64 in the Debian Package 
Auto-Building environment.

But python-cpuinfo source package lacks LoongArch architecture support.

- Background information is provided below.
When I analyzed why python3-pandas-lib:loong64 was blocking the build of 
29 source packages, I found that the compilation dependency 
(python3-tables-lib:loong64) of pandas was not satisfied.
The reason is that pytables compilation failed, please check the 
following error log,

```
..
File "/usr/lib/python3/dist-packages/cpuinfo/cpuinfo.py", line 366, in 
_check_arch

    raise Exception("py-cpuinfo currently only works on X86 "
Exception: py-cpuinfo currently only works on X86 and some 
ARM/PPC/S390X/MIPS/RISCV CPUs.

..
```
The full build log of pytables, please see 
https://buildd.debian.org/status/logs.php?pkg=pytables=3.9.2-1=loong64.

In short, the chain of dependencies is as follows,
python3-pandas-lib(src:pandas) ——> python3-tables-lib(src:pytables) ——> 
python3-cpuinfo(src:python-cpuinfo)
The result is that python-cpuinfo lacks LoongArch support, even though 
it is a package for the all architecture.


- The support for LoongArch was added to python-cpuinfo upstream in Nov. 
2022.
The upstream link for python-cpuinfo is 
https://github.com/workhorsy/py-cpuinfo.


The end, could you add LoongArch support in the next upload?
Your suggestions are welcome.

Thanks,
Dandan Zhang

Bug#1059991: grub-installer: build loong64.udeb for loongarch64

[zhangdandan]

On Tue, 12 Mar 2024 09:20:40 +0100 John Paul Adrian Glaubitz wrote:
> Hi Dandan,
>
> On Tue, 2024-03-12 at 16:07 +0800, zhangdandan wrote:
> >  Thanks for your heads up.
> >  I have updated the patch (Add support for loongarch64).
> >  Please consider the patch I have attached.
> >  Your suggestions are always welcome.
>
> I already made the changes before you sent this mail, so we're all good.
>
> See: 
https://salsa.debian.org/installer-team/grub-installer/-/commit/0962896894d83716dec19a60ba9db94fdc807a1c

>

Thanks.

Dandan

Bug#1059991: grub-installer: build loong64.udeb for loongarch64

[zhangdandan]

Hi Adrian,
> I don't think this is true since the grub2 source is actually not 
building
> any loong64 packages yet. We will need to change the grub2 source 
first to
> build at packages such as grub-efi-loong64 and so on similar to 
riscv64 [1].

>
> After that, loong64 can be added to grub-installer as it was be done for
> riscv64 [2] (except for the case for "riscv64/*)").

Thanks for your heads up.
I have updated the patch (Add support for loongarch64).
Please consider the patch I have attached.
Your suggestions are always welcome.

Thanks,
Dandan Zhang


diff -Nru grub-installer-1.200/debian/control 
grub-installer-1.200/debian/control
--- grub-installer-1.200/debian/control 2024-02-16 18:45:32.0 +
+++ grub-installer-1.200/debian/control 2024-02-16 19:25:38.0 +
@@ -8,7 +8,7 @@
 Vcs-Git: https://salsa.debian.org/installer-team/grub-installer.git
 
 Package: grub-installer
-Architecture: amd64 arm64 armhf i386 ia64 hurd-i386 hurd-amd64 kfreebsd-i386 
kfreebsd-amd64 mipsel powerpc ppc64 ppc64el riscv64 sparc sparc64
+Architecture: amd64 arm64 armhf i386 ia64 hurd-i386 hurd-amd64 kfreebsd-i386 
kfreebsd-amd64 loong64 mipsel powerpc ppc64 ppc64el riscv64 sparc sparc64
 XB-Subarchitecture: ${subarch}
 Provides: bootable-system
 Depends: ${shlibs:Depends}, ${misc:Depends}, kernel-installer, created-fstab, 
di-utils, di-utils-mapdevfs, os-prober, partman-utils
diff -Nru grub-installer-1.200/debian/isinstallable 
grub-installer-1.200/debian/isinstallable
--- grub-installer-1.200/debian/isinstallable   2024-02-16 18:45:32.0 
+
+++ grub-installer-1.200/debian/isinstallable   2024-02-16 19:25:38.0 
+
@@ -33,6 +33,12 @@
log "GRUB is only usable on EFI riscv64 systems, not $ARCH"
exit 1
;;
+loong64/efi)
+   ;;
+loong64/*)
+   log "GRUB is only usable on EFI loong64 systems, not $ARCH"
+   exit 1
+   ;;
 esac
 
 db_get grub-installer/skip
diff -Nru grub-installer-1.200/grub-installer 
grub-installer-1.200/grub-installer
--- grub-installer-1.200/grub-installer 2024-02-16 18:45:33.0 +
+++ grub-installer-1.200/grub-installer 2024-02-16 19:25:38.0 +
@@ -354,6 +354,9 @@
 ia64/*)
grub_package="grub-efi-ia64"
;;
+loong64/efi)
+   grub_package="grub-efi-loong64"
+   ;;
 powerpc/*|ppc64/*)
grub_package="grub-ieee1275"
;;

Bug#1061371: gcc-14 ftbfs on loong64

[zhangdandan]

Hi,
  Thanks for your feedback on loong64's compilation errors.

> > Package: src:gcc-14
> > Version: 14-20240121-1
> > Severity: important
> > Tags: sid trixie ftbfs
> > X-Debbugs-CC: debian-loonga...@lists.debian.org
> >
> > gcc-14 ftbfs on loong64:
> >...
>
> The remaining build failure is now:
>
> 
https://buildd.debian.org/status/fetch.php?pkg=gcc-14=loong64=14-20240303-1=1709485913=0

>
> ...
> dh_installdirs -plibgcc-s1 usr/share/doc/libgcc-s1 
usr/lib/loongarch64-linux-gnu
> mv debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1 
debian/libgcc-s1/usr/lib/loongarch64-linux-gnu/.
> mv: cannot stat 
'debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1': No such file 
or directory
> make[1]: *** [debian/rules.d/binary-libgcc.mk:291: 
stamps/08-binary-stamp-libgcc] Error 1


- For the compilation error raised by Matthias Klose.
It is because the linux header file linux-libc-dev lacks loong64 support.
The Debian kernel-team has merged the loong64's patch, please see 
https://salsa.debian.org/kernel-team/linux/-/merge_requests/879.


- I have reproduced the gcc-14 compilation error locally from Adrian Bunk.
The compilation error is consistent with the feedback from Adrian Bunk.
For gcc-14, the loong64's multilib modification is not included in 
gcc-multilib-multiarch.
Please consider the following patch. If you have any questions, you can 
contact me at any time.

```
--- a/src/gcc/config/loongarch/t-linux
+++ b/src/gcc/config/loongarch/t-linux
@@ -16,9 +16,9 @@
 # along with GCC; see the file COPYING3.  If not see
 # .

-MULTIOSDIR_lp64d := ../lib64$(call if_multiarch,:loongarch64-linux-gnu)
-MULTIOSDIR_lp64f := ../lib64/f32$(call 
if_multiarch,:loongarch64-linux-gnuf32)
-MULTIOSDIR_lp64s := ../lib64/sf$(call 
if_multiarch,:loongarch64-linux-gnusf)

+MULTIOSDIR_lp64d := ../lib$(call if_multiarch,:loongarch64-linux-gnu)
+MULTIOSDIR_lp64f := ../lib/f32$(call 
if_multiarch,:loongarch64-linux-gnuf32)

+MULTIOSDIR_lp64s := ../lib/sf$(call if_multiarch,:loongarch64-linux-gnusf)

 # Don't define MULTILIB_OSDIRNAMES if multilib is disabled.
 ifeq ($(filter LA_DISABLE_MULTILIB,$(tm_defines)),)
```

BTW, the gcc-14 source package was compiled successfully on my local 
loong64 rootfs environment, for examples,

```
..
dh_installdirs -plibgcc-s1 usr/share/doc/libgcc-s1 
usr/lib/loongarch64-linux-gnu
mv debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1 
debian/libgcc-s1/usr/lib/loongarch64-linux-gnu/.

debian/dh_doclink -plibgcc-s1 gcc-14-base
..
dpkg-deb: building package 'libgfortran-14-dev' in 
'../libgfortran-14-dev_14-20240201-3_loong64.deb'.
dpkg-deb: building package 'g++-14-loongarch64-linux-gnu' in 
'../g++-14-loongarch64-linux-gnu_14-20240201-3_loong64.deb'.
dpkg-deb: building package 'gccrs-14-loongarch64-linux-gnu-dbgsym' in 
'../gccrs-14-loongarch64-linux-gnu-dbgsym_14-20240201-3_loong64.deb'.
dpkg-deb: building package 'gcc-14-loongarch64-linux-gnu-dbgsym' in 
'../gcc-14-loongarch64-linux-gnu-dbgsym_14-20240201-3_loong64.deb'.

..
make[1]: Leaving directory '/home/zdd/gcc-14/gcc-14-14-20240201'
 dpkg-genbuildinfo --build=binary 
-O../gcc-14_14-20240201-3_loong64.buildinfo

 dpkg-genchanges --build=binary -O../gcc-14_14-20240201-3_loong64.changes
```

thanks,
Dandan Zhang

Bug#1065587: re: rust-polling: Please try to rebuild rust-polling for loong64

[zhangdandan]

Hi,

On Thu, 7 Mar 2024 14:39:31 + Peter Green wrote:

> > I have built the rust-polling successfully in my local loong64
> > environment, without modifications required.
>
> Make sure you are not using DEB_BUILD_OPTIONS=nocheck
>

I didn't use any DEB_BUILD_OPTIONS in my local ENV.
After comparing, I found that the packages version I used when compiling 
rust-polling locally were different from the current Debian 
Auto-Building packages version, for examples:

- My local ENV
   Compiling libc v0.2.150   //Note that
   Compiling rustix v0.38.25
   Compiling linux-raw-sys v0.4.11
   Compiling pin-project-lite v0.2.13
   Compiling cfg-if v1.0.0
   Compiling bitflags v2.4.0
   Compiling tracing-core v0.1.30
- Debian Package Auto-Building ENV
   Compiling libc v0.2.150   //Note that
   Compiling rustix v0.38.25
   Compiling linux-raw-sys v0.4.11
   Compiling pin-project-lite v0.2.13
   Compiling cfg-if v1.0.0
   Compiling bitflags v2.4.0
   Compiling tracing-core v0.1.30

The error build log of rust-polling is as follows,
```
error[E0425]: cannot find value `FS_IOC_GETFLAGS` in module `c`
    --> /usr/share/cargo/registry/rustix-0.38.30/src/fs/ioctl.rs:142:57
..
error[E0425]: cannot find value `FS_IOC_SETFLAGS` in module `c`
    --> /usr/share/cargo/registry/rustix-0.38.30/src/fs/ioctl.rs:161:57
 |
161  | let ctl = ioctl::Setter::c::FS_IOC_SETFLAGS }>, u32>::new(flags.bits());

 | ^^^
 |
    ::: 
/usr/share/cargo/registry/libc-0.2.152/src/unix/linux_like/linux/mod.rs:2922:1

..
```

> > Please try to rebuild rust-polling for loong64 in the Debian Package
> > Auto-Building environment.
>
> It failed again.

Analyzed by our rust team, due to rust libc 0.2.152 missing LoongArch's 
FS_IOC_{G,S}{ETVERSION,ETFLAGS} related symbol bindings.
The following commit (Add ioctl FS_IOC_{G,S}{ETVERSION,ETFLAGS} for 
LoongArch64) can resolve this question:

https://github.com/rust-lang/libc/commit/9a074313961e93a0f38fab26b72a4fc393ed1148

Could the above commit "Add ioctl FS_IOC_{G,S}{ETVERSION,ETFLAGS} for 
LoongArch64" be backpunched to Debian rust-libc 0.2.152-1。

Or wait for the next upstream version of rust-lang/libc.
What about your suggestion?


Thanks,
Dandan Zhang

Bug#1066023: libdebian-installer: Add subarch detection for loongarch64

[zhangdandan]

Source: libdebian-installer
Version: 0.124
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

I have added subarch detection for loongarch64 in libdebian-installer 
source package.

Please consider the patch I have attached.

The libdebian-installer source package was compiled successfully on my 
local loong64 rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru libdebian-installer-0.124/src/system/Makefile.am 
libdebian-installer-0.124/src/system/Makefile.am
--- libdebian-installer-0.124/src/system/Makefile.am2021-02-08 
12:52:58.0 +
+++ libdebian-installer-0.124/src/system/Makefile.am2022-10-02 
02:14:09.0 +
@@ -22,6 +22,7 @@
subarch-armeb-linux.c \
subarch-armel-linux.c \
subarch-armhf-linux.c \
+   subarch-loongarch64-linux.c \
subarch-m68k-linux.c \
subarch-mips-linux.c \
subarch-mipsel-linux.c \
diff -Nru libdebian-installer-0.124/src/system/subarch-loongarch64-linux.c 
libdebian-installer-0.124/src/system/subarch-loongarch64-linux.c
--- libdebian-installer-0.124/src/system/subarch-loongarch64-linux.c
1970-01-01 00:00:00.0 +
+++ libdebian-installer-0.124/src/system/subarch-loongarch64-linux.c
2022-10-02 02:14:09.0 +
@@ -0,0 +1,29 @@
+/*
+ * subarch-loongarch64-linux.c
+ *
+ * Copyright (C) 2023
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program.  If not, see .
+ */
+
+#include 
+#include 
+
+const char *di_system_subarch_analyze(void)
+{
+   if (di_system_is_efi())
+   return "efi";
+   else
+   return "generic";
+}

Bug#1065467: marisa: FTBFS on loongarch64 as the test case fails

[zhangdandan]

Hi,

   Thanks for your reply.

On Thu, 07 Mar 2024 09:31:20 -0500 Boyuan Yang wrote:

> Hi,
>
> 在 2024-03-05星期二的 12:10 +0800，zhangdandan写道：
> > Source: marisa
> > Version: 0.2.6-15
> > Severity: wishlist
> > Tags: ftbfs
> > User: debian-loonga...@lists.debian.org
> > Usertags: loong64
> >
> > Dear maintainers,
> >
> > Compiling the marisa failed for loong64 in the Debian Package
> > Auto-Building environment.
> > Please consider the patch (my local patch) I have attached.
> > If you have any questions, you can contact me at any time.
>
> I can take this patch, but the patch should be forwarded upstream first.
> Please forward it to GitHub upstream project so that I can use the 
forwarded

> link as a reference. After that, I can make the patched upload in Debian.

I have submitted a pull request to upstream, please see 
https://github.com/s-yata/marisa-trie/pull/56.
But this marisa-trie project hasn't been updated for a long time (about 
4 years).
Refer to other architectures for handling, could you add a patch for 
marisa-0.2.6 source package?


Thanks,
Dandan Zhang

Bug#1065592: partman-efi: add build support for loongarch64

[zhangdandan]

Source: partman-efi
Version: 103
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The partman-efi source package lacks LoongArch architecture support.
We need to add build support for loongarch64 in d/control.

Please consider the patch I have attached.
The partman-efi source package was compiled successfully on my local 
loong64 rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru partman-efi-103/debian/control partman-efi-103/debian/control
--- partman-efi-103/debian/control  2024-01-06 21:33:46.0 +
+++ partman-efi-103/debian/control  2024-01-06 21:49:11.0 +
@@ -9,6 +9,6 @@
 
 Package: partman-efi
 Package-Type: udeb
-Architecture: i386 ia64 amd64 arm64 armhf riscv64
+Architecture: i386 ia64 amd64 arm64 armhf riscv64 loong64
 Depends: partman-base, efi-modules, dosfstools-udeb, ${misc:Depends}
 Description: Add to partman support for EFI System Partitions

Bug#1065591: openvswitch: enable dpdk build support for loongarch64

[zhangdandan]

Source: openvswitch
Version: 3.3.0~git20240118.e802fe7-3
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The openvswitch source package lacks additional loongarch64 support.
Please consider the patch I attached.

Based on the attached patch, it is possible to compile 2 more packages 
for loong64, for examples,

openvswitch-switch-dpdk-dbgsym_3.3.0~git20240118.e802fe7-3_loong64.deb
openvswitch-switch-dpdk_3.3.0~git20240118.e802fe7-3_loong64.deb

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru openvswitch-3.3.0~git20240118.e802fe7/debian/control 
openvswitch-3.3.0~git20240118.e802fe7/debian/control
--- openvswitch-3.3.0~git20240118.e802fe7/debian/control2024-01-19 
11:03:39.0 +
+++ openvswitch-3.3.0~git20240118.e802fe7/debian/control2024-02-05 
08:45:19.0 +
@@ -22,10 +22,10 @@
  iproute2,
  libbpf-dev,
  libcap-ng-dev,
- libdbus-1-dev [amd64 i386 ppc64el arm64 riscv64],
- libdpdk-dev (>= 22.11.3-2~) [amd64 i386 ppc64el arm64 riscv64],
- libnuma-dev [amd64 i386 ppc64el arm64 riscv64 s390x],
- libpcap-dev [amd64 i386 ppc64el arm64 riscv64],
+ libdbus-1-dev [amd64 i386 ppc64el arm64 riscv64 loong64],
+ libdpdk-dev (>= 22.11.3-2~) [amd64 i386 ppc64el arm64 riscv64 loong64],
+ libnuma-dev [amd64 i386 ppc64el arm64 riscv64 loong64 s390x],
+ libpcap-dev [amd64 i386 ppc64el arm64 riscv64 loong64],
  libssl-dev,
  libtool,
  libunbound-dev,
@@ -180,7 +180,7 @@
  the Open vSwitch kernel-based switch.
 
 Package: openvswitch-switch-dpdk
-Architecture: amd64 arm64 i386 ppc64el riscv64
+Architecture: amd64 arm64 i386 ppc64el riscv64 loong64
 Pre-Depends: ${misc:Pre-Depends},
 Depends:
  dpdk,
diff -Nru openvswitch-3.3.0~git20240118.e802fe7/debian/rules 
openvswitch-3.3.0~git20240118.e802fe7/debian/rules
--- openvswitch-3.3.0~git20240118.e802fe7/debian/rules  2024-01-19 
11:03:39.0 +
+++ openvswitch-3.3.0~git20240118.e802fe7/debian/rules  2024-02-05 
08:45:19.0 +
@@ -34,7 +34,7 @@
 $(DATAPATH_CONFIGURE_OPTS) \
 $(EXTRA_CONFIGURE_OPTS) \
 )
-ifneq (,$(filter i386 amd64 ppc64el arm64 riscv64, $(DEB_HOST_ARCH)))
+ifneq (,$(filter i386 amd64 ppc64el arm64 riscv64 loong64, $(DEB_HOST_ARCH)))
test -d _dpdk || mkdir _dpdk
cd _dpdk && ( \
test -e Makefile || \
@@ -142,7 +142,7 @@
fi
 # Skip DPDK testing on arm64 as builders don't have crc32 support
 # which is used in aarch64 based crc optimization in ovs >= 2.12.0~
-ifneq (,$(filter i386 amd64 ppc64el riscv64, $(DEB_HOST_ARCH)))
+ifneq (,$(filter i386 amd64 ppc64el riscv64 loong64, $(DEB_HOST_ARCH)))
if $(MAKE) -C _dpdk check TESTSUITEFLAGS='$(PARALLEL) 
$(TEST_LIST_DPDK)' || \
$(MAKE) -C _dpdk check 
TESTSUITEFLAGS='--recheck'; then :; \
else \
@@ -155,7 +155,7 @@
 override_dh_auto_build:
dh_auto_build --sourcedirectory=_debian -- distdir-am 
distdir=openvswitch
dh_auto_build --sourcedirectory=_debian
-ifneq (,$(filter i386 amd64 ppc64el arm64 riscv64, $(DEB_HOST_ARCH)))
+ifneq (,$(filter i386 amd64 ppc64el arm64 riscv64 loong64, $(DEB_HOST_ARCH)))
dh_auto_build --sourcedirectory=_dpdk
 endif
 

Bug#1065587: rust-polling: Please try to rebuild rust-polling for loong64

[zhangdandan]

Source: rust-polling
Version: 3.4.0-1
Severity: wishlist
Tags: help
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The package librust-async-io-2+default-dev blocked compilation of 29 
packages in the Debian Package Auto-Building environment.

The dependency state of rust-async-io is as follows,
```
Dependency installability problem for rust-async-io on loong64:
rust-async-io build-depends on missing:
- librust-polling-3+default-dev:loong64
```
After analyzing the package rust-async-io, I found out that it's because 
compilation of rust-polling failed.
The build log of rust-polling can be found at 
https://buildd.debian.org/status/logs.php?pkg=rust-polling=3.4.0-1=loong64.


I have built the rust-polling successfully in my local loong64 
environment, without modifications required.

```
..
   dh_md5sums -O--buildsystem=cargo
   dh_builddeb -O--buildsystem=cargo
dpkg-deb: building package '../librust-polling-dev_3.4.0-1_loong64.deb' 
in 'librust-polling-dev'。

dpkg-genbuildinfo -O../rust-polling_3.4.0-1_loong64.buildinfo
dpkg-genchanges -O../rust-polling_3.4.0-1_loong64.changes

```
Please try to rebuild rust-polling for loong64 in the Debian Package 
Auto-Building environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1065586: rust-async-std: Missing installation dependency librust-async-io-2+default-dev for librust-async-std-dev

[zhangdandan]

Package: librust-async-std-dev
Version: 1.12.0-17
Severity: wishlist
Tags: help
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

For loong64 there is 1 phenomenon in the Debian Package Auto-Building 
environment.

Using the build status of python-maturin as a example,
```
Dependency installability problem for python-maturin on loong64:
python-maturin build-depends on:
- librust-configparser-dev:loong64
librust-configparser-dev depends on:
- librust-async-std-1+default-dev:loong64 (>= 1.12.0-~~) | 
librust-async-std-1+default-dev:loong64 (>= 1.12.0-~~)

librust-async-std-dev depends on missing:
- librust-async-io-2+default-dev:loong64
```
The librust-async-std-dev is built in X86 buildd ENV, please see 
https://buildd.debian.org/status/package.php?p=rust-async-std=sid
But when installing librust-async-std-dev, it depends on 
librust-async-io-2+default-dev.
I didn't find the package librust-async-io-2+default-dev in 
X86/loong64/others arch.


Please help us to solve the above question.
BTW, the package librust-async-io-2+default-dev blocked compilation of 
29 packages, provide an example,

```
94 pandoc:loong64
41 coq:loong64
34 g++-14:loong64
32 gnuplot-data:loong64
32 gnat-12:loong64
29 librust-async-io-2+default-dev:loong64 //Note that
29 libopencv-dev:loong64
27 libappstream4:loong64
```

thanks,
Dandan Zhang

Bug#1065491: qtwebkit-opensource-src: Add support for loongarch64

[zhangdandan]

Source: qtwebkit-opensource-src
Version: 5.212.0~alpha4-33
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the qtwebkit-opensource-src failed for loong64 in the Debian 
Package Auto-Building environment.

The reason is the lack of loongarch64 support in qtwebkit-opensource-src.

I have added the patch(add loongarch64 support) to upstream, please see 
the pull-request https://github.com/qtwebkit/qtwebkit/pull/1096.

But the status of pull request from upstream is still open.

Reference to other architectures, I added the loongarch64 support to the 
qtwebkit-opensource-src source package.

Please consider the patch I attached.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Description: Add loongarch64 support
Author: Dandan Zhang 
Forwarded: https://github.com/qtwebkit/qtwebkit/pull/1096
Last-Update: 2024-03-05

--- qtwebkit-opensource-src-5.212.0~alpha4.orig/CMakeLists.txt
+++ qtwebkit-opensource-src-5.212.0~alpha4/CMakeLists.txt
@@ -63,6 +63,8 @@ elseif (LOWERCASE_CMAKE_SYSTEM_PROCESSOR
 set(WTF_CPU_ARM64 1)
 elseif (LOWERCASE_CMAKE_SYSTEM_PROCESSOR MATCHES "alpha*")
 set(WTF_CPU_ALPHA 1)
+elseif (LOWERCASE_CMAKE_SYSTEM_PROCESSOR MATCHES "loongarch64")
+set(WTF_CPU_LOONGARCH64 1)
 elseif (LOWERCASE_CMAKE_SYSTEM_PROCESSOR MATCHES "^mips")
 set(WTF_CPU_MIPS 1)
 elseif (LOWERCASE_CMAKE_SYSTEM_PROCESSOR MATCHES "sh4")
--- qtwebkit-opensource-src-5.212.0~alpha4.orig/Source/JavaScriptCore/CMakeLists.txt
+++ qtwebkit-opensource-src-5.212.0~alpha4/Source/JavaScriptCore/CMakeLists.txt
@@ -1280,6 +1280,7 @@ if (WTF_CPU_ARM)
 elseif (WTF_CPU_ARM64)
 elseif (WTF_CPU_ALPHA)
 elseif (WTF_CPU_HPPA)
+elseif (WTF_CPU_LOONGARCH64)
 elseif (WTF_CPU_PPC)
 elseif (WTF_CPU_PPC64)
 elseif (WTF_CPU_PPC64LE)
--- qtwebkit-opensource-src-5.212.0~alpha4.orig/Source/WTF/wtf/Platform.h
+++ qtwebkit-opensource-src-5.212.0~alpha4/Source/WTF/wtf/Platform.h
@@ -80,6 +80,11 @@
 #endif
 #endif
 
+/* CPU(LOONGARCH64) - LoongArch 64-bit */
+#if defined(__loongarch64)
+#define WTF_CPU_LOONGARCH64 1
+#endif
+
 /* CPU(MIPS) - MIPS 32-bit and 64-bit */
 #if (defined(mips) || defined(__mips__) || defined(MIPS) || defined(_MIPS_) || defined(__mips64))
 #if defined(_ABI64) && (_MIPS_SIM == _ABI64)
@@ -713,7 +718,8 @@
 || CPU(MIPS64) \
 || CPU(PPC64) \
 || CPU(PPC64LE) \
-|| CPU(RISCV64)
+|| CPU(RISCV64) \
+|| CPU(LOONGARCH64)
 #define USE_JSVALUE64 1
 #else
 #define USE_JSVALUE32_64 1
--- qtwebkit-opensource-src-5.212.0~alpha4.orig/Source/WTF/wtf/dtoa/utils.h
+++ qtwebkit-opensource-src-5.212.0~alpha4/Source/WTF/wtf/dtoa/utils.h
@@ -49,7 +49,7 @@
 defined(__ARMEL__) || \
 defined(_MIPS_ARCH_MIPS32R2)
 #define DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS 1
-#elif CPU(MIPS) || CPU(MIPS64) || CPU(PPC) || CPU(PPC64) || CPU(PPC64LE) || CPU(SH4) || CPU(S390) || CPU(S390X) || CPU(IA64) || CPU(ALPHA) || CPU(ARM64) || CPU(HPPA) || CPU(RISCV64)
+#elif CPU(MIPS) || CPU(MIPS64) || CPU(PPC) || CPU(PPC64) || CPU(PPC64LE) || CPU(SH4) || CPU(S390) || CPU(S390X) || CPU(IA64) || CPU(ALPHA) || CPU(ARM64) || CPU(HPPA) || CPU(RISCV64) || CPU(LOONGARCH64)
 #define DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS 1
 #elif defined(_M_IX86) || defined(__i386__)
 #if defined(_WIN32)

Bug#1065467: marisa: FTBFS on loongarch64 as the test case fails

[zhangdandan]

Source: marisa
Version: 0.2.6-15
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the marisa failed for loong64 in the Debian Package 
Auto-Building environment.

The error messages is as follows,
```

   marisa 0.2.6: tests/test-suite.log


# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: base-test
===
```

The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=marisa=0.2.6-15=loong64.


After analyzing the test case failures, I have fixed wordsize detection 
for loongarch64 architecture.

Please consider the patch (my local patch) I have attached.
If you have any questions, you can contact me at any time.

BTW, the tests results and build results in my local loong64 ENV are as 
follows,

```
PASS: io-test
PASS: trie-test
PASS: vector-test
PASS: base-test
PASS: marisa-test

Testsuite summary for marisa 0.2.6

# TOTAL: 5
# PASS:  5
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

..
make[1]: Leaving directory '/home/zdd/marisa/marisa-0.2.6'
   dh_md5sums
   dh_builddeb
dpkg-deb: building package 'libmarisa-perl' in 
'../libmarisa-perl_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'libmarisa-perl-dbgsym' in 
'../libmarisa-perl-dbgsym_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'libmarisa-dev' in 
'../libmarisa-dev_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'python3-marisa' in 
'../python3-marisa_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'python3-marisa-dbgsym' in 
'../python3-marisa-dbgsym_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'ruby-marisa-dbgsym' in 
'../ruby-marisa-dbgsym_0.2.6-15_loong64.deb'.

dpkg-deb: building package 'marisa' in '../marisa_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'libmarisa0' in 
'../libmarisa0_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'libmarisa0-dbgsym' in 
'../libmarisa0-dbgsym_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'ruby-marisa' in 
'../ruby-marisa_0.2.6-15_loong64.deb'.
dpkg-deb: building package 'marisa-dbgsym' in 
'../marisa-dbgsym_0.2.6-15_loong64.deb'.

 dpkg-genbuildinfo -O../marisa_0.2.6-15_loong64.buildinfo
 dpkg-genchanges -O../marisa_0.2.6-15_loong64.changes
```

thanks,
Dandan Zhang

Description: Fix wordsize detection for loongarch64 architecture 
Last-Update: 2024-03-05

--- marisa-0.2.6.orig/include/marisa/base.h
+++ marisa-0.2.6/include/marisa/base.h
@@ -34,7 +34,7 @@ typedef uint64_t marisa_uint64;
 ( defined(__sparc__) && defined(__arch64__) ) || \
 ( defined(__riscv) && (__riscv_xlen == 64) ) || \
 defined(__mips64) || defined(__aarch64__) || defined(__s390x__) || \
-defined(__alpha__)
+defined(__alpha__) || defined(__loongarch64)
  #define MARISA_WORD_SIZE 64
 #else  // defined(_WIN64), etc.
  #define MARISA_WORD_SIZE 32

Bug#1054471: vtk9: FTBFS: add support for loongarch64

[zhangdandan]

Dear maintainers,

On Tue, 24 Oct 2023 17:28:02 +0800 zhangdandan wrote:

> Source: vtk9
> Version: 9.1.0+really9.1.0+dfsg2-7
> Severity: wishlist
> Tags: ftbfs patch
> User: debian-loonga...@lists.debian.org
> Usertags: loong64
>
> Dear maintainers,
>
> When compiling the package vtk9 for loong64 in the Debian Package

> The full compilation log can be found at [2].
>
> Please consider the patch I have attached.
> The LoongArch architecture has been supported in the vtk upstream [3].
> Would it be possible to include the support for LoongArch in the next
> upload?
Please add loongarch64 support in vtk9.
The number of libvtk9-dev:loong64 blocking compilation source packages 
is 12 in Debian Package Auto-Building.

>
> [1]:https://buildd.debian.org/status/package.php?p=vtk9=sid
> 
[2]:https://buildd.debian.org/status/logs.php?pkg=vtk9=9.1.0%2Breally9.1.0%2Bdfsg2-7=loong64
> 
[3]:https://gitlab.kitware.com/vtk/vtk/-/blob/master/Utilities/KWIML/vtkkwiml/include/kwiml/abi.h

>
> thanks,
> Dandan Zhang
>

Bug#1062361: gnss-sdr: add support for loongarch64

[zhangdandan]

Source: gnss-sdr
Version: 0.0.18-2
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add loongarch64 support in gnss-sdr.
Please consider the patch I have attached.
If the maintainer sees no problem with the patch, can also submit to 
upstream.


In addition, I give feedback on an error when compiling on my local ENV, 
for example:

```
..
/usr/include/gnuradio/io_signature.h:194:73: error: ‘string_view’ is not 
a member of ‘std’
  194 | struct GR_RUNTIME_API fmt::formatter : 
formatter {

| ^~~
/usr/include/gnuradio/io_signature.h:194:73: note: ‘std::string_view’ is 
only available from C++17 onwards
/usr/include/gnuradio/io_signature.h:194:73: error: ‘string_view’ is not 
a member of ‘std’
/usr/include/gnuradio/io_signature.h:194:73: note: ‘std::string_view’ is 
only available from C++17 onwards
/usr/include/gnuradio/io_signature.h:194:84: error: template argument 1 
is invalid
  194 | struct GR_RUNTIME_API fmt::formatter : 
formatter {

|
```

If you have any questions, you can contact me at any time.

Thanks,
Dandan Zhang

Description: Add loongarch64 support 
Last-Update: 2024-01-30

--- gnss-sdr-0.0.18.orig/CMakeLists.txt
+++ gnss-sdr-0.0.18/CMakeLists.txt
@@ -1200,7 +1200,7 @@ if(NOT VOLKGNSSSDR_FOUND)
 include(GNUInstallDirs)
 set(SUPPORTED_CPU_FEATURES_ARCH FALSE)
 if(CMAKE_SYSTEM_PROCESSOR MATCHES
-"(^mips)|(^arm)|(^aarch64)|(x86_64)|(AMD64|amd64)|(^i.86$)|(^powerpc)|(^ppc)|(^s390x)|^riscv")
+	"(^mips)|(^arm)|(^aarch64)|(x86_64)|(AMD64|amd64)|(^i.86$)|(^loongarch64)|(^loong64)|(^powerpc)|(^ppc)|(^s390x)|^riscv")
 set(SUPPORTED_CPU_FEATURES_ARCH TRUE)
 endif()
 if(${CMAKE_INSTALL_LIBDIR} MATCHES lib64)
@@ -1239,7 +1239,7 @@ if(NOT VOLKGNSSSDR_FOUND)
 set_package_properties(CPUFEATURES PROPERTIES
 DESCRIPTION "A cross platform C99 library to get CPU features at runtime (version: ${CPUFEATURES_VERSION})"
 )
-if((CMAKE_SYSTEM_PROCESSOR MATCHES "(^s390x)|^riscv") AND (CPUFEATURES_VERSION VERSION_LESS "0.8.0")) # detect cpu_features without s390x / riscv support
+		if((CMAKE_SYSTEM_PROCESSOR MATCHES "(^s390x)|^riscv|(^loongarch64)|(^loong64)") AND (CPUFEATURES_VERSION VERSION_LESS "0.8.0")) # detect cpu_features without s390x / riscv support
 set(ENABLE_CPUFEATURES OFF)
 endif()
 else()
--- gnss-sdr-0.0.18.orig/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/CMakeLists.txt
+++ gnss-sdr-0.0.18/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/CMakeLists.txt
@@ -258,7 +258,7 @@ endif()
 
 # cpu_features - sensible defaults, user settable option
 if(CMAKE_SYSTEM_PROCESSOR MATCHES
-"(^mips)|(^arm)|(^aarch64)|(x86_64)|(AMD64|amd64)|(^i.86$)|(^powerpc)|(^ppc)|(^s390x)|^riscv")
+"(^mips)|(^arm)|(^aarch64)|(x86_64)|(AMD64|amd64)|(^i.86$)|(^loongarch64)|(^loong64)|(^powerpc)|(^ppc)|(^s390x)|^riscv")
 option(VOLK_CPU_FEATURES "volk-gnsssdr uses cpu_features" ON)
 else()
 option(VOLK_CPU_FEATURES "volk-gnsssdr uses cpu_features" OFF)
@@ -266,7 +266,7 @@ endif()
 
 if(CMAKE_VERSION VERSION_GREATER 3.0 AND VOLK_CPU_FEATURES)
 find_package(CPUFEATURES)
-if(CPUFEATURES_FOUND AND (CMAKE_SYSTEM_PROCESSOR MATCHES "(^s390x)|^riscv") AND (CPUFEATURES_VERSION VERSION_LESS "0.8.0"))
+if(CPUFEATURES_FOUND AND (CMAKE_SYSTEM_PROCESSOR MATCHES "(^s390x)|^riscv|(^loongarch64)|(^loong64)") AND (CPUFEATURES_VERSION VERSION_LESS "0.8.0"))
 set(USE_CPU_FEATURES OFF)
 unset(CPUFEATURES_FOUND CACHE)
 message(STATUS "Building volk-gnsssdr without cpu_features, installed version v${CPUFEATURES_VERSION} does not support the ${CMAKE_SYSTEM_PROCESSOR} architecture")
--- gnss-sdr-0.0.18.orig/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cpu_features/CMakeLists.txt
+++ gnss-sdr-0.0.18/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cpu_features/CMakeLists.txt
@@ -54,6 +54,7 @@ set(PROCESSOR_IS_MIPS FALSE)
 set(PROCESSOR_IS_ARM FALSE)
 set(PROCESSOR_IS_AARCH64 FALSE)
 set(PROCESSOR_IS_X86 FALSE)
+set(PROCESSOR_IS_LOONGARCH64 FALSE)
 set(PROCESSOR_IS_POWER FALSE)
 set(PROCESSOR_IS_S390X FALSE)
 set(PROCESSOR_IS_RISCV FALSE)
@@ -66,6 +67,8 @@ elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^
   set(PROCESSOR_IS_ARM TRUE)
 elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "(x86_64)|(AMD64|amd64)|(^i.86$)")
   set(PROCESSOR_IS_X86 TRUE)
+elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(loongarch64)|^(loong64)")
+  set(PROCESSOR_IS_LOONGARCH64 TRUE)
 elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(powerpc|ppc)")
   set(PROCESSOR_IS_POWER TRUE)
 elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(s390x)")
@@ -90,6 +93,8 @@ macro(add_cpu_features_headers_and_sourc
   list(APPEND ${HDRS_LIST_NAME} ${PROJECT_SOURCE_DIR}/include/cpuinfo_x86.h)
   list(APPEND ${SRCS_LIST_NAME} ${PROJECT_SOURCE_DIR}/include/internal/cpuid_x86.h)
   list(APPEND ${SRCS_LIST_NAME} 

Bug#1061728: fio: add build support for loongarch64

[zhangdandan]

Hi,
    I'm very happy to receive your timely reply. Nice to meet you.
在 2024/1/29 下午5:08, Martin Steigerwald 写道:

Hi Dandan.

Thanks for your in-advance notice.
Am Montag, dem 29.01.2024 um 15:57 +0800 schrieb zhangdandan:
> I would like to remind you that the compilation dependency of fio is
> not yet satisfied. Depends on the librbd-dev and libnbd-dev packages
> when compiling fio.

So about timing: Does it make sense to include your patch in the next
upload already or do you prefer me to wait until further notice?
I will also actively pay attention to whether fio's dependency packages 
are satisfied.

About timing, I believe your solution will be more appropriate.

I intend to wait for next fio release until uploading again.


I agree with your plan, thank you.

Regards,
Dandan

Bug#1061728: fio: add build support for loongarch64

[zhangdandan]

Source: fio
Version: 3.36-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Maybe we need to add build support for loongarch64.
I hope to give you feedback in advance.
Please consider the patch I have attached.

I would like to remind you that the compilation dependency of fio is not 
yet satisfied. Depends on the librbd-dev and libnbd-dev packages when 
compiling fio.
About the dependencies packages, such as librbd-dev and libnbd-dev, we 
have also submitted bug separately to BTS to add loongarch64 support.
The fio source package was compiled successfully on my local loong64 
rootfs environment, for example:


```
make[1]: Leaving directory '/home/fio/fio-3.36'
   dh_auto_test
   make -j32 test "TESTSUITEFLAGS=-j32 --verbose" VERBOSE=1
make[1]: Entering directory '/home/fio/fio-3.36'
./fio --minimal --thread --exitall_on_error --runtime=1s --name=nulltest 
--ioengine=null --rw=randrw --iodepth=2 --norandommap 
--random_generator=tausworthe64 --size=16T --name=verifyfstest 
--filename=fiotestfile.tmp --unlink=1 --rw=write --verify=crc32c 
--verify_state_save=0 --size=16K

3;fio-3.36;nulltest;0;0;2045220;2045220;511305;1000;0;83;0.104989;0.11;0;49;0.541493;0.089076;1.00%=0;5.00%=0;10.00%=0;20.00%=0;30.00%=0;40.00%=0;50.00%=0;60.00%=0;70.00%=0;80.00%=0;90.00%=0;95.00%=0;99.00%=0;99.50%=0;99.90%=0;99.95%=0;99.99%=2;0%=0;0%=0;0%=0;0;84;0.646483;0.150796;2046475;2046475;100.00%;2046475.00;0.00;2042196;2042196;510549;1000;0;3;0.107921;0.010351;0;14;0.542254;0.044376;1.00%=0;5.00%=0;10.00%=0;20.00%=0;30.00%=0;40.00%=0;50.00%=0;60.00%=0;70.00%=0;80.00%=0;90.00%=0;95.00%=0;99.00%=0;99.50%=0;99.90%=0;99.95%=0;99.99%=2;0%=0;0%=0;0%=0;0;14;0.650175;0.045519;2043635;2043635;100.00%;2043635.00;0.00;99.70%;0.00%;2;0;0;100.0%;0.0%;0.0%;0.0%;0.0%;0.0%;0.0%;99.99%;0.01%;0.01%;0.01%;0.01%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%
..
dpkg-deb: building package 'fio-dbgsym' in 
'../fio-dbgsym_3.36-1_loong64.deb'.
dpkg-deb: building package 'fio-examples' in 
'../fio-examples_3.36-1_all.deb'.

dpkg-deb: building package 'fio' in '../fio_3.36-1_loong64.deb'.
```

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru fio-3.36/debian/control fio-3.36/debian/control
--- fio-3.36/debian/control 2023-10-23 09:47:12.0 +
+++ fio-3.36/debian/control 2023-10-23 09:47:12.0 +
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Martin Steigerwald 
-Build-Depends: debhelper-compat (= 13), libaio-dev [linux-any], zlib1g-dev, 
librdmacm-dev [linux-any], libibverbs-dev [linux-any], librbd-dev [linux-amd64 
linux-arm64 linux-ppc64el linux-ppc64 linux-riscv64 linux-mips64el linux-s390x 
linux-ia64 linux-sparc64], libcairo2-dev, libnuma-dev [linux-any], flex, bison, 
sphinx, python3-sphinx, libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 
mips64el s390x ia64 sparc64], libpmem-dev [amd64 arm64 ppc64el], libnbd-dev
+Build-Depends: debhelper-compat (= 13), libaio-dev [linux-any], zlib1g-dev, 
librdmacm-dev [linux-any], libibverbs-dev [linux-any], librbd-dev [linux-amd64 
linux-arm64 linux-loong64 linux-ppc64el linux-ppc64 linux-riscv64 
linux-mips64el linux-s390x linux-ia64 linux-sparc64], libcairo2-dev, 
libnuma-dev [linux-any], flex, bison, sphinx, python3-sphinx, libglusterfs-dev 
[amd64 arm64 loong64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64], 
libpmem-dev [amd64 arm64 ppc64el], libnbd-dev
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
 Homepage: https://github.com/axboe/fio

Bug#1061542: tracker-miners: FTBFS on amd64, arm64, loong64 and so on

[zhangdandan]

Source: tracker-miners
Version: 3.4.6-2
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The package tracker-miners failed to compile on amd64, arm64, loong64 
and other architectures in the Debian Package Auto-Building environment. 
The error messages are as follows,

```
..
=== 54/54 


test: tracker-miners:examples / query-sync
start time:   21:21:01
duration: 1.68s
result:   exit status 0
command: ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/usr/lib/loongarch64-linux-gnu 
TRACKER_EXAMPLES_AUTOMATED_TEST=1 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 
TEST_ONTOLOGIES_DIR=/usr/share/tracker3/ontologies/nepomuk 
MALLOC_PERTURB_=224 /usr/bin/python3 
/<>/obj-loongarch64-linux-gnu/run-uninstalled 
--store-tmpdir /<>/examples/python/query-sync.py
--- stdout 
---

Music albums:
--- stderr 
---
(tracker-miner-fs-3:1266574): Tracker-WARNING **: 21:21:01.850: Locale 
'LANG' is not set, defaulting to C locale
(tracker-miner-fs-3:1266574): libupower-glib-WARNING **: 21:21:02.093: 
Couldn't connect to proxy: Could not connect: No such file or directory
(tracker-miner-fs-3:1266574): Tracker-WARNING **: 21:21:02.093: Unable 
to connect to UPower

==


Summary of Failures:

21/54 tracker-miners:extractor+audio / mp3-id3v2.4-1  
FAIL 0.20s   exit status 1
22/54 tracker-miners:extractor+audio / mp3-id3v2.3-empty-artist-album 
FAIL 0.18s   exit status 1
23/54 tracker-miners:extractor+audio / mp3-id3v2.4-2  
FAIL 0.18s   exit status 1
24/54 tracker-miners:extractor+desktop / application  
FAIL 0.18s   exit status 1
25/54 tracker-miners:extractor+desktop / link-wikipedia-tracker   
FAIL 0.18s   exit status 1
26/54 tracker-miners:extractor+audio / flac-musicbrainz   
FAIL 0.18s   exit status 1
27/54 tracker-miners:extractor+audio / vorbis-musicbrainz 
FAIL 0.18s   exit status 1
28/54 tracker-miners:extractor+images / jpeg-basic    
FAIL 0.18s   exit status 1
29/54 tracker-miners:extractor+images / jpeg-region-of-interest   
FAIL 0.18s   exit status 1
30/54 tracker-miners:extractor+images / jpeg-gps-location 
FAIL 0.18s   exit status 1
31/54 tracker-miners:extractor+images / jpeg-iptc-tags    
FAIL 0.18s   exit status 1
32/54 tracker-miners:extractor+images / jpeg-iptcdata-records 
FAIL 0.18s   exit status 1
33/54 tracker-miners:extractor+images / gif-comment-extension-block   
FAIL 0.18s   exit status 1
35/54 tracker-miners:extractor+images / gif-xmp   
FAIL 0.18s   exit status 1
36/54 tracker-miners:extractor+images / png-basic 
FAIL 0.18s   exit status 1
37/54 tracker-miners:extractor+images / png-region-of-interest    
FAIL 0.18s   exit status 1
38/54 tracker-miners:extractor+images / raw-cr2   
FAIL 0.18s   exit status 1
39/54 tracker-miners:extractor+images / tiff-basic    
FAIL 0.18s   exit status 1
40/54 tracker-miners:extractor+playlists / playlist-test-1    
FAIL 0.18s   exit status 1
42/54 tracker-miners:extractor+office / oasis-doc 
FAIL 0.18s   exit status 1
43/54 tracker-miners:extractor+office / office-doc    
FAIL 0.18s   exit status 1
44/54 tracker-miners:extractor+office / powerpoint    
FAIL 0.18s   exit status 1
45/54 tracker-miners:extractor+office / pdf-doc   
FAIL 0.18s   exit status 1
46/54 tracker-miners:extractor+office / ps-doc    
FAIL 0.18s   exit status 1
47/54 tracker-miners:extractor+office / ps-doc-atend  
FAIL 0.18s   exit status 1
48/54 tracker-miners:extractor+office / psgz-doc  
FAIL 0.18s   exit status 1
49/54 tracker-miners:extractor+video / mkv-basic  
FAIL 0.18s   exit status 1
50/54 tracker-miners:extractor+video / mov-basic  
FAIL 0.18s   exit status 1
51/54 tracker-miners:extractor+video / mp4-basic  
FAIL 0.18s   exit status 1
52/54 tracker-miners:extractor+video / mp4-video-without-audio    
FAIL 0.18s   exit status 1


Ok: 24
Expected Fail:  0
Fail:   30
Unexpected 

Bug#1061384: acl2: add support for loongarch64

[zhangdandan]

Source: acl2
Version: 8.5dfsg-5
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Maybe we need to add LoongArch support in 
books/kestrel/x86/parsers/parse-pe-file.lisp.

Refer to riscv64, please consider the patch I have attached.
If you have better modification suggestions, please help us fix this patch.

I would like to remind you that the compilation dependency of acl2 is 
not yet satisfied. Depends on the gcl ( >= 2.6.14-1) package when 
compiling acl2.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Description: Add PE header machine type for LoongArch
Last-Update: 2024-01-23

--- acl2-8.5dfsg.orig/books/kestrel/x86/parsers/parse-pe-file.lisp
+++ acl2-8.5dfsg/books/kestrel/x86/parsers/parse-pe-file.lisp
@@ -93,6 +93,8 @@
 (#xebc . :IMAGE_FILE_MACHINE_EBC)
 (#x14c . :IMAGE_FILE_MACHINE_I386)
 (#x200 . :IMAGE_FILE_MACHINE_IA64)
+(#x6232 . :IMAGE_FILE_MACHINE_LOONGARCH32)
+(#x6264 . :IMAGE_FILE_MACHINE_LOONGARCH64)
 (#x9041 . :IMAGE_FILE_MACHINE_M32R)
 (#x266 . :IMAGE_FILE_MACHINE_MIPS16)
 (#x366 . :IMAGE_FILE_MACHINE_MIPSFPU)

Bug#1061108: llvmlite: FTBFS depends on llvm-14

[zhangdandan]

Source: llvmlite
Version: 0.41.1-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

When I compiled llvmlite 0.41.1-1 which depends llvm-14, and the code is 
forced to depend on llvm-14.
The pool-loong64 repository in Debian-ports only has llvm-toolchain-16 
and llvm-toolchain-17.


I download llvmlite 0.39.1, and modify the the llvm version in 
d/control, d/rules.

Build llvmlite 0.39.1 with llvm-13 (form my local repository).
The result is that the llvm version that llvmlite 0.39.1 depends on is 
modified to llvm-13 and the compilation is normal.


But llvmlite 0.41.1-1 is forced to depend on llvm-14.
Could the llvmlite source code be considered compatible with newer llvm 
versions, such as llvm-16 or the lastest llvm version?


thanks,
Dandan Zhang

Bug#1060900: freebsd-buildutils: add e_machine judgment for loongarch

[zhangdandan]

Source: freebsd-buildutils
Version: 10.3~svn296373-7.1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

I have added e_machine judgment for loongarch in 
src/usr.bin/elfdump/elfdump.c.

Reference,
/* Legal values for e_machine (architecture).  */
#define EM_NONE  0  /* No machine */
#define EM_M32   1  /* AT WE 32100 */
#define EM_SPARC 2  /* SUN SPARC */
..
#define EM_CSKY 252 /* C-SKY */
#define EM_LOONGARCH    258 /* LoongArch */

Please consider the patch I have attached.
I would like to remind you that the compilation dependency of 
freebsd-buildutils is not yet satisfied.
Depends on gcc-9 when compiling freebsd-buildutils, please see d/control 
and d/rules.
The LoongArch architecture was supported in Debian GCC since version 
12.2.0-14.


If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Description: Add e_machine judgment for loongarch
Last-Update: 2024-01-16

--- freebsd-buildutils-10.3~svn296373.orig/src/usr.bin/elfdump/elfdump.c
+++ freebsd-buildutils-10.3~svn296373/src/usr.bin/elfdump/elfdump.c
@@ -273,6 +273,7 @@ e_machines(u_int mach)
 	case EM_X86_64:	return "EM_X86_64";
 	case EM_AARCH64:return "EM_AARCH64";
 	case EM_RISCV:	return "EM_RISCV";
+	case EM_LOONGARCH: return "EM_LOONGARCH";
 	}
 	snprintf(machdesc, sizeof(machdesc),
 	"(unknown machine) -- type 0x%x", mach);

Bug#1060886: swupdate: Additional dependency support may need to be added

[zhangdandan]

Source: swupdate
Version: 2023.12+dfsg-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The swupdate source package (pull from sid) was compiled successfully on 
my local loong64 rootfs environment.
But refer to other architectures, maybe we need to add additional 
dependency support in d/control and d/rules.
I would like to remind you there is no package for loong64 yet about the 
additional dependency.


I reported this phenomenon (whether additional dependency support is 
needed?) in advance and hope to get suggestions from the maintainers.

Please consider the patch (my local patch) I have attached.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff --git a/debian/control b/debian/control
index acbecd4..62c39ff 100644
--- a/debian/control
+++ b/debian/control
@@ -36,7 +36,7 @@ Build-Depends: debhelper-compat (= 13),
libwebsockets-dev (>= 3.2.0) ,
liburiparser-dev,
libubootenv-dev (>= 0.3.5) [linux-any],
-   libebgenv-dev [any-amd64 any-i386 any-arm64 armhf any-riscv64 any-ia64],
+   libebgenv-dev [any-amd64 any-i386 any-arm64 armhf any-loong64 any-riscv64 any-ia64],
libcmocka-dev,
node-jquery,
pkg-config,
diff --git a/debian/rules b/debian/rules
index 3b1cc0f..8444b49 100755
--- a/debian/rules
+++ b/debian/rules
@@ -41,7 +41,7 @@ endif
 ifeq (,$(filter pkg.swupdate.bpo,$(DEB_BUILD_PROFILES)))
 	echo CONFIG_DELTA=y >> configs/debian_defconfig
 endif
-ifneq (,$(findstring $(DEB_HOST_ARCH),amd64 i386 arm64 armhf riscv64 ia64))
+ifneq (,$(findstring $(DEB_HOST_ARCH),amd64 i386 arm64 armhf loong64 riscv64 ia64))
 	echo CONFIG_BOOTLOADER_EBG=y>> configs/debian_defconfig
 endif
 ifeq (,$(filter pkg.swupdate.nohwcompat,$(DEB_BUILD_PROFILES)))
-- 
2.43.0

Bug#1060884: efibootguard: add support for loongarch64

[zhangdandan]

Source: efibootguard
Version: 0.15-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Maybe we need to add loongarch64 support in configure.ac.
Please consider the patch I have attached.

I would like to remind you that the compilation dependency of 
efibootguard is not yet satisfied. Depends on the gnu-efi package when 
compiling efibootguard.
We hope that the gnu-efi source package can support the loongarch 
architecture (LoongArch patch has been merged in upstream).
We have submitted the Bug request to Debian BTS, please see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025787.


If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff --git a/configure.ac b/configure.ac
index 90d70b0..cd02a11 100644
--- a/configure.ac
+++ b/configure.ac
@@ -88,6 +88,7 @@ SET_ARCH(IA64, ia64*)
 SET_ARCH(AARCH64, aarch64*)
 SET_ARCH(ARM, arm*)
 SET_ARCH(RISCV64, riscv64*)
+SET_ARCH(LOONGARCH64, loongarch64*)
 
 ARCH=$(echo $host | sed "s/\(-\).*$//")
 
@@ -107,6 +108,9 @@ AM_COND_IF(ARCH_ARM, [
 AM_COND_IF(ARCH_RISCV64, [
   MACHINE_TYPE_NAME=riscv64])
 
+AM_COND_IF(ARCH_LOONGARCH64, [
+  MACHINE_TYPE_NAME=loongarch64])
+
 AC_SUBST([ARCH])
 AC_SUBST([MACHINE_TYPE_NAME])
 AM_CONDITIONAL([ARCH_IS_X86], [test "$ARCH" = "ia32" -o "$ARCH" = "x86_64"])

Bug#1059276: python-demgengeo: FTBFS on loongarch64 - error: cannot find the flags to link with Boost system

[zhangdandan]

Dear maintainers,

>
> The full log can be found at
> 
https://buildd.debian.org/status/logs.php?pkg=python-demgengeo=1.4-4.1=loong64

> Referring to other architectures, the relevant bug is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829143
>
> Please add loongarch64 directories in m4/boost.m4.

I have added loongarch64 support in python-demgengeo.
Please consider the patch (my local patch) I have attached.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang


Description: Add loongarch64 support
Last-Update: 2023-12-23

--- python-demgengeo-1.4.orig/m4/boost.m4
+++ python-demgengeo-1.4/m4/boost.m4
@@ -491,17 +491,17 @@ for boost_py_ in '' ${python_suffix}; do
   possible_paths="${with_boost}/lib ${with_boost}"
 else
   possible_paths="${boost_cv_inc_path%/include}/lib \
-/usr/lib*/x86_64* /usr/lib*/i386* /usr/lib*/aarch64* /usr/lib*/alpha* /usr/lib*/arm* /usr/lib*/ia64* /usr/lib*/hppa* /usr/lib*/mips* /usr/lib*/m68k* \
+/usr/lib*/x86_64* /usr/lib*/i386* /usr/lib*/aarch64* /usr/lib*/alpha* /usr/lib*/arm* /usr/lib*/ia64* /usr/lib*/hppa* /usr/lib*/loongarch64*/ /usr/lib*/mips* /usr/lib*/m68k* \
   /usr/lib*/powerpc* /usr/lib*/ppc64* /usr/lib*/riscv64* /usr/lib*/s390* /usr/lib*/sh4* /usr/lib*/sparc* /usr/lib* \
 /usr/local/lib*/x86_64* /usr/local/lib*/i386* /usr/local/lib*/aarch64* /usr/local/lib*/alpha* /usr/local/lib*/arm* /usr/local/lib*/ia64* \
-  /usr/local/lib*/hppa* /usr/local/lib*/mips* /usr/local/lib*/m68k* /usr/local/lib*/powerpc* /usr/local/lib*/ppc64* /usr/local/lib*/riscv64* /usr/local/lib*/s390* \
+  /usr/local/lib*/hppa* /usr/local/lib*/loongarch64* /usr/local/lib*/mips* /usr/local/lib*/m68k* /usr/local/lib*/powerpc* /usr/local/lib*/ppc64* /usr/local/lib*/riscv64* /usr/local/lib*/s390* \
   /usr/local/lib*/sh4* /usr/local/lib*/sparc* /usr/local/lib* \
-/opt/lib*/x86_64* /opt/lib*/i386* /opt/lib*/aarch64* /opt/lib*/alpha* /opt/lib*/arm* /opt/lib*/ia64* /opt/lib*/hppa* /opt/lib*/mips* /opt/lib*/m68k* \
+/opt/lib*/x86_64* /opt/lib*/i386* /opt/lib*/aarch64* /opt/lib*/alpha* /opt/lib*/arm* /opt/lib*/ia64* /opt/lib*/hppa* /opt/lib*/loongarch64* /opt/lib*/mips* /opt/lib*/m68k* \
   /opt/lib*/powerpc* /opt/lib*/ppc64* /opt/lib*/riscv64* /opt/lib*/s390* /opt/lib*/sh4* /opt/lib*/sparc* /opt/lib* \
 /opt/local/lib*/x86_64* /opt/local/lib*/i386* /opt/local/lib*/aarch64* /opt/local/lib*/alpha* /opt/local/lib*/arm* /opt/local/lib*/ia64*\
-  /opt/local/lib*/hppa* /opt/local/lib*/mips* /opt/local/lib*/m68k* /opt/local/lib*/powerpc* /opt/local/lib*/ppc64* /opt/local/lib*/riscv64* /opt/local/lib*/s390* \
+  /opt/local/lib*/hppa* /opt/local/lib*/loongarch64* /opt/local/lib*/mips* /opt/local/lib*/m68k* /opt/local/lib*/powerpc* /opt/local/lib*/ppc64* /opt/local/lib*/riscv64* /opt/local/lib*/s390* \
   /opt/local/lib*/sh4* /opt/local/lib*/sparc* /opt/local/lib* \
-/lib*/x86_64* /lib*/i386* /lib*/aarch64* /lib*/alpha* /lib*/arm* /lib*/ia64* /lib*/hppa* /lib*/mips* /lib*/m68k* \
+/lib*/x86_64* /lib*/i386* /lib*/aarch64* /lib*/alpha* /lib*/arm* /lib*/ia64* /lib*/hppa* /lib*/loongarch64* /lib*/mips* /lib*/m68k* \
   /lib*/powerpc* /lib*/ppc64* /lib*/riscv64* /lib*/s390* /lib*/sh4* /lib*/sparc* /lib* \
 C:/Boost/lib"
 fi

Bug#1060368: partman-auto: add basic support for loongarch64

[zhangdandan]

Source: partman-auto
Version: 163
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Support automatic partition adaptation partman-auto for debian-installer.
Please consider the patch (my local patch) I have attached.
If the content of my local patch does not meet the specifications, 
please contact me.
According to the maintainer's suggestions, it may be necessary to 
continue updating or modifying this patch.


I integrated partman-auto_163+loong64_loong64.udeb in my local DVD iso. 
When installing the system through debian-installer, supports automatic 
partitioning function by default.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru partman-auto-163/debian/changelog 
partman-auto-163+loong64/debian/changelog
--- partman-auto-163/debian/changelog   2023-09-24 09:38:45.0 +
+++ partman-auto-163+loong64/debian/changelog   2023-12-14 06:44:04.0 
+
@@ -1,3 +1,9 @@
+partman-auto (163+loong64) unstable; urgency=medium
+
+  * add version 
+  * add basic loongarch64 support (local patch).
+  * If the content of this patch does not meet the specifications, 
+  * please contact me.
+
+ -- Dandan Zhang   Thu, 14 Dec 2023 14:44:04 +0800
+
 partman-auto (163) unstable; urgency=medium
 
   * Team upload
diff -Nru partman-auto-163/recipes-loong64/_numbers 
partman-auto-163+loong64/recipes-loong64/_numbers
--- partman-auto-163/recipes-loong64/_numbers   1970-01-01 00:00:00.0 
+
+++ partman-auto-163+loong64/recipes-loong64/_numbers   2023-11-13 
09:08:20.0 +
@@ -0,0 +1,3 @@
+30 atomic
+50 home
+80 multi
diff -Nru partman-auto-163/recipes-loong64/atomic 
partman-auto-163+loong64/recipes-loong64/atomic
--- partman-auto-163/recipes-loong64/atomic 1970-01-01 00:00:00.0 
+
+++ partman-auto-163+loong64/recipes-loong64/atomic 2023-11-20 
07:19:21.0 +
@@ -0,0 +1,33 @@
+partman-auto/text/atomic_scheme ::
+
+300 512 300 ext2
+   $iflabel{ gpt }
+   $primary{ }
+   $bootable{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   filesystem{ ext2 }
+   mountpoint{ /boot } .
+
+300 512 300 fat32
+$lvmok{ }
+method{ format }
+format{ }
+use_filesystem{ }
+filesystem{ fat32 }
+mountpoint{ /boot/efi } .
+
+800 1 -1 $default_filesystem
+   $lvmok{ }
+   $primary{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   $default_filesystem{ }
+   mountpoint{ / } .
+
+100% 512 300% linux-swap
+   $lvmok{ }
+   method{ swap }
+   format{ } .
diff -Nru partman-auto-163/recipes-loong64/home 
partman-auto-163+loong64/recipes-loong64/home
--- partman-auto-163/recipes-loong64/home   1970-01-01 00:00:00.0 
+
+++ partman-auto-163+loong64/recipes-loong64/home   2023-11-20 
07:30:06.0 +
@@ -0,0 +1,42 @@
+partman-auto/text/home_scheme ::
+
+300 512 300 ext2
+   $iflabel{ gpt }
+   $primary{ }
+   $bootable{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   filesystem{ ext2 }
+   mountpoint{ /boot } .
+
+300 512 300 fat32
+$lvmok{ }
+method{ format }
+format{ }
+use_filesystem{ }
+filesystem{ fat32 }
+mountpoint{ /boot/efi } .
+
+1500 6000 2 $default_filesystem
+   $lvmok{ }
+   $primary{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   $default_filesystem{ }
+   mountpoint{ / } .
+
+100% 512 300% linux-swap
+   $lvmok{ }
+   method{ swap }
+   format{ } .
+
+1000 1 -1 $default_filesystem
+   $lvmok{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   $default_filesystem{ }
+   mountpoint{ /home } .
+
diff -Nru partman-auto-163/recipes-loong64/multi 
partman-auto-163+loong64/recipes-loong64/multi
--- partman-auto-163/recipes-loong64/multi  1970-01-01 00:00:00.0 
+
+++ partman-auto-163+loong64/recipes-loong64/multi  2023-11-20 
07:30:20.0 +
@@ -0,0 +1,58 @@
+partman-auto/text/multi_scheme ::
+
+300 512 300 ext2
+   $iflabel{ gpt }
+   $primary{ }
+   $bootable{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   filesystem{ ext2 }
+   mountpoint{ /boot } .
+
+300 512 300 fat32
+$lvmok{ }
+method{ format }
+format{ }
+use_filesystem{ }
+filesystem{ fat32 }
+mountpoint{ /boot/efi } .
+
+2000 3500 25000 $default_filesystem
+   $lvmok{ }
+   $primary{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   $default_filesystem{ }
+   mountpoint{ / } .
+
+1000 1500 1 $default_filesystem
+   $lvmok{ }
+   method{ format }
+   format{ }
+   use_filesystem{ }
+   $default_filesystem{ }
+   mountpoint{ /var } .
+
+100% 512 300% linux-swap
+

Bug#1060136: nbdkit: add dependencies when executing dh_auto_test

[zhangdandan]

Source: nbdkit
Version: 1.36.2-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

When compiling the package nbdkit for loong64 in my local loong64 
environment.
I found that maybe we need to add dependencies in d/control when 
executing dh_auto_test.


Please consider the patch I have attached.
I would like to remind you that the compilation dependencies of loong64 
nbdkit are not yet satisfied.
The current unmet dependencies are libguestfs-tools and 
libguestfs-dev(>= 1:1.36.11-3).

We want to give feedback in advance, please don't feel pressured.
If you have any questions, you can contact me at any time.


thanks,
Dandan Zhang

diff --git a/debian/control b/debian/control
index f8089c0..9a91ccc 100644
--- a/debian/control
+++ b/debian/control
@@ -33,6 +33,7 @@ Build-Depends: debhelper-compat (= 12),
  linux-image-4kc-malta [mips mipsel]  | linux-image-5kc-malta [mips 
mipsel] ,
  linux-image-5kc-malta [mips64 mips64el] ,
  linux-image-686-pae [i386]  | linux-image-586 [i386]  | 
linux-image-486 [i386] ,
+ linux-image-loong64 [loong64] ,
  linux-image-powerpc64le [ppc64el] ,
  linux-image-riscv64 [riscv64] ,
  linux-image-s390x [s390x] ,
@@ -41,7 +42,7 @@ Build-Depends: debhelper-compat (= 12),
  jq ,
  socat ,
 # libguestfs does noot currently work on armel, mipsel, mips64el
- libguestfs-tools [amd64 arm64 armhf i386 ppc64el riscv64 s390x] ,
+ libguestfs-tools [amd64 arm64 armhf i386 loong64 ppc64el riscv64 s390x] 
,
  libnbd-dev,
  libnbd-bin ,
  python3-libnbd ,

Bug#1059090: elpi: add build support for loongarch64

[zhangdandan]

Hi,

On Wed, 20 Dec 2023 08:28:45 +0100 Julien Puydt wrote:

> I would like to remind you that the compilation dependencies of loong64
> > elpi are not yet satisfied.
> > If you have any questions, you can contact me at any time.
> >
>
> I guess you're working your way up and you want to remove future easy
> hurdles already.
Yes, as you said.
> I'll get this out of your way, but notice all Coq packages are mostly
> blocked since weeks - I'll push the change for elpi on salsa but won't
> upload before I can get everything in shape, probably not before january.
>
Thanks for your understanding and help.

Sincerely,
Dandan Zhang

Bug#1060131: pydevd: FAILED tests_python/test_debugger_json.py::test_notify_gevent

[zhangdandan]

Source: pydevd
Version: 2.10.0+ds-8
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

When compiling the package pydevd for loong64 in the Debian Package 
Auto-Building environment, the error message are as follows:

..omit
tests_python/test_tracing_on_top_level.py:121
/<>/.pybuild/cpython3_3.11_pydevd/build/tests_python/test_tracing_on_top_level.py:121: 
PytestDeprecationWarning: @pytest.yield_fixture is deprecated.

  Use @pytest.fixture instead; they are the same.
    @pytest.yield_fixture

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 

FAILED tests_python/test_debugger_json.py::test_notify_gevent - 
AssertionErro...
= 1 failed, 758 skipped, 71 deselected, 11 warnings in 19.10s 
==

*** END OF RUN 5: NOT ALL TESTS HAVE YET PASSED/XFAILED ***
*** SOME TESTS FAILED/ERRORED EVERY RUN, ABORTING ***
..omit

The full compilation log can be found at 
https://buildd.debian.org/status/logs.php?pkg=pydevd=2.10.0%2Bds-8=loong64


After analysis, I found that the linux-libc-dev_6.6.8-1 lacks 
loongarch's header files when compiling pydev in Debian Package 
Auto-Building environment.

```
creating build/temp.linux-loongarch64-cpython-311/_pydevd_bundle
loongarch64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall 
-g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-DPy_BUILD_CORE_MODULE=1 -I/usr/include/python3.11 -c 
_pydevd_bundle/pydevd_cython.c -o 
build/temp.linux-loongarch64-cpython-311/_pydevd_bundle/pydevd_cython.o 
-flto

In file included from /usr/include/loongarch64-linux-gnu/bits/errno.h:26,
 from /usr/include/errno.h:28,
 from /usr/include/python3.11/Python.h:25,
 from _pydevd_bundle/pydevd_cython.c:19:
/usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file 
or directory

    1 | #include 
  |  ^
compilation terminated.
error: command '/usr/bin/loongarch64-linux-gnu-gcc' failed with exit code 1
```
We have updated the linux-libc-dev_6.6.9-1 (including 
/usr/include/loongarch64-linux-gnu/asm/errno.h)to debian ports.

The pydevd source package was compiled successfully on my local environment.
Feedback the above phenomenon to the maintainer, please help us to giveback.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059991: grub-installer: build loong64.udeb for loongarch64

[zhangdandan]

Source: grub-installer
Version: 1.197
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in debian/control.
Please consider the patch I have attached.

The grub-installer source package was compiled successfully on my local 
environment.
I integrated grub-installer_1.197_loong64.udeb in my local DVD iso. When 
installing the DVD iso through debian-installer, grub2 software packages 
can be installed normally.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru grub-installer-1.197/debian/control 
grub-installer-1.197/debian/control
--- grub-installer-1.197/debian/control 2023-09-20 11:00:26.0 +
+++ grub-installer-1.197/debian/control 2023-09-20 11:00:26.0 +
@@ -8,7 +8,7 @@
 Vcs-Git: https://salsa.debian.org/installer-team/grub-installer.git
 
 Package: grub-installer
-Architecture: amd64 arm64 armhf i386 ia64 hurd-i386 kfreebsd-i386 
kfreebsd-amd64 mipsel powerpc ppc64 ppc64el sparc sparc64
+Architecture: amd64 arm64 armhf i386 ia64 hurd-i386 kfreebsd-i386 
kfreebsd-amd64 loong64 mipsel powerpc ppc64 ppc64el sparc sparc64
 XB-Subarchitecture: ${subarch}
 Provides: bootable-system
 Depends: ${shlibs:Depends}, ${misc:Depends}, kernel-installer, created-fstab, 
di-utils, di-utils-mapdevfs, os-prober, partman-utils

Bug#1059989: snap-aligner: add build support for loongarch64

[zhangdandan]

Source: snap-aligner
Version: 2.0.3+dfsg-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The snap-aligner could not be compiled for loong64 in Debian Package 
Auto-Building.
Please see 
https://buildd.debian.org/status/package.php?p=snap-aligner=sid


Please pay attention to this phenomenon that I reported.
Patch attached.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru snap-aligner-2.0.3+dfsg/debian/control 
snap-aligner-2.0.3+dfsg/debian/control
--- snap-aligner-2.0.3+dfsg/debian/control  2023-08-24 09:17:57.0 
+
+++ snap-aligner-2.0.3+dfsg/debian/control  2023-08-24 09:17:57.0 
+
@@ -15,7 +15,7 @@
 Rules-Requires-Root: no
 
 Package: snap-aligner
-Architecture: amd64 arm64 mips64el ppc64el s390x alpha kfreebsd-amd64 ppc64 
riscv64 sparc64
+Architecture: amd64 arm64 loong64 mips64el ppc64el s390x alpha kfreebsd-amd64 
ppc64 riscv64 sparc64
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Description: Scalable Nucleotide Alignment Program

Bug#1059966: thunderbird: loong64 is not present in the architecture list

[zhangdandan]

Source: thunderbird
Version: 1:115.6.0-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The thunderbird could not be compiled for loong64 in Debian Package 
Auto-Building.
Please see 
https://buildd.debian.org/status/package.php?p=thunderbird=sid


Maybe thunderbird's control file lacks loong64 support, for examples,
```
Package: thunderbird
-Architecture: amd64 arm64 i386 mips64el ppc64el s390x ppc64 riscv64
+Architecture: amd64 arm64 i386 loong64 mips64el ppc64el s390x ppc64 riscv64
```

Please pay attention to this phenomenon that I reported.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059965: nfs-ganesha: add build support for loongarch64

[zhangdandan]

Source: nfs-ganesha
Version: 4.3-8
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The nfs-ganesha source package lacks LoongArch architecture support.
We need to add build support for loongarch64 in debian/control and 
debian/rules.


Please consider the patch I have attached.
The nfs-ganesha source package was compiled successfully on my local 
environment, for examples,

```
root@localhost:/home/buildd/nfs-ganesha-4.3# ls ../
nfs-ganesha_4.3-8.debian.tar.xz
nfs-ganesha_4.3-8.dsc
nfs-ganesha_4.3-8_loong64.buildinfo
nfs-ganesha_4.3-8_loong64.changes
nfs-ganesha_4.3-8_loong64.deb
nfs-ganesha_4.3.orig.tar.gz
nfs-ganesha-add-loongarch64-support.debdiff
nfs-ganesha-ceph_4.3-8_loong64.deb
nfs-ganesha-ceph-dbgsym_4.3-8_loong64.deb
nfs-ganesha-dbgsym_4.3-8_loong64.deb
nfs-ganesha-doc_4.3-8_all.deb
nfs-ganesha-gluster_4.3-8_loong64.deb
..
```
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru nfs-ganesha-4.3/debian/control nfs-ganesha-4.3/debian/control
--- nfs-ganesha-4.3/debian/control  2023-10-30 21:32:53.0 +
+++ nfs-ganesha-4.3/debian/control  2023-10-30 21:32:53.0 +
@@ -18,15 +18,15 @@
  libcap-dev,
  libcephfs-dev,
  libdbus-1-dev,
- libglusterfs-dev (>= 9.0) [amd64 arm64 ia64 mips64el ppc64 ppc64el riscv64 
s390x sparc64],
+ libglusterfs-dev (>= 9.0) [amd64 arm64 ia64 loong64 mips64el ppc64 ppc64el 
riscv64 s390x sparc64],
  libkrb5-dev,
  liblttng-ctl-dev,
  liblttng-ust-dev,
  libnfsidmap-dev,
  libntirpc-dev (>= 4.3),
  libpython3-all-dev,
- librados-dev [amd64 arm64 mips64el ppc64el riscv64 s390x],
- librgw-dev [amd64 arm64 mips64el ppc64el riscv64 s390x],
+ librados-dev [amd64 arm64 loong64 mips64el ppc64el riscv64 s390x],
+ librgw-dev [amd64 arm64 loong64 mips64el ppc64el riscv64 s390x],
  liburcu-dev,
  libwbclient-dev,
  lttng-tools,
@@ -60,7 +60,7 @@
  This package contains the binaries
 
 Package: nfs-ganesha-ceph
-Architecture: amd64 arm64 mips64el ppc64el riscv64 s390x
+Architecture: amd64 arm64 loong64 mips64el ppc64el riscv64 s390x
 Section: libs
 Depends:
  nfs-ganesha (=${binary:Version}),
@@ -94,7 +94,7 @@
 
 Package: nfs-ganesha-gluster
 Multi-Arch: same
-Architecture: amd64 arm64 ia64 mips64el ppc64 ppc64el riscv64 s390x sparc64
+Architecture: amd64 arm64 ia64 loong64 mips64el ppc64 ppc64el riscv64 s390x 
sparc64
 Section: libs
 Depends:
  libglusterfs0 (>= 6.0),
@@ -190,7 +190,7 @@
 
 Package: nfs-ganesha-rados-grace
 Multi-Arch: foreign
-Architecture: amd64 arm64 mips64el ppc64el riscv64 s390x
+Architecture: amd64 arm64 loong64 mips64el ppc64el riscv64 s390x
 Depends:
  nfs-ganesha (=${binary:Version}),
  ${misc:Depends},
@@ -205,7 +205,7 @@
 
 Package: nfs-ganesha-rgw
 Multi-Arch: same
-Architecture: amd64 arm64 mips64el ppc64el riscv64 s390x
+Architecture: amd64 arm64 loong64 mips64el ppc64el riscv64 s390x
 Section: libs
 Depends:
  nfs-ganesha (=${binary:Version}),
diff -Nru nfs-ganesha-4.3/debian/rules nfs-ganesha-4.3/debian/rules
--- nfs-ganesha-4.3/debian/rules2023-10-30 21:32:53.0 +
+++ nfs-ganesha-4.3/debian/rules2023-10-30 21:32:53.0 +
@@ -19,7 +19,7 @@
 else
   FSALGLUSTER=-DUSE_FSAL_GLUSTER=NO
 endif
-ifneq (,$(findstring $(DEB_HOST_ARCH),"amd64 arm64 mips64el ppc64el riscv64 
s390x"))
+ifneq (,$(findstring $(DEB_HOST_ARCH),"amd64 arm64 loong64 mips64el ppc64el 
riscv64 s390x"))
   FSALCEPH=-DUSE_FSAL_CEPH=YES -DUSE_FSAL_RGW=YES
   RADOSOPT=-DUSE_RADOS_RECOV=YES -DRADOS_URLS=YES
 else

Bug#1059893: haskell-hoogle: add build support for loongarch64

[zhangdandan]

Source: haskell-hoogle
Version: 5.0.18.3+dfsg1-4
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in debian/control and 
debian/tests/control.

Please consider the patch I have attached.

I would like to remind you that the compilation dependencies of
haskell-hoogle are not yet satisfied.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff --git a/debian/control b/debian/control
index 1c7f853..b25cf9b 100644
--- a/debian/control
+++ b/debian/control
@@ -152,7 +152,7 @@ Description: Haskell API Search; documentation
  This package contains the documentation files.
 
 Package: hoogle
-Architecture: amd64 arm64 ia64 kfreebsd-amd64 mips64el ppc64 ppc64el riscv64 
s390x sparc64
+Architecture: amd64 arm64 ia64 kfreebsd-amd64 loong64 mips64el ppc64 ppc64el 
riscv64 s390x sparc64
 Section: misc
 Depends: ghc-doc,
  libjs-jquery,
diff --git a/debian/tests/control b/debian/tests/control
index 9152079..edc4491 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,9 +1,9 @@
 Tests: setlocale
 Depends: hoogle, libghc-setlocale-doc
 Restrictions: allow-stderr
-Architecture: amd64 arm64 ia64 kfreebsd-amd64 mips64el ppc64 ppc64el riscv64 
s390x sparc64
+Architecture: amd64 arm64 ia64 kfreebsd-amd64 loong64 mips64el ppc64 ppc64el 
riscv64 s390x sparc64
 
 Tests: install-remove
 Depends: hoogle, libghc-setlocale-doc
 Restrictions: needs-root allow-stderr
-Architecture: amd64 arm64 ia64 kfreebsd-amd64 mips64el ppc64 ppc64el riscv64 
s390x sparc64
+Architecture: amd64 arm64 ia64 kfreebsd-amd64 loong64 mips64el ppc64 ppc64el 
riscv64 s390x sparc64
-- 
2.43.0

Bug#1059613: gtk4: add build support for loongarch64

[zhangdandan]

Source: gtk4
Version: 4.12.4+ds-3
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the gtk4 failed for loong64 in the Debian Package 
Auto-Building environment. The error messages is as follows,

```
Ok: 1467
Expected Fail:  0
Fail:   33
Unexpected Pass:    0
Skipped:    15
Timeout:    0
+ debian/log-reftests.py
```
The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=gtk4=4.12.4%2Bds-3=loong64


Please consider the patch I have attached.
If you have any questions, you can contact me at any time.
The gtk4 source package was compiled successfully on my local 
environment and the test cases passed.

```
..
1515/1515 gtk:reftest / reftest window-height-for-width.ui 
OK    3.62s   1 subtests passed


Ok: 1500
Expected Fail:  0
Fail:   0
Unexpected Pass:    0
Skipped:    15
Timeout:    0

Full log written to 
/home/buildd/gtk4-4.12.4+ds/debian/build/deb/meson-logs/testlog-wayland.txt

..
dpkg-deb: building package 'libgtk-4-1-dbgsym' in 
'../libgtk-4-1-dbgsym_4.12.4+ds-3_loong64.deb'.
dpkg-deb: building package 'libgtk-4-1' in 
'../libgtk-4-1_4.12.4+ds-3_loong64.deb'.
dpkg-deb: building package 'gtk-4-examples-dbgsym' in 
'../gtk-4-examples-dbgsym_4.12.4+ds-3_loong64.deb'.

..
dpkg-deb: building package 'gir1.2-gtk-4.0' in 
'../gir1.2-gtk-4.0_4.12.4+ds-3_loong64.deb'.
dpkg-deb: building package 'libgtk-4-media-gstreamer-dbgsym' in 
'../libgtk-4-media-gstreamer-dbgsym_4.12.4+ds-3_loong64.deb'.
dpkg-deb: building package 'libgtk-4-1-udeb' in 
'debian/.debhelper/scratch-space/build-libgtk-4-1-udeb/libgtk-4-1-udeb_4.12.4+ds-3_loong64.deb'.
    Renaming libgtk-4-1-udeb_4.12.4+ds-3_loong64.deb to 
libgtk-4-1-udeb_4.12.4+ds-3_loong64.udeb

 dpkg-genbuildinfo -O../gtk4_4.12.4+ds-3_loong64.buildinfo
 dpkg-genchanges -O../gtk4_4.12.4+ds-3_loong64.changes
dpkg-genchanges: info: not including original source code in upload
 dpkg-source --after-build .
dpkg-buildpackage: info: binary and diff upload (original source NOT 
included)

```

thanks,
Dandan Zhang

diff -Nru gtk4-4.12.4+ds/debian/control gtk4-4.12.4+ds/debian/control
--- gtk4-4.12.4+ds/debian/control   2023-12-09 01:33:26.0 +
+++ gtk4-4.12.4+ds/debian/control   2023-12-09 01:33:26.0 +
@@ -46,8 +46,8 @@
libpango1.0-dev (>= 1.50.0),
libpng-dev,
libpolkit-gobject-1-dev [linux-any],
-   librsvg2-common [amd64 arm64 armel armhf i386 mips64el mipsel 
ppc64el s390x powerpc ppc64 riscv64 sparc64 x32] ,
-   librsvg2-dev (>= 2.52.0) [amd64 arm64 armel armhf i386 mips64el 
mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32],
+   librsvg2-common [amd64 arm64 armel armhf i386 loong64 mips64el 
mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32] ,
+   librsvg2-dev (>= 2.52.0) [amd64 arm64 armel armhf i386 loong64 
mips64el mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32],
libswresample-dev [amd64 arm64 armel armhf i386 mips64el mipsel 
ppc64el s390x],
libswscale-dev [amd64 arm64 armel armhf i386 mips64el mipsel 
ppc64el s390x],
libsysprof-capture-4-dev (>= 3.40.1) [linux-any],
@@ -266,7 +266,7 @@
  ${shlibs:Depends},
  libgtk-4-1 (= ${binary:Version})
 Recommends: fonts-cantarell,
-librsvg2-common (>= 2.52.0) [amd64 arm64 armel armhf i386 mips64el 
mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32],
+librsvg2-common (>= 2.52.0) [amd64 arm64 armel armhf i386 loong64 
mips64el mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32],
 Description: example files for GTK 4
  GTK is a multi-platform toolkit for creating graphical user
  interfaces. Offering a complete set of widgets, GTK is suitable
@@ -281,7 +281,7 @@
 Section: x11
 Architecture: any
 Depends: iso-codes,
- librsvg2-common (>= 2.52.0) [amd64 arm64 armel armhf i386 mips64el 
mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32],
+ librsvg2-common (>= 2.52.0) [amd64 arm64 armel armhf i386 loong64 
mips64el mipsel ppc64el s390x powerpc ppc64 riscv64 sparc64 x32],
  ${misc:Depends},
  ${shlibs:Depends},
  libgtk-4-1 (= ${binary:Version}),
diff -Nru gtk4-4.12.4+ds/debian/rules gtk4-4.12.4+ds/debian/rules
--- gtk4-4.12.4+ds/debian/rules 2023-12-09 01:33:26.0 +
+++ gtk4-4.12.4+ds/debian/rules 2023-12-09 01:33:26.0 +
@@ -196,7 +196,7 @@
 test_timeout_multiplier = 10
 endif
 
-ifneq ($(filter m68k riscv64 sh4,$(DEB_HOST_ARCH_CPU)),)
+ifneq ($(filter loong64 m68k riscv64 sh4,$(DEB_HOST_ARCH_CPU)),)
 $(info Architecture with qemu buildds detected, increasing test timeout a lot)
 test_timeout_multiplier = 20
 endif

Bug#1059608: freebsd-glue: Build dependency(gcc-9) is not satisfied in multiple architectures

[zhangdandan]

Source: freebsd-glue
Version: 0.2.22+nmu1
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the freebsd-glue with a dependency on gcc-9, the build 
dependency is not satisfied in several architectures such as riscv64, 
loong64 and so on. The full status can be found at 
https://buildd.debian.org/status/package.php?p=freebsd-glue=sid.
With Debian package updates, compilation dependencies of freebsd-glue 
should not be written as fixed gcc-9 (fixed gcc version).


The current version of gcc for debian ports is 13.2.0.
I have changed the d/rule and d/control with current gcc version(The 
patch in my attachment is used locally and is for reference only). The 
freebsd-glue source package was compiled successfully on my local 
environment.

Please pay attention to the phenomenon of my feedback above.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru freebsd-glue-0.2.22+nmu1/debian/control 
freebsd-glue-0.2.22+nmu1/debian/control
--- freebsd-glue-0.2.22+nmu1/debian/control 2023-08-06 23:18:20.0 
+
+++ freebsd-glue-0.2.22+nmu1/debian/control 2023-08-06 23:20:16.0 
+
@@ -7,7 +7,7 @@
  Steven Chamberlain ,
 Build-Depends:
  debhelper (>= 8.0),
- gcc-9,
+ gcc-13,
  kfreebsd-kernel-headers (>= 10.0~3) [kfreebsd-any],
  freebsd-mk,
  bmake,
diff -Nru freebsd-glue-0.2.22+nmu1/debian/rules 
freebsd-glue-0.2.22+nmu1/debian/rules
--- freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-06 23:20:16.0 
+
+++ freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-06 23:20:16.0 
+
@@ -6,7 +6,7 @@
 # Determine host architecture compiler
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 ifeq ($(origin CC),default)
-CC := $(DEB_HOST_GNU_TYPE)-gcc-9
+CC := $(DEB_HOST_GNU_TYPE)-gcc-13
 endif
 
 # Determine build architecture compiler

Bug#1059606: fwupd: add build support for loongarch64

[zhangdandan]

Source: fwupd
Version: 1.9.10-1
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the fwupd failed for loong64 in the my local loong64 environment.
Referring to other architectures, maybe we need to add build support for 
loongarch64 (drop valgrind build dependency for loong64).

```
debian/control
- valgrind [!ia64 !riscv64 !x32 !mips !sparc64 !sh4 !ppc64 !powerpcspe 
!hppa !alpha !mips64el !armhf !armel !mipsel !m68k],
+ valgrind [!ia64 !riscv64 !x32 !mips !sparc64 !sh4 !ppc64 !powerpcspe 
!hppa !alpha !mips64el !armhf !armel !mipsel !m68k !loong64],

```

With the above change in d/control, the fwupd source package was 
compiled successfully on my local loong64 rootfs environment.
Please review whether the above modifications are correct. Your opinions 
are welcome.


thanks,
Dandan Zhang

Bug#1059601: ectrans: add build support for loongarch64

[zhangdandan]

Source: ectrans
Version: 1.1.0-4
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control, for example,
```
Package: libectrans-0
Section: libs
-Architecture: amd64 arm64 ppc64 mips64el ppc64el s390x riscv64 sparc64  
kfreebsd-amd64 ia64
+Architecture: amd64 arm64 ppc64 loong64 mips64el ppc64el s390x riscv64 
sparc64  kfreebsd-amd64 ia64


Package: ectrans-utils
-Architecture: amd64 arm64 ppc64 mips64el ppc64el s390x riscv64 sparc64  
kfreebsd-amd64 ia64
+Architecture: amd64 arm64 ppc64 loong64 mips64el ppc64el s390x riscv64 
sparc64  kfreebsd-amd64 ia64


Package: libectrans-dev
Section: libdevel
-Architecture: amd64 arm64 ppc64 mips64el ppc64el s390x riscv64 sparc64  
kfreebsd-amd64 ia64
+Architecture: amd64 arm64 ppc64 loong64 mips64el ppc64el s390x riscv64 
sparc64  kfreebsd-amd64 ia64

```

Please consider the above support for loongarch64.
I would like to remind you that the compilation dependencies of ectrans 
are not yet satisfied.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059600: fiat-ecmwf: add build support for loongarch64

[zhangdandan]

Source: fiat-ecmwf
Version: 1.2.0-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control, for example,
```
Package: libfiat-0
Section: libs
-Architecture: amd64 arm64 ppc64 mips64el ppc64el s390x riscv64 sparc64  
kfreebsd-amd64 ia64
+Architecture: amd64 arm64 ppc64 loong64 mips64el ppc64el s390x riscv64 
sparc64  kfreebsd-amd64 ia64


Package: fiat-utils
-Architecture: amd64 arm64 ppc64 mips64el ppc64el s390x riscv64 sparc64  
kfreebsd-amd64 ia64
+Architecture: amd64 arm64 ppc64 loong64 mips64el ppc64el s390x riscv64 
sparc64  kfreebsd-amd64 ia64


Package: libfiat-dev
Section: libdevel
-Architecture: amd64 arm64 ppc64 mips64el ppc64el s390x riscv64 sparc64  
kfreebsd-amd64 ia64
+Architecture: amd64 arm64 ppc64 loong64 mips64el ppc64el s390x riscv64 
sparc64  kfreebsd-amd64 ia64

```

Please consider the above support for loongarch64.
I would like to remind you that the compilation dependencies of 
fiat-ecmwf are not yet satisfied.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059557: python-cogent: add build support for loongarch64

[zhangdandan]

Source: python-cogent
Version: 2023.2.12a1+dfsg-4
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control, for example,
```
Package: python3-cogent3
-Architecture: any-amd64 arm64 mips64el ppc64el s390x ia64 ppc64 riscv64 
sparc64 alpha
+Architecture: any-amd64 arm64 mips64el ppc64el s390x ia64 loong64 ppc64 
riscv64 sparc64 alpha

```

Please consider the above support for loongarch64.
I would like to remind you that the compilation dependencies of 
python-cogent are not yet satisfied.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059556: gauche: add loongarch64 support

[zhangdandan]

Source: gauche
Version: 0.9.10-3
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the gauche failed for loong64 in the Debian Package 
Auto-Building environment. The error message is as follows,

```
In file included from ./include/private/gc_priv.h:123,
 from ./include/private/dbg_mlc.h:28,
 from extra/../backgraph.c:15,
 from extra/gc.c:40:
./include/private/gcconfig.h:709:5: error: #error The collector has not 
been ported to this machine/OS combination
  709 | #   error The collector has not been ported to this machine/OS 
combination

  | ^
./include/private/gcconfig.h:3068:3: error: #error Undefined ALIGNMENT
 3068 | # error Undefined ALIGNMENT
  |   ^
..
```
The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=gauche=0.9.10-3=loong64


I have added the loongarch64 support in gauche source code.
The gauche source package was compiled successfully on my local 
environment and the test cases passed.

```
make[2]: Entering directory “/home/buildd/gauche-0.9.10/src”
Testing math.* modules ... passed.
Testing data.* modules ... passed.
Testing util.* modules extra ... passed.
Testing optimizer ... passed.
Testing control ... passed.
Testing miscellaneous compiler features ... passed.
Testing debug features ... passed.
Testing utility scripts ... passed.
Testing interactive ... passed.
Testing r7rs-tests ... passed.
Testing r7rs-aux ... passed.
make[2]: Leaving directory “/home/buildd/gauche-0.9.10/src”
Total: 30709 tests, 30709 passed, 0 failed, 0 aborted.
```
Please consider the patch I have attached.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Description: Add loongarch64 support 
Last-Update: 2023-10-28

--- gauche-0.9.10.orig/gc/include/private/gcconfig.h
+++ gauche-0.9.10/gc/include/private/gcconfig.h
@@ -675,6 +675,11 @@ EXTERN_C_BEGIN
 #   define mach_type_known
 # endif
 
+# if defined(__loongarch__) && defined(LINUX)
+#define LOONGARCH
+#define mach_type_known
+# endif
+
 # if defined(SN_TARGET_PSP2)
 #   define mach_type_known
 # endif
@@ -1742,6 +1747,21 @@ EXTERN_C_BEGIN
 #   define STACKBOTTOM ((ptr_t)0xf000) /* for Encore */
 # endif
 
+# ifdef LOONGARCH
+#   define MACH_TYPE "LoongArch"
+#   define CPP_WORDSZ __loongarch_grlen
+#   define ALIGNMENT (__loongarch_grlen/8)
+#   ifdef LINUX
+# define OS_TYPE "LINUX"
+# pragma weak __data_start
+  extern int __data_start[];
+# define DATASTART ((ptr_t)(__data_start))
+# define LINUX_STACKBOTTOM
+# define COUNT_UNMAPPED_REGIONS
+# define DYNAMIC_LOADING
+#   endif
+# endif /* LOONGARCH */
+
 # ifdef MIPS
 #   define MACH_TYPE "MIPS"
 #   ifdef LINUX

Bug#1059554: ares: FTBFS: "unknown arch, please specify manually"

[zhangdandan]

Source: ares
Version: 132-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the ares failed for loong64 in the Debian Package 
Auto-Building environment. The error messages is as follows,

```
make[1]: Entering directory '/<>/desktop-ui'
../nall/GNUmakefile:123: *** unknown arch, please specify manually..  Stop.
make[1]: Leaving directory '/<>/desktop-ui'
dh_auto_clean: error: cd desktop-ui && make -j16 distclean returned exit 
code 2

```
The full build log can be found at 
https://buildd.debian.org/status/logs.php?pkg=ares=132-1=loong64.


I have added the loongarch64 support in ares source code.
The ares source package was compiled successfully on my local environment.
Please consider the patch I have attached.
I have also submitted the pull-request to ares upstream, please see 
https://github.com/ares-emulator/ares/pull/1356.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Description: Add loongarch64 support 
Last-Update: 2023-12-28

--- ares-132.orig/nall/GNUmakefile
+++ ares-132/nall/GNUmakefile
@@ -90,6 +90,8 @@ ifneq ($(filter amd64-% x86_64-%,$(machi
   machine := amd64
 else ifneq ($(filter arm64-% aarch64-%,$(machine_str)),)
   machine := arm64
+else ifneq ($(filter loong64-% loongarch64-%,$(machine_str)),)
+  machine := loong64
 else ifneq ($(filter powerpc64-% powerpc64le-%,$(machine_str)),)
   machine := ppc64
 endif
--- ares-132.orig/nall/intrinsics.hpp
+++ ares-132/nall/intrinsics.hpp
@@ -183,6 +183,7 @@ namespace nall {
 static constexpr bool amd64 = 0;
 static constexpr bool arm64 = 0;
 static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 0;
 static constexpr bool ppc64 = 0;
 static constexpr bool ppc32 = 0;
   };
@@ -196,6 +197,7 @@ namespace nall {
 static constexpr bool amd64 = 1;
 static constexpr bool arm64 = 0;
 static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 0;
 static constexpr bool ppc64 = 0;
 static constexpr bool ppc32 = 0;
   };
@@ -207,6 +209,7 @@ namespace nall {
 static constexpr bool amd64 = 0;
 static constexpr bool arm64 = 1;
 static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 0;
 static constexpr bool ppc64 = 0;
 static constexpr bool ppc32 = 0;
   };
@@ -217,6 +220,18 @@ namespace nall {
 static constexpr bool amd64 = 0;
 static constexpr bool arm64 = 0;
 static constexpr bool arm32 = 1;
+static constexpr bool loong64 = 0;
+static constexpr bool ppc64 = 0;
+static constexpr bool ppc32 = 0;
+  };
+#elif defined(__loongarch64)
+  #define ARCHITECTURE_LOONG64
+  struct Architecture {
+static constexpr bool x86   = 0;
+static constexpr bool amd64 = 0;
+static constexpr bool arm64 = 0;
+static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 1;
 static constexpr bool ppc64 = 0;
 static constexpr bool ppc32 = 0;
   };
@@ -227,6 +242,7 @@ namespace nall {
 static constexpr bool amd64 = 0;
 static constexpr bool arm64 = 0;
 static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 0;
 static constexpr bool ppc64 = 1;
 static constexpr bool ppc32 = 0;
   };
@@ -237,6 +253,7 @@ namespace nall {
 static constexpr bool amd64 = 0;
 static constexpr bool arm64 = 0;
 static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 0;
 static constexpr bool ppc64 = 0;
 static constexpr bool ppc32 = 1;
   };
@@ -248,6 +265,7 @@ namespace nall {
 static constexpr bool amd64 = 0;
 static constexpr bool arm64 = 0;
 static constexpr bool arm32 = 0;
+static constexpr bool loong64 = 0;
 static constexpr bool ppc64 = 0;
 static constexpr bool ppc32 = 0;
   };
@@ -259,7 +277,7 @@ namespace nall {
 
 /* Endian detection */
 
-#if (defined(__BYTE_ORDER) && defined(__LITTLE_ENDIAN) && __BYTE_ORDER == __LITTLE_ENDIAN) || defined(__LITTLE_ENDIAN__) || defined(__i386__) || defined(__amd64__) || defined(_M_IX86) || defined(_M_AMD64)
+#if (defined(__BYTE_ORDER) && defined(__LITTLE_ENDIAN) && __BYTE_ORDER == __LITTLE_ENDIAN) || defined(__LITTLE_ENDIAN__) || defined(__i386__) || defined(__amd64__) || defined(_M_IX86) || defined(_M_AMD64) || defined(__loongarch64)
   #define ENDIAN_LITTLE
   struct Endian {
 static constexpr bool Little = 1;

Bug#1059517: gdcm: add build support for loongarch64

[zhangdandan]

Source: gdcm
Version: 3.0.22-2
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the gdcm failed for loong64 in the my local loong64 environment.
We need to add build support for loongarch64 in d/control.
Please consider the patch I have attached.

I would like to remind you that compilation dependency of gdcm is 
libvtk9-dev (vtk9 lacks loongarch64 support), I have submitted a bug 
request to vtk9 to support loongarch64, please see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054471.
The gdcm source package was compiled successfully on my local loong64 
rootfs environment, for examples,

```
..
   dh_md5sums -O--buildsystem=cmake\+ninja
   dh_builddeb -O--buildsystem=cmake\+ninja
dpkg-deb: 正在 '../libgdcm3.0_3.0.22-2_loong64.deb' 中构建软件包 
'libgdcm3.0'。
dpkg-deb: 正在 '../libgdcm-tools_3.0.22-2_loong64.deb' 中构建软件包 
'libgdcm-tools'。
dpkg-deb: 正在 '../libgdcm3.0-dbgsym_3.0.22-2_loong64.deb' 中构建软件包 
'libgdcm3.0-dbgsym'。

..
dpkg-deb: 正在 '../python3-vtkgdcm_3.0.22-2_loong64.deb' 中构建软件包 
'python3-vtkgdcm'。
dpkg-deb: 正在 '../libgdcm-java-dbgsym_3.0.22-2_loong64.deb' 中构建软件包 
'libgdcm-java-dbgsym'。

 dpkg-genbuildinfo -O../gdcm_3.0.22-2_loong64.buildinfo
 dpkg-genchanges -O../gdcm_3.0.22-2_loong64.changes
..
```

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru gdcm-3.0.22/debian/control gdcm-3.0.22/debian/control
--- gdcm-3.0.22/debian/control  2023-10-30 14:38:48.0 +
+++ gdcm-3.0.22/debian/control  2023-12-07 09:37:28.0 +
@@ -185,7 +185,7 @@
  This is the documentation for gdcm and vtkgdcm
 
 Package: libgdcm-java
-Architecture: alpha amd64 arm64 armel armhf i386 ia64 m68k mips64el mipsel 
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32
+Architecture: alpha amd64 arm64 armel armhf i386 ia64 loong64 m68k mips64el 
mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32
 Section: java
 Depends: ${java:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Suggests: java-virtual-machine
diff -Nru gdcm-3.0.22/debian/control.in gdcm-3.0.22/debian/control.in
--- gdcm-3.0.22/debian/control.in   2023-10-30 14:38:48.0 +
+++ gdcm-3.0.22/debian/control.in   2023-12-07 09:37:28.0 +
@@ -185,7 +185,7 @@
  This is the documentation for gdcm and vtkgdcm
 
 Package: libgdcm-java
-Architecture: alpha amd64 arm64 armel armhf i386 ia64 m68k mips64el mipsel 
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32
+Architecture: alpha amd64 arm64 armel armhf i386 ia64 loong64 m68k mips64el 
mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32
 Section: java
 Depends: ${java:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Suggests: java-virtual-machine

Bug#1059510: bowtie2: add build support for loongarch64

[zhangdandan]

Source: bowtie2
Version: 2.5.1-1
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the bowtie2 failed for loong64 in the my local loong64 
environment.

We need to add build support for loongarch64 in d/control.

The bowtie2 source package was compiled successfully on my local loong64 
rootfs environment.

Please consider the patch I have attached.
Your opinions are welcome.

thanks,
Dandan Zhang

diff -Nru bowtie2-2.5.1/debian/control bowtie2-2.5.1/debian/control
--- bowtie2-2.5.1/debian/control2023-09-12 11:15:56.0 +
+++ bowtie2-2.5.1/debian/control2023-09-12 11:16:13.0 +
@@ -22,7 +22,7 @@
 Rules-Requires-Root: no
 
 Package: bowtie2
-Architecture: any-amd64 arm64 mips64el ppc64el ia64 m68k ppc64 riscv64 sh4 
sparc64
+Architecture: any-amd64 arm64 mips64el ppc64el ia64 loong64 m68k ppc64 riscv64 
sh4 sparc64
 Depends: python3,
  ${misc:Depends},
  ${shlibs:Depends},

Bug#1059504: sagemath: add loongarch64 support

[zhangdandan]

Source: sagemath
Version: 9.5-6
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in sagemath source code, 
for example,

```
./debian/control.in:Architecture: amd64 arm64 i386 ppc64el s390x alpha 
hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 loong64 m68k powerpc 
ppc64 riscv64 sh4 sparc64 x32
./sage/m4/ax_boost_base.m4: 
[ppc64|powerpc64|s390x|sparc64|aarch64|ppc64le|powerpc64le|riscv64|loongarch64],[libsubdirs="lib64 
lib lib64"],

```

Please consider the above support for loongarch64.
I would like to remind you that the compilation dependencies of loong64 
sagemath are not yet satisfied.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059439: jsonnet: add loongarch64 support

[zhangdandan]

Source: jsonnet
Version: 0.20.0+ds-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the jsonnet failed on my local loong64 rootfs environment.
We need to add build support for loong64 in debian/control.
At the same time, we also need to add the loongarch64 support in jsonnet 
source code.


Please consider the patch I have attached.
The jsonnet source package was compiled successfully on my local env and 
the tests passed.

```
8: /home/jsonnet-0.20.0+ds/test_suite/run_tests.sh: All 157 test scripts 
pass.

8/8 Test #8: regression_test ..   Passed   34.02 sec
100% tests passed, 0 tests failed out of 8
Total Test time (real) =  34.04 sec
```

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru jsonnet-0.20.0+ds/debian/control jsonnet-0.20.0+ds/debian/control
--- jsonnet-0.20.0+ds/debian/control2023-07-30 13:33:59.0 +
+++ jsonnet-0.20.0+ds/debian/control2023-07-30 13:37:07.0 +
@@ -11,7 +11,7 @@
 Rules-Requires-Root: no
 
 Package: jsonnet
-Architecture: amd64 arm64 armhf i386 armel ppc64el riscv64
+Architecture: amd64 arm64 armhf i386 armel loong64 ppc64el riscv64
 Depends: ${misc:Depends}, ${shlibs:Depends},
 Description: data templating language
  A data templating language for app and tool developers
@@ -37,7 +37,7 @@
 
 Package: libjsonnet0
 Section: libs
-Architecture: amd64 arm64 armhf i386 armel ppc64el riscv64
+Architecture: amd64 arm64 armhf i386 armel loong64 ppc64el riscv64
 Depends: ${misc:Depends}, ${shlibs:Depends},
 Description: data templating language (lib)
  A data templating language for app and tool developers
@@ -63,7 +63,7 @@
 
 Package: libjsonnet-dev
 Section: libdevel
-Architecture: amd64 arm64 armhf i386 armel ppc64el riscv64
+Architecture: amd64 arm64 armhf i386 armel loong64 ppc64el riscv64
 Depends: ${misc:Depends}, libjsonnet0 (= ${binary:Version})
 Description: data templating language (devel)
  A data templating language for app and tool developers
@@ -89,7 +89,7 @@
 
 Package: python3-jsonnet
 Section: python
-Architecture: amd64 arm64 armhf i386 armel ppc64el riscv64
+Architecture: amd64 arm64 armhf i386 armel loong64 ppc64el riscv64
 Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends},
 Description: data templating language (Python)
  A data templating language for app and tool developers
diff -Nru jsonnet-0.20.0+ds/debian/patches/add-loongarch64-support.patch 
jsonnet-0.20.0+ds/debian/patches/add-loongarch64-support.patch
--- jsonnet-0.20.0+ds/debian/patches/add-loongarch64-support.patch  
1970-01-01 00:00:00.0 +
+++ jsonnet-0.20.0+ds/debian/patches/add-loongarch64-support.patch  
2023-07-30 13:37:07.0 +
@@ -0,0 +1,28 @@
+Description: add loongarch64 support 
+Last-Update: 2023-12-25
+
+--- 
jsonnet-0.20.0+ds.orig/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/cpu.hpp
 jsonnet-0.20.0+ds/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/cpu.hpp
+@@ -91,6 +91,11 @@
+ #   define C4_WORDSIZE 8
+ #   define C4_BYTE_ORDER _C4EL
+ 
++#elif defined(__loongarch64)
++#   define C4_CPU_LOONGARCH64
++#   define C4_WORDSIZE 8
++#   define C4_BYTE_ORDER _C4EL
++
+ #elif defined(SWIG)
+ #else
+ #   error "unknown CPU architecture"
+--- 
jsonnet-0.20.0+ds.orig/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/ext/fast_float/include/fast_float/float_common.h
 
jsonnet-0.20.0+ds/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/ext/fast_float/include/fast_float/float_common.h
+@@ -8,7 +8,7 @@
+ #if (defined(__x86_64) || defined(__x86_64__) || defined(_M_X64)   \
+|| defined(__amd64) || defined(__aarch64__) || defined(_M_ARM64) \
+|| defined(__MINGW64__)  \
+-   || defined(__s390x__)\
++   || defined(__s390x__) || defined(__loongarch64)  \
+|| (defined(__ppc64__) || defined(__PPC64__) || defined(__ppc64le__) \
+|| defined(__PPC64LE__) || defined(__riscv) && __riscv_xlen == 64))
+ #define FASTFLOAT_64BIT
diff -Nru jsonnet-0.20.0+ds/debian/patches/series 
jsonnet-0.20.0+ds/debian/patches/series
--- jsonnet-0.20.0+ds/debian/patches/series 2022-07-31 13:53:10.0 
+
+++ jsonnet-0.20.0+ds/debian/patches/series 2023-07-30 13:37:07.0 
+
@@ -1,3 +1,4 @@
 0001-fix-FTBFS-on-several-release-architectures.patch
 0002-fix-compile-error-in-armel.patch
 0003-add-support-riscv64.patch
+add-loongarch64-support.patch

Bug#1059425: cpu-checker: enable loongarch64 build

[zhangdandan]

Source: cpu-checker
Version: 0.7-1.3
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the cpu-checker failed on my local loong64 rootfs environment.
We need to add build support for loong64 in debian/control.
At the same time, we also need to add the loongarch64 support in kvm-ok 
for the LoongArch architecture.


Please consider the patch I have attached.
Referring to other architectures, I have submitted a bug to the Ubuntu 
launchpad, plesase see https://bugs.launchpad.net/cpu-checker/+bug/2047347

Your opinions are welcome.

thanks,
Dandan Zhang

diff -Nru cpu-checker-0.7/debian/control cpu-checker-0.7/debian/control
--- cpu-checker-0.7/debian/control  2021-08-02 13:30:02.0 +
+++ cpu-checker-0.7/debian/control  2021-09-14 06:45:39.0 +
@@ -9,7 +9,7 @@
 Vcs-Bzr: lp:~cpu-checker-dev/cpu-checker/trunk
 
 Package: cpu-checker
-Architecture: amd64 arm64 armhf i386 ppc64el powerpc riscv64 s390x
+Architecture: amd64 arm64 armhf i386 loong64 ppc64el powerpc riscv64 s390x
 Depends: msr-tools [amd64 i386], ${shlibs:Depends}, ${misc:Depends}
 Conflicts: qemu-kvm (<< 0.12.3-0ubuntu13)
 Replaces: qemu-kvm (<< 0.12.3-0ubuntu13)
diff -Nru 
cpu-checker-0.7/debian/patches/cpu-checker-add-loongarch64-support.patch 
cpu-checker-0.7/debian/patches/cpu-checker-add-loongarch64-support.patch
--- cpu-checker-0.7/debian/patches/cpu-checker-add-loongarch64-support.patch
1970-01-01 00:00:00.0 +
+++ cpu-checker-0.7/debian/patches/cpu-checker-add-loongarch64-support.patch
2021-09-14 06:45:39.0 +
@@ -0,0 +1,26 @@
+Description: Add loongarch64 support 
+Last-Update: 2023-12-25
+
+--- cpu-checker-0.7.orig/kvm-ok
 cpu-checker-0.7/kvm-ok
+@@ -63,6 +63,10 @@ case "$(uname -m)" in
+   virt="RISCV"
+   kvm_mod="kvm"
+   ;;
++loongarch64)
++  virt="LOONGARCH"
++  kvm_mod="kvm"
++  ;;
+ *)
+   virt=$(egrep -m1 -w '^flags[[:blank:]]*:' /proc/cpuinfo | egrep -wo 
'(vmx|svm)') || true
+   [ "$virt" = "vmx" ] && kvm_mod="kvm_intel"
+@@ -122,6 +126,9 @@ elif [ "$virt" = "ARM" ]; then
+ elif [ "$virt" = "RISCV" ]; then
+ # Should also test that we booted in HS mode, if detectable
+ :
++elif [ "$virt" = "LOONGARCH" ]; then
++# Should also test that we booted in LVZ mode, if detectable
++:
+ elif [ "$virt" = "generic" ]; then
+ :
+ else
diff -Nru cpu-checker-0.7/debian/patches/series 
cpu-checker-0.7/debian/patches/series
--- cpu-checker-0.7/debian/patches/series   2021-08-02 13:30:02.0 
+
+++ cpu-checker-0.7/debian/patches/series   2021-09-14 06:45:39.0 
+
@@ -3,3 +3,4 @@
 powerpc-dummy.patch
 cpu-checker-s390x.patch
 riscv64-dummy.patch
+cpu-checker-add-loongarch64-support.patch

Bug#1059276: python-demgengeo: FTBFS on loongarch64 - error: cannot find the flags to link with Boost system

[zhangdandan]

Source: python-demgengeo
Version: 1.4-4.1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the python-demgengeo failed for loong64 in the Debian Package 
Auto-Building environment.

The error messages are as follows,
```
checking for the Boost system library... /usr/lib/libboost_system.so ...
no...
/usr/lib64/libboost_system.so ...
no...
/usr/libexec/libboost_system.so ...
no...
/usr/local/lib/libboost_system.so ...
no...
...
/usr/lib64/libboost_system-d.so ...
no...
/usr/libexec/libboost_system-d.so ...
no...
/usr/local/lib/libboost_system-d.so ...
no...
/lib/libboost_system-d.so ...
no...
/lib64/libboost_system-d.so ...
no...
/libboost_system-d.so ...
no...
/usr/lib/libboost_system-mt-d.so ...
no...
/usr/lib64/libboost_system-mt-d.so ...
no...
/usr/libexec/libboost_system-mt-d.so ...
no...
/usr/local/lib/libboost_system-mt-d.so ...
no...
..
/lib64/libboost_system--mt-d-1_83.so ...
no...
/libboost_system--mt-d-1_83.so ...
no...
no
configure: error: cannot find the flags to link with Boost system
```

The full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=python-demgengeo=1.4-4.1=loong64
Referring to other architectures, the relevant bug is 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829143


Please add loongarch64 directories in m4/boost.m4.

thanks,
Dandan Zhang

Bug#1059268: rust-coreutils: add loongarch64 support

[zhangdandan]

Source: rust-coreutils
Version: 0.0.23-2
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the rust-coreutils failed for loong64 in the my local loong64 
environment.

The error messages are as follows,
```
..
Compiling uu_stdbuf v0.0.23 
(/home/build/rust-coreutils-0.0.23/src/uu/stdbuf)

error[E0308]: mismatched types
   --> src/uucore/src/lib/features/fs.rs:124:16
    |
111 | pub fn number_of_links() -> u64 {
    |  --- expected `u64` because 
of return type

...
124 | return self.0.st_nlink;
    |    ^^^ expected `u64`, found `u32`
    |
help: you can convert a `u32` to a `u64`
    |
124 | return self.0.st_nlink.into();
    |   +++

For more information about this error, try `rustc --explain E0308`.
error: could not compile `uucore` due to previous error
```

I have added loongarch64 support for rust-coreutils.
The rust-coreutils source package was compiled successfully on my local 
loong64 rootfs environment.

Please consider the patch I have attached.
Your opinions are welcome.

thanks,
Dandan Zhang

Description: Add loongarch64 support 
Last-Update: 2023-12-22

--- rust-coreutils-0.0.23.orig/docs/compiles_table.py
+++ rust-coreutils-0.0.23/docs/compiles_table.py
@@ -18,6 +18,7 @@ TARGETS = [
 # Linux - GNU
 "aarch64-unknown-linux-gnu",
 "i686-unknown-linux-gnu",
+"loongarch64-unknown-linux-gnu",
 "powerpc64-unknown-linux-gnu",
 "riscv64gc-unknown-linux-gnu",
 "x86_64-unknown-linux-gnu",
--- rust-coreutils-0.0.23.orig/src/uucore/src/lib/features/fs.rs
+++ rust-coreutils-0.0.23/src/uucore/src/lib/features/fs.rs
@@ -119,6 +119,7 @@ impl FileInformation {
 not(target_os = "solaris"),
 not(target_arch = "aarch64"),
 not(target_arch = "riscv64"),
+not(target_arch = "loongarch64"),
 target_pointer_width = "64"
 ))]
 return self.0.st_nlink;
@@ -133,6 +134,7 @@ impl FileInformation {
 target_os = "solaris",
 target_arch = "aarch64",
 target_arch = "riscv64",
+target_arch = "loongarch64",
 not(target_pointer_width = "64")
 )
 ))]

Bug#1059246: rust-laurel: add loongarch64 support

[zhangdandan]

Source: rust-laurel
Version: 0.5.3-1.1
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

I have submitted the LoongArch architecture support in rust-laurel 
upstream [1], please see the pull-request link [2].
Please add support for loongarch64 (64-bit LoongArch) in rust-laurel 
source package.


Please consider the patch I have attached.
Your opinions are welcome.

[1]:https://github.com/threathunters-io/laurel
[2]:https://github.com/threathunters-io/laurel/pull/186

thanks,
Dandan Zhang

Description: Add loongarch64 support 
Last-Update: 2023-12-21

--- rust-laurel-0.5.3.orig/src/constants.rs
+++ rust-laurel-0.5.3/src/constants.rs
@@ -59,6 +59,7 @@ const ARCHS: &[(, u32)] = &[
 ("hexagon", 0x00a4),
 ("i386", 0x4003),
 ("ia64", 0xc032),
+("loongarch64", 0xc102),
 ("m32r", 0x0058),
 ("m68k", 0x0004),
 ("microblaze", 0x00bd),

Bug#1059219: gudhi: add build support for loongarch64

[zhangdandan]

Source: gudhi
Version: 3.7.1+dfsg-2
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control.
Please consider the patch I have attached.

The gudhi source package was compiled successfully on my local loong64 
rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru gudhi-3.7.1+dfsg/debian/control gudhi-3.7.1+dfsg/debian/control
--- gudhi-3.7.1+dfsg/debian/control 2023-11-26 12:08:34.0 +
+++ gudhi-3.7.1+dfsg/debian/control 2023-11-26 12:08:34.0 +
@@ -97,7 +97,7 @@
 
 Package: python3-gudhi
 Section: python
-Architecture: amd64 arm64 i386 mips64el ppc64el s390x ia64 ppc64 riscv64 
sparc64 x32
+Architecture: amd64 arm64 i386 loong64 mips64el ppc64el s390x ia64 ppc64 
riscv64 sparc64 x32
 Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
 Recommends: python3-eagerpy,
 python3-matplotlib,
@@ -115,7 +115,7 @@
 
 Package: gudhui
 Section: math
-Architecture: amd64 arm64 i386 mips64el ppc64el s390x ia64 ppc64 riscv64 
sparc64 x32
+Architecture: amd64 arm64 i386 loong64 mips64el ppc64el s390x ia64 ppc64 
riscv64 sparc64 x32
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: GUI for some of the functionality of the GUDHI library
  The GUDHI library is a generic open source C++ library for
@@ -129,7 +129,7 @@
 
 Package: gudhi-utils
 Section: math
-Architecture: amd64 arm64 i386 mips64el ppc64el s390x ia64 ppc64 riscv64 
sparc64 x32
+Architecture: amd64 arm64 i386 loong64 mips64el ppc64el s390x ia64 ppc64 
riscv64 sparc64 x32
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: Utilities from the GUDHI library
  The GUDHI library is a generic open source C++ library for

Bug#1059217: telegram-purple: add build support for loongarch64

[zhangdandan]

Source: telegram-purple
Version: 1.4.3-3
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control, for example,
```
Package: telegram-purple
# see #958828; little endian (big: hppa m68k powerpc ppc64 s390x sparc64)
-Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 ia64
 kfreebsd-amd64 kfreebsd-i386 mips64el mipsel ppc64el riscv64 sh4 x32
+Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 ia64
 kfreebsd-amd64 kfreebsd-i386 loong64 mips64el mipsel ppc64el riscv64 
sh4 x32


```
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059215: slinkwatch: add build support for loongarch64

[zhangdandan]

Source: slinkwatch
Version: 1.1-5
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control, for example,
```
Package: slinkwatch
-Architecture: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
riscv64 s390x
+Architecture: amd64 arm64 armel armhf i386 loong64 mips mips64el mipsel 
ppc64el riscv64 s390x

```
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059213: simka: add build support for loongarch64

[zhangdandan]

Source: simka
Version: 1.5.3-7
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control.
Please consider the patch I have attached.

The simka source package was compiled successfully on my local loong64 
rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru simka-1.5.3/debian/control simka-1.5.3/debian/control
--- simka-1.5.3/debian/control  2023-02-17 23:01:08.0 +
+++ simka-1.5.3/debian/control  2023-02-17 23:01:22.0 +
@@ -19,7 +19,7 @@
 Rules-Requires-Root: no
 
 Package: simka
-Architecture: any-amd64 arm64 mips64el ppc64el ia64 ppc64 riscv64 sparc64 alpha
+Architecture: any-amd64 arm64 loong64 mips64el ppc64el ia64 ppc64 riscv64 
sparc64 alpha
 Depends: ${shlibs:Depends},
  ${misc:Depends},
 Description: comparative metagenomics method dedicated to NGS datasets
diff -Nru simka-1.5.3/debian/tests/control simka-1.5.3/debian/tests/control
--- simka-1.5.3/debian/tests/control2023-02-17 22:59:24.0 +
+++ simka-1.5.3/debian/tests/control2023-02-17 23:01:22.0 +
@@ -1,4 +1,4 @@
 Tests: run-unit-test
 Depends: @
 Restrictions: allow-stderr
-Architecture: amd64 arm64 i386 ppc64el s390x hppa ia64 ppc64 riscv64 sparc64
+Architecture: amd64 arm64 i386 ppc64el s390x hppa ia64 loong64 ppc64 riscv64 
sparc64

Bug#1059212: spaln: add build support for loongarch64

[zhangdandan]

Source: spaln
Version: 2.4.13f+dfsg-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control.
Please consider the patch I have attached.

The spaln source package was compiled successfully on my local loong64 
rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru spaln-2.4.13f+dfsg/debian/control spaln-2.4.13f+dfsg/debian/control
--- spaln-2.4.13f+dfsg/debian/control   2023-02-05 20:42:42.0 +
+++ spaln-2.4.13f+dfsg/debian/control   2023-02-05 20:42:42.0 +
@@ -12,7 +12,7 @@
 Rules-Requires-Root: no
 
 Package: spaln
-Architecture: amd64 arm64 mips64el ppc64el s390x alpha ia64 kfreebsd-amd64 
ppc64 riscv64 sparc64
+Architecture: amd64 arm64 loong64 mips64el ppc64el s390x alpha ia64 
kfreebsd-amd64 ppc64 riscv64 sparc64
 Depends: ${shlibs:Depends},
  ${misc:Depends},
  spaln-data,

Bug#1059206: scikit-learn: FTBFS on loong64

[zhangdandan]

Source: scikit-learn
Version: 1.2.1+dfsg-1
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the scikit-learn failed for loong64 in the Debian Package 
Auto-Building environment.
The full compilation log can be found at 
https://buildd.debian.org/status/logs.php?pkg=scikit-learn=1.2.1%2Bdfsg-1%2Bb1=loong64


Refer to other architectures, need to add loong64 in d/rules where test 
suite results are ignored.


Please consider the patch I have attached.
The scikit-learn source package was compiled successfully on my local 
loong64 rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru scikit-learn-1.2.1+dfsg/debian/rules 
scikit-learn-1.2.1+dfsg/debian/rules
--- scikit-learn-1.2.1+dfsg/debian/rules2023-01-30 06:02:29.0 
+
+++ scikit-learn-1.2.1+dfsg/debian/rules2023-01-30 06:02:29.0 
+
@@ -108,7 +108,7 @@
 
 else
 # for all architectures that are known to have failures in test suite we are 
ignoring these
-ifeq ($(DEB_HOST_ARCH),$(filter $(DEB_HOST_ARCH), i386 mipsel mips64el hppa 
armel armhf arm64 ppc64 ppc64el s390x alpha riscv64 amd64))
+ifeq ($(DEB_HOST_ARCH),$(filter $(DEB_HOST_ARCH), i386 loong64 mipsel mips64el 
hppa armel armhf arm64 ppc64 ppc64el s390x alpha riscv64 amd64))
   # Ignored due to bug #1003165
 IGNORE_ERRORS= || true
 endif

Bug#1059192: ethflux: add build support for loongarch64

[zhangdandan]

Source: ethflux
Version: 1.0-4
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control, for examples,
```
Package: ethflux
-Architecture: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
riscv64 s390x
+Architecture: amd64 arm64 armel armhf i386 loong64 mips mips64el mipsel 
ppc64el riscv64 s390x

```

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059142: love: add build support for loongarch64

[zhangdandan]

Source: love
Version: 11.4-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

We need to add build support for loongarch64 in d/control.
Please consider the patch I have attached.

The love source package was compiled successfully on my local loong64 
rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru love-11.4/debian/control love-11.4/debian/control
--- love-11.4/debian/control2022-06-09 09:44:50.0 +
+++ love-11.4/debian/control2022-06-09 09:44:50.0 +
@@ -8,7 +8,7 @@
  debhelper-compat (= 13),
  libfreetype6-dev,
  liblua5.1-0-dev,
- libluajit-5.1-dev [!alpha !ia64 !ppc64el !riscv64 !sh4 !s390x],
+ libluajit-5.1-dev [!alpha !ia64 !loong64 !ppc64el !riscv64 !sh4 !s390x],
  libmodplug-dev,
  libmpg123-dev,
  libogg-dev,
@@ -30,7 +30,7 @@
 Vcs-Browser: https://salsa.debian.org/games-team/love
 
 Package: love
-Architecture: alpha any-i386 any-amd64 arm64 armel armhf ia64 mips64el mipsel 
ppc64el riscv64 sh4 x32
+Architecture: alpha any-i386 any-amd64 arm64 armel armhf ia64 loong64 mips64el 
mipsel ppc64el riscv64 sh4 x32
 Depends:
  ${misc:Depends},
  ${shlibs:Depends}

Bug#1054471: vtk9: FTBFS: add support for loongarch64

[zhangdandan]

Hi,

On Sun, 10 Dec 2023 22:31:42 +0800 Bo YU wrote:

> On Tue, Oct 24, 2023 at 05:28:02PM +0800, zhangdandan wrote:
> >Source: vtk9
> >Version: 9.1.0+really9.1.0+dfsg2-7
> >Severity: wishlist
> >Tags: ftbfs patch
> >User: debian-loonga...@lists.debian.org
> >Usertags: loong64
> >
>
> We can just open one reportbug to submit issue with the same theme. If
> we want to remind the maintainer to be noticed in time, we can follow-up
> with the same issue.
>
> I am trying to built it on my local build machines and then do team
> upload.
>
> BTW, what status for vtk9 upstream support loon64? It would be better to
> submit patch on Debian with `--dep3` standard to let the maintainer to
> learn more.

Please see this commit in vtk9 upstream: 
https://gitlab.kitware.com/seanm/vtk/-/commit/886b536a0d0bb3694951e09169a52896d585c517


thanks,
Dandan Zhang

Bug#1059090: elpi: add build support for loongarch64

[zhangdandan]

Source: elpi
Version: 8.5.4-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The elpi source package lacks LoongArch architecture support.
We need to add build support for loongarch64 in d/control, for examples,
```
Package: libelpi-ocaml
-Architecture: amd64 arm64 i386 ppc64el ppc64 riscv64 sh4
+Architecture: amd64 arm64 i386 loong64 ppc64el ppc64 riscv64 sh4

Package: libelpi-ocaml-dev
-Architecture: amd64 arm64 i386 ppc64el ppc64 riscv64 sh4
+Architecture: amd64 arm64 i386 loong64 ppc64el ppc64 riscv64 sh4

Package: elpi
-Architecture: amd64 arm64 i386 ppc64el ppc64 riscv64 sh4
+Architecture: amd64 arm64 i386 loong64 ppc64el ppc64 riscv64 sh4
```
I would like to remind you that the compilation dependencies of loong64 
elpi are not yet satisfied.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Bug#1059082: dpdk-kmods: enable build for loongarch64

[zhangdandan]

Source: dpdk-kmods
Version: 0~20220829+git-3
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The dpdk-kmods source package lacks LoongArch architecture support.
We need to add build support for loongarch64 in d/control.
Please consider the patch I have attached.

The dpdk-kmods source package was compiled successfully on my local 
loong64 rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru dpdk-kmods-0~20220829+git/debian/control 
dpdk-kmods-0~20220829+git/debian/control
--- dpdk-kmods-0~20220829+git/debian/control2022-12-30 15:47:15.0 
+
+++ dpdk-kmods-0~20220829+git/debian/control2022-12-30 15:47:30.0 
+
@@ -13,7 +13,7 @@
 Testsuite: autopkgtest-pkg-dkms
 
 Package: dpdk-kmods-dkms
-Architecture: amd64 arm64 i386 ppc64el riscv64
+Architecture: amd64 arm64 i386 loong64 ppc64el riscv64
 Depends: dkms, libelf-dev, make, ${misc:Depends},
 Description: Data Plane Development Kit (dkms)
  DPDK is a set of libraries for fast packet processing. Applications run