Your message dated Fri, 27 Sep 2024 14:39:32 +0000
with message-id <e1suc84-00exlm...@fasolo.debian.org>
and subject line Bug#1068685: fixed in tup 0.7.11-5
has caused the Debian Bug report #1068685,
regarding tup: FTBFS on loong64
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 ow...@bugs.debian.org
immediately.)
--
1068685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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&ver=0.7.11-4&arch=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:
--- End Message ---
--- Begin Message ---
Source: tup
Source-Version: 0.7.11-5
Done: Gianfranco Costamagna <locutusofb...@debian.org>
We believe that the bug you reported is fixed in the latest version of
tup, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gianfranco Costamagna <locutusofb...@debian.org> (supplier of updated tup
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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 27 Sep 2024 16:13:06 +0200
Source: tup
Built-For-Profiles: noudeb
Architecture: source
Version: 0.7.11-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Gianfranco Costamagna <locutusofb...@debian.org>
Closes: 1068685
Changes:
tup (0.7.11-5) unstable; urgency=medium
.
* Team upload.
[ zhangdandan <zhangdan...@loongson.cn> ]
* Add support for loong64 (Closes: #1068685)
Checksums-Sha1:
7f1cf6a90d89e9ccdc97ff66b595ed96cba91157 1936 tup_0.7.11-5.dsc
1ea70448e0700555909c6a711b6271418219140e 12404 tup_0.7.11-5.debian.tar.xz
73234e3fa565964417a4aa8feefb86db6b33e910 8240 tup_0.7.11-5_source.buildinfo
Checksums-Sha256:
a9b240371adb4e480bbdd4ed792834213a74c58b38a8236966259dab220e63a2 1936
tup_0.7.11-5.dsc
dc90a261dff7f23b044fdae425abd7e519f40ec32df223f9f5ae1e31725b7faf 12404
tup_0.7.11-5.debian.tar.xz
884977811d7632927b132436df9fa313584f768d5931f991cf76243d33ab92e7 8240
tup_0.7.11-5_source.buildinfo
Files:
d334364d1fa76459a936616116ffa80a 1936 devel optional tup_0.7.11-5.dsc
f9c74e3dab9da04df6f988a717b55975 12404 devel optional
tup_0.7.11-5.debian.tar.xz
fc600e5a98b3de936d271191f88dd1b1 8240 devel optional
tup_0.7.11-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmb2vZ8ACgkQ808JdE6f
XdnLCRAAgx+5fpF5H4+f7pj3qWvKKcsNrfPpbSMwDoTicfGJEjbVBt/zrKA/OB6J
NuYj8AKJdqME0w/P6Z1Exf+qY2Mp3ghO/5n0WMMrZW16hDpFz4zX+LJdgJknbxHE
nxIFrAnGAMN5rcXlOdh2vZcmpYGz7qbQ4Y9de793nB4iN+khR2TMkiNKE8vmR+Ev
gMRJr9q9fs+TTb3b5pmAfz2cnh/buptRcqaYWAUDK8bV7K8pMI7RmgTNMTe2LtCS
7YIKHld1v+ZkDhp/eKVz9TQm7w6KmnyRqpvef0/zvvBuIAkIubuHJR9uVYPrvGoq
CCVcIuRTp+1ik8XOzJocJcdYuD4fr9H6I1leVgFRgb2JBGJnOH+q84yUvFE5jsFk
InSsamryIOHUl9G89qAc53SvFn/V/v4ZrF3BAUP3loP84/NV1yzukCiSv0yso1JA
bDtURGV4QNQYl9TzWCE+gmGfEAGT1W3zfVev7iY7SZwJqJGHSm3Ss72sOuNh7arO
Ic/zounP8Zhpu1baAFBS0/+FStJLAVIPVWEcXrx6uoYD/PW+3oU/QZNHs5sf5kP9
1lcVrgV6HWD85zc01XYPoZdWqGa2XslpGJAxtPHwsIYLzXAgi8LkgeVNG/zqHQ4B
bGaK9ixAUMfgikiQwjEmcCTfZm1BoiVBuKsPHL/goMlKvnhKdxo=
=mVqu
-----END PGP SIGNATURE-----
pgpAXQxlX_AdM.pgp
Description: PGP signature
--- End Message ---
