Your message dated Sun, 23 Mar 2025 21:15:59 +0000
with message-id <[email protected]>
and subject line Bug#1098244: fixed in lnav 0.12.4-1
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
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 20:37:34 +0100
Source: lnav
Architecture: source
Version: 0.12.4-1
Distribution: unstable
Urgency: medium
Maintainer: Salvatore Bonaccorso <[email protected]>
Changed-By: Salvatore Bonaccorso <[email protected]>
Closes: 1098244
Changes:
lnav (0.12.4-1) unstable; urgency=medium
.
* Upload to unstable
.
lnav (0.12.4-1~exp3) experimental; urgency=medium
.
* Correct disabling of test_sql_json_func.sh test
.
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
.
lnav (0.12.4-1~exp1) experimental; urgency=medium
.
* New upstream version 0.12.4
* debian/control: Add Build-Depends on libunistring-dev
* Update copyright years for upstream files
* Update copyright years for debian/* packaging files
* Disable test_cmds.sh test
Checksums-Sha1:
6e9939a85d0ac58912141a732cc7d217527b1019 2133 lnav_0.12.4-1.dsc
0737b536410fe4464701c3baa45dd5dd55c6f543 11220 lnav_0.12.4-1.debian.tar.xz
Checksums-Sha256:
845a42172799428f9d5a1caf00bd5a0013380927e58208becb36507457ca9bab 2133
lnav_0.12.4-1.dsc
884c6fb2729ccfe0d9078f18349fc25271f9fb0bc119f1991ddca26cb9efe940 11220
lnav_0.12.4-1.debian.tar.xz
Files:
c1555f8571858cdf1bbbb9fe2cd20b57 2133 admin optional lnav_0.12.4-1.dsc
cb5f5f7c4d0a1ee994803e09af29b4ab 11220 admin optional
lnav_0.12.4-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmfgZKtfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ERgkP/jfSDyN4fU4fRjlBxj3U2YiBrzTntdDG
9e8KizDpmTgpOaFDhDBGgeeMsW9k0KM26OOy+k8X9DyL8UwqswRga4GL628RBph9
+c5zzYUu12iXsdXlPHm9tg4hkdx0xANQRnmhaj9fpM0cSzqe+hcEJAnX6JUMc0Q9
P/ZqtXUUE0xQnk+recq3jO+7D/htWVtl7jvPgsGb5VI8F48ydMNSGuiroWnS/UF7
FYPAFrHWl/C7qI3yjtZqSC4MXXAQypYuG/tCGYSyIo9chl2VV9MXAVMtdQnHm9DW
8ERZZRLWfJTNsvkEO2yAYD/RjYw7LvnwjNlSQYRvixGGjrY0BCbsmCJc5lVAsPWG
+IL8Qfs3KgfCGc7eQlTMDjE0c1s2F/73/KAf9Z5wHfR1Ii1wpdPOQsnkfq1d4ml2
7p5MATBibwiQLNId+Y74q676fGnCOirQ7xjLuB+xwIXTOaY4II6NlswNlXjyhY9g
+dwMRb/yuzMdFUy0BJT8WUcpzrtkqBS+p3JV3XmUw7fFy6D/13RwRggxky/La4g6
w+V2MOGwaV3qrQA/KI7psI1cvZfNxxXp0zmN4sbrbkjGuZnKViM4xg+6dSHZBYh8
K0uBLQemrUYSZKTzODMimJ12vIXQD3Yl4SEPigAnsd9zadW2+R4cEkt9jon0CLsT
em70sabPHrpF
=5Fd+
-----END PGP SIGNATURE-----
pgp97cTH8pJ8n.pgp
Description: PGP signature
--- End Message ---
