Your message dated Sun, 23 Mar 2025 15:08:03 +0000
with message-id <[email protected]>
and subject line Bug#1098244: fixed in lnav 0.12.4-1~exp2
has caused the Debian Bug report #1098244,
regarding lnav: FTBFS: Add loongarch64 support
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1098244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098244
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lnav
Version: 0.12.3-1
Severity: normal
Tags: FTBFS patch
User: [email protected]
Usertags: loong64

Dear maintainers,

Compiling the lnav failed for loong64 in the Debian Package Auto-Building environment.
The error log is as follows,
```
In file included from yaml-extension-functions.cc:36:
./third-party/rapidyaml/ryml_all.hpp:514:5: error: #error "unknown CPU architecture"
  514 |    #error "unknown CPU architecture"
      |     ^~~~~
g++ -std=c++17 -DHAVE_CONFIG_H -I. ......
```
The full build log can be found at https://buildd.debian.org/status/logs.php?pkg=lnav&ver=0.12.3-1&arch=loong64.

Please consider the patch I attached.
Based on the attached patch, lnav 0.12.3-1 was built successfully on local ENV.
```
Testsuite summary for lnav 0.12.3
=====================================
# TOTAL: 40
# PASS:  40
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
=====================================
......
   dh_builddeb
dpkg-deb: building package 'lnav-dbgsym' in '../lnav-dbgsym_0.12.3-1_loong64.deb'.
dpkg-deb: building package 'lnav' in '../lnav_0.12.3-1_loong64.deb'.
 dpkg-genbuildinfo -O../lnav_0.12.3-1_loong64.buildinfo
 dpkg-genchanges -O../lnav_0.12.3-1_loong64.changes
......
```

Your opinions are welcome.

Best regards,
Dandan Zhang

Description: Add loongarch64 support
Last-Update: 2025-02-18

--- lnav-0.12.3.orig/src/third-party/rapidyaml/ryml_all.hpp
+++ lnav-0.12.3/src/third-party/rapidyaml/ryml_all.hpp
@@ -498,6 +498,10 @@ C4_FOR_EACH(PRN_STRUCT_OFFSETS, a, b, c)
    #endif
    #define C4_BYTE_ORDER _C4EL
 
+#elif defined(__loongarch64)
+   #define C4_CPU_LOONGARCH64
+   #define C4_WORDSIZE 8
+
 #elif defined(mips) || defined(__mips__) || defined(__mips)
 
     #define C4_WORDSIZE 8
@@ -1810,6 +1814,15 @@ __inline__ static void trap_instruction(
 	 * 'riscv_sw_breakpoint_from_kind' */
 	__asm__ volatile(".4byte 0x00100073");
 }
+#elif defined(__loongarch64)
+	#define DEBUG_BREAK_IMPL DEBUG_BREAK_USE_TRAP_INSTRUCTION
+__attribute__((always_inline))
+__inline__ static void trap_instruction(void)
+{
+	/* See 'loongarch-tdep.c' in GDB source,
+	 * 'loongarch_default_breakpoint' */
+	__asm__ volatile(".4byte 0x002a0005");
+}
 #else
 	#define DEBUG_BREAK_IMPL DEBUG_BREAK_USE_SIGTRAP
 #endif
@@ -7503,7 +7516,7 @@ from_chars_result from_chars_advanced(co
        || defined(__MINGW64__)                                          \
        || defined(__s390x__)                                            \
        || (defined(__ppc64__) || defined(__PPC64__) || defined(__ppc64le__) || defined(__PPC64LE__)) \
-       || defined(__EMSCRIPTEN__))
+       || defined(__EMSCRIPTEN__)) || defined(__loongarch64)
 #define FASTFLOAT_64BIT
 #elif (defined(__i386) || defined(__i386__) || defined(_M_IX86)   \
      || defined(__arm__) || defined(_M_ARM)                   \

--- End Message ---
--- Begin Message ---
Source: lnav
Source-Version: 0.12.4-1~exp2
Done: Salvatore Bonaccorso <[email protected]>

We believe that the bug you reported is fixed in the latest version of
lnav, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso <[email protected]> (supplier of updated lnav package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 23 Mar 2025 15:41:00 +0100
Source: lnav
Architecture: source
Version: 0.12.4-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Salvatore Bonaccorso <[email protected]>
Changed-By: Salvatore Bonaccorso <[email protected]>
Closes: 1098244
Changes:
 lnav (0.12.4-1~exp2) experimental; urgency=medium
 .
   * Add loongarch64 support (Closes: #1098244)
   * Disable broken test_sql_indexes.sh test
   * Declare compliance with Debian policy 4.7.2
Checksums-Sha1: 
 778b6bb867314d273fddea33d5362efc5dd534b3 2153 lnav_0.12.4-1~exp2.dsc
 5bc7a6bf4abbff978c9147c8430a492de9ff9f29 11216 lnav_0.12.4-1~exp2.debian.tar.xz
Checksums-Sha256: 
 c91903d5fcad44321c22661360602d2590ad44097b075118fe0d3a5ce63d87b7 2153 
lnav_0.12.4-1~exp2.dsc
 4042346639213dc3904d37585371c505668b4b42a964925b82d00b1078590d0c 11216 
lnav_0.12.4-1~exp2.debian.tar.xz
Files: 
 efb26c6c90bc025855329b1546078b30 2153 admin optional lnav_0.12.4-1~exp2.dsc
 c835e0805f8b2a3092e5ac53229eae46 11216 admin optional 
lnav_0.12.4-1~exp2.debian.tar.xz


-----BEGIN PGP SIGNATURE-----

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmfgH41fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E0L0P/1BljnMXSUmoR7YEfJ4B/eeS+1KQaBzv
KDfc4+R+XT03+l20wAuWEyousZz9o7lR59wzbadA6skLLJS/yN39p6apYQeck9LN
QexPpyYfueFuyhSzQXOt9TePC/QT/4WD2qTtRIXHcd84aP+M1ADzVg6j0dKfRUjK
BY3JV9hJ0+zI+EWlRI17sLT1Qx6wIEXwsIm1oCFXAeYULvynZOULerHSoXZ++aRW
rxM5Ju8Uc1bqoifBGXZmMMKauimuZ9eX80Q97hPT3257LJxp0jSV3zwN0EVpzh+D
0KUJIvWu2RMXaXkCOkZHEOHtAUSjlNpVLwQp4cGuSvNR7bptgVo+0yXBfXrhrZml
lSXP3N0fsX+t/++Jqm+iq7xd1OAJCHR9IvIyqEPp3OGjXzaLnhvX++LkDEMIsvzt
7eqdzMyx63FdE3ay2P+6TbwwoA7tiGq/LGQiwH3oBrsFYC4PxqsGW8aVZCcCPchJ
oR+esPTyvZlFjTXrgz3r2gWt00UMAgbjOqL/y+ikQKSc7Dwz9zSU0naTusILmAA3
b+ElPluUoN8XGJrqAE2rpR+teoyAAiKwG47mDNpKGUsP7oAjUAKoHU8S59fj87Xj
dGfCKIY+EBKwixG/Ua5cr8flSTpZKoS3HhghDwe13KDrd7WOiMva3nCS3S0mttLP
tf39HHSCEVp9
=9oz2
-----END PGP SIGNATURE-----

Attachment: pgpn1u3I6bnnT.pgp
Description: PGP signature


--- End Message ---

Reply via email to