Your message dated Thu, 31 Oct 2024 17:22:11 +0000 with message-id <E1t6Ys7-00FOiK-U3@fasolo.debian.org> and subject line Bug#1051821: fixed in a2jmidid 9-3.1 has caused the Debian Bug report #1051821, regarding a2jmidid: FTBFS: enable build for LoongArch 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 owner@bugs.debian.org immediately.) -- 1051821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051821 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
- Subject: a2jmidid: FTBFS: enable build for LoongArch
- From: zhangdandan <zhangdandan@loongson.cn>
- Date: Wed, 13 Sep 2023 11:22:21 +0800
- Message-id: <efbbdb89-4cb8-6b4e-8044-dd0e2b407f38@loongson.cn>
Package: a2jmidid Version: 9-3 Severity: normal Tags: patch ftbfs User: debian-devel@lists.debian.org Usertags: loongarch64 Dear maintainers,When compiling the package a2jmidid for loong64 in the Debian Package Auto-Building environment [1], The error message is as follows:......Omit ../sigsegv.c: In function ‘signal_segv’: ../sigsegv.c:97:20: error: ‘NGREG’ undeclared (first use in this function) 97 | for(i = 0; i < NGREG; i++) | ^~~~~../sigsegv.c:97:20: note: each undeclared identifier is reported only once for each function it appears inIn file included from ../sigsegv.c:39:../sigsegv.c:106:39: error: ‘mcontext_t’ has no member named ‘gregs’; did you mean ‘__gregs’?106 | ucontext->uc_mcontext.gregs[i] | ^~~~~ ../log.h:47:134: note: in definition of macro ‘a2j_error’ ......Omit The full compilation log can be found at [2]. Please consider the patch I have attached.BTW, the patch I provided in the attachment doesn't affect other architectures and compiles fine on the loongarch architecture.If you have any questions, you can contact me at any time. [1]:https://buildd.debian.org/status/package.php?p=a2jmidid&suite=sid [2]:https://buildd.debian.org/status/logs.php?pkg=a2jmidid&ver=9-3&arch=loong64 thanks, Dandan ZhangDescription: Add support for loongarch Last-Update: 2023-09-13 --- a2jmidid-9.orig/sigsegv.c +++ a2jmidid-9/sigsegv.c @@ -93,7 +93,7 @@ static void signal_segv(int signum, sigi a2j_error("info.si_addr = %p", info->si_addr); #if !defined(__alpha__) && !defined(__ia64__) && \ !defined(__FreeBSD_kernel__) && !defined(__arm__) && !defined(__hppa__) && \ - !defined(__sh__) && !defined(__aarch64__) && !defined(__riscv) + !defined(__sh__) && !defined(__aarch64__) && !defined(__riscv) && !defined(__loongarch__) for(i = 0; i < NGREG; i++) a2j_error("reg[%02d] = 0x" REGFORMAT, i, #if defined(__powerpc__) && !defined(__powerpc64__) @@ -106,7 +106,7 @@ static void signal_segv(int signum, sigi ucontext->uc_mcontext.gregs[i] #endif ); -#endif /* alpha, ia64, kFreeBSD, arm, hppa, aarch64, riscv */ +#endif /* alpha, ia64, kFreeBSD, arm, hppa, aarch64, riscv, loongarch */ #if defined(SIGSEGV_STACK_X86) || defined(SIGSEGV_STACK_IA64) # if defined(SIGSEGV_STACK_IA64)
--- End Message ---
--- Begin Message ---
- To: 1051821-close@bugs.debian.org
- Subject: Bug#1051821: fixed in a2jmidid 9-3.1
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Thu, 31 Oct 2024 17:22:11 +0000
- Message-id: <E1t6Ys7-00FOiK-U3@fasolo.debian.org>
- Reply-to: Gianfranco Costamagna <locutusofborg@debian.org>
Source: a2jmidid Source-Version: 9-3.1 Done: Gianfranco Costamagna <locutusofborg@debian.org> We believe that the bug you reported is fixed in the latest version of a2jmidid, 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 1051821@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna <locutusofborg@debian.org> (supplier of updated a2jmidid 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 26 Oct 2024 18:04:34 +0200 Source: a2jmidid Built-For-Profiles: noudeb Architecture: source Version: 9-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org> Changed-By: Gianfranco Costamagna <locutusofborg@debian.org> Closes: 1051821 1067662 Launchpad-Bugs-Fixed: 2058799 Changes: a2jmidid (9-3.1) unstable; urgency=medium . * Non-maintainer upload. . [ zhangdandan <zhangdandan@loongson.cn> ] * Enable building for LoongArch (Closes: #1051821) . [ Erich Eickmeyer ] * Patch: add port id to port name to avoid collision (LP: #2058799) - (Closes: #1067662) Checksums-Sha1: a6dfad9ef42da02105568af3078925afc5a40ad7 2014 a2jmidid_9-3.1.dsc ff93fb6166dfe154acb7fdca5aaa83fa0f0a621e 5992 a2jmidid_9-3.1.debian.tar.xz 623fb5deed9406590485e1c092b00b41d1a654d0 8498 a2jmidid_9-3.1_source.buildinfo Checksums-Sha256: 2f1cb79c582d7067a5f4aeed08a69a241211d9bbb83f52495dacc229b95de1cb 2014 a2jmidid_9-3.1.dsc f293d5bee969d3c1e9743742352f98b62aea4e51ec1faead99c55705137f761a 5992 a2jmidid_9-3.1.debian.tar.xz e5883ac2d6ad0ce194b4107f5d60dec052eb681c00d42dc0f678c58a078e8b74 8498 a2jmidid_9-3.1_source.buildinfo Files: 1223042d01380de9292fe8486a97399f 2014 sound optional a2jmidid_9-3.1.dsc beb3578671ed1cbf85bdebeaa5188f57 5992 sound optional a2jmidid_9-3.1.debian.tar.xz 44a2733356ccf9cf3c950024ce214d07 8498 sound optional a2jmidid_9-3.1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmcdFZMACgkQ808JdE6f Xdl2Ag//fE3aRtlC7X3NzNDGbxOZVjpFweiqxsY5DXhHh8xdecYrasT86ewjOgmk MtaUNw6Of19BARagPhcCeya//JAYkSxIG6hQ4x0gEp7yGg5nMvczqDG7qXY5ewJ3 gXHSzb54os6oxKaxCCgWq05fo/uxFqaGoSMQj1mhG1WZGZzR8gKNEPnDrjaQNVNI txhMzX3KBUx6BNIssFLsHhA7RAs+12j3Idj0xn8xHTJO8GX0ahQcQyqmuRxSFtD6 YnsFvmpMwCk3D+UO+KPxZYA9LPFuFbSwlXfZHh64nXpEUI7UNrUg3do4ZOVPiAJE 6slNtwhQY+k0vYIoCmNZeTCVD+FZZ4SCb2lRPgBu2nPyfJousoGIBXeHffTR3d5m kGCyrPUcgmFlyDWZyIqNoJXioL3IGMFss21dDpdktm1f/2iUy7cFw0on9BP23G3i 2yoWlNwhKOyV3eteXX91ZqUj3IAOezLMuvysl0cqhBVeD/ToU/3ovZ3z5K8wqIlI 9/zQy2cN7Cdpa/2GjK/hliie/oK28d6yQxXwyVMQNobfjmMyH+cE9I/yuxtBGWWs VU54IKOj9vkDjAZU48nyjfuYy1HNCP3u4D1hmRTHc8+GmxGyl8EAvGM/VYZY4Mbd UwEs4UMpYbfa2fboorJEqXnOprJcjizFRBBNfAn6wfyuOMSyUUo= =g1er -----END PGP SIGNATURE-----Attachment: pgpNT7jL9EEl6.pgp
Description: PGP signature
--- End Message ---