[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1015924: marked as done (pvm: ftbfs on riscv64("Unknown architecture!"))

Your message dated Sun, 15 Jan 2023 04:04:31 +0000
with message-id <E1pGuFz-0085JI-Hq@fasolo.debian.org>
and subject line Bug#1015924: fixed in pvm 3.4.6-5
has caused the Debian Bug report #1015924,
regarding pvm: ftbfs on riscv64("Unknown architecture!")
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.)


-- 
1015924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015924
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: pvm
Version: 3.4.6-3.2
Severity: minor
Tags: ftbfs, patch
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@lists.debian.org

Dear pvm Maintainer,

The pvm package has a ftbfs issue on riscv64:
```
...
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
Unknown architecture!
Unknown architecture!
echo "#!/bin/sh" > lib/pvmgetarch
echo "echo " > lib/pvmgetarch
chmod +x lib/pvmgetarch
chmod +x debian/getpvmarch
make PVM_ROOT=`pwd` clean
...
```

The full buildd log is here:

https://buildd.debian.org/status/fetch.php?pkg=pvm&arch=riscv64&ver=3.4.6-3.2&stamp=1636477315&raw=0


The patch attached is to fix the issue and I can build it on 
riscv64 arch with it, so please consider to apply it to fix the 
issue, thanks.

-- 
Regards,
--
  Bo YU


diff -Nru pvm-3.4.6/debian/getpvmarch pvm-3.4.6/debian/getpvmarch
--- pvm-3.4.6/debian/getpvmarch	2018-07-24 22:31:14.000000000 +0800
+++ pvm-3.4.6/debian/getpvmarch	2021-11-10 00:16:02.000000000 +0800
@@ -48,6 +48,9 @@
 	sh4)
 		echo LINUXSH
 		;;
+	riscv64)
+		echo LINUXRISCV
+		;;
 	*)
 		echo 'Unknown architecture!' 1>&2
 		exit 1;
diff -Nru pvm-3.4.6/debian/patches/27-add-riscv64-support.patch pvm-3.4.6/debian/patches/27-add-riscv64-support.patch
--- pvm-3.4.6/debian/patches/27-add-riscv64-support.patch	1970-01-01 07:30:00.000000000 +0730
+++ pvm-3.4.6/debian/patches/27-add-riscv64-support.patch	2021-11-10 00:16:02.000000000 +0800
@@ -0,0 +1,36 @@
+--- /dev/null
++++ b/conf/LINUXRISCV.def
+@@ -0,0 +1,10 @@
++ARCHCFLAGS     =       -DSYSVSIGNAL -DNOWAIT3 -DRSHCOMMAND=\"/usr/bin/rsh\" \
++                       -DNEEDENDIAN -DFDSETNOTSTRUCT -DHASERRORVARS \
++                       -DCTIMEISTIMET -DSYSERRISCONST -DHASREADLINE
++ARCHDLIB       =
++ARCHDOBJ       =
++ARCHLIB                =       -lreadline
++HASRANLIB      =       t
++AR             =       ar
++PVM_ARCH       =       LINUXRISCV
++MAKE           =       make
+--- /dev/null
++++ b/conf/LINUXRISCV.m4
+@@ -0,0 +1,20 @@
++divert(-1)
++undefine(`len')
++#
++# append an underscore to FORTRAN function names
++#
++define(`FUNCTION',`$1_')
++#
++# FORTRAN character strings are passed as follows:
++# a pointer to the base of the string is passed in the normal
++# argument list, and the length is passed by value as an extra
++# argument, after all of the other arguments.
++#
++define(`ARGS',`($1`'undivert(1))')
++define(`SAVE',`divert(1)$1`'divert(0)')
++define(`STRING_ARG',`$1_ptr`'SAVE(`, $1_len')')
++define(`STRING_ARG_DECL',`char * $1_ptr; int $1_len')
++define(`STRING_LEN',`$1_len')
++define(`STRING_PTR',`$1_ptr')
++divert(0)
++
diff -Nru pvm-3.4.6/debian/patches/series pvm-3.4.6/debian/patches/series
--- pvm-3.4.6/debian/patches/series	2020-08-19 22:48:23.000000000 +0800
+++ pvm-3.4.6/debian/patches/series	2021-11-10 00:16:02.000000000 +0800
@@ -27,3 +27,4 @@
 26-groff-quote.patch
 -fallow-argument-mismatch-in-examples-Makefile.aimk
 -fallow-argument-mismatch-in-gexamples-Makefile.aimk
+27-add-riscv64-support.patch

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: pvm
Source-Version: 3.4.6-5
Done: Bo YU <tsu.yubo@gmail.com>

We believe that the bug you reported is fixed in the latest version of
pvm, 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 1015924@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bo YU <tsu.yubo@gmail.com> (supplier of updated pvm 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: SHA512

Format: 1.8
Date: Sat, 14 Jan 2023 22:19:03 +0800
Source: pvm
Architecture: source
Version: 3.4.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bo YU <tsu.yubo@gmail.com>
Closes: 1015924
Changes:
 pvm (3.4.6-5) unstable; urgency=medium
 .
   * QA upload.
 .
   * Fix ftbfs on riscv64. (Closes: #1015924)
   * Set std ver to 4.6.2
Checksums-Sha1:
 20e8eea96ac17f68184ac6cd2228baec32fe163e 2016 pvm_3.4.6-5.dsc
 00e7db98fe581b11682a356281a3f2f24851bb51 24588 pvm_3.4.6-5.debian.tar.xz
 0280842701e145fa18521013f3ccc7de3bd723eb 6593 pvm_3.4.6-5_source.buildinfo
Checksums-Sha256:
 1cd3cb463e743f4d8ea1f6cd7e14a20d8bdc3e6497db6afab4d5db72f5dd61d5 2016 pvm_3.4.6-5.dsc
 e3b7694a725371902378285dd5cf045d1ed677b7d18e5533b9bf79775550446b 24588 pvm_3.4.6-5.debian.tar.xz
 447f98eabcb90dd01a73aab5342b1334292f3ebd9eac1e39aaaa45dcab57bff0 6593 pvm_3.4.6-5_source.buildinfo
Files:
 eb383d3d9db83aaba50405a9fa153f1f 2016 devel optional pvm_3.4.6-5.dsc
 c1d076f1a9fabab2ebc38e98e774e56b 24588 devel optional pvm_3.4.6-5.debian.tar.xz
 d1d96b1bf631a5e2ec5851ceadf64db0 6593 devel optional pvm_3.4.6-5_source.buildinfo

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

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmPDdhwACgkQweDZLphv
fH5rDg/+NENb0FayzTR03yfRlIMEH4v9B7SABAhr/8ytEJTbwg8hzBqGh0NrVppG
18d4feDNtsUvlFnWhfiOa4QVfYNPrdMMkVCkZ2cSZ0Nd0ZUUMx1LWFdt6miEakk2
vASFzD9Za1zBxt3QlDey90R908cdcP5DeJsLMN8W0nK/Yu3sYDpPbvjAfiYhbxI2
AMx+m760BUN7KKpEtoKsB0GbBsM7GL/6uhEsJM/Lc6yRps997VKHmw+z/IPaaWbR
/Ydl0dzxN1yNIMHh0Ztm3XmsmpsV4l8x0FsimROvqzT35uPmrckVdYuIlvSPuBpL
Tni2Y/T7dgNwgqOYxSVLZFIB6dO0h3UhxZmkgmPK94BhkvSBeiWWAEDdtWPtBH2O
DYtKHkSsTTy0ivHYI5Dj44+e38G6bZ04M4FCDfnh8h1t25u4LiE9+Ji70AVrGWGP
6f1Pfa6CCI4/dhnLenn0kbtBoKVBhcTz/k85dQXYMMNDc9eYJt0dqHH37SDOwfFK
2Axn+cT2pt7xts3h35aSGd3fhCXUc23zM8CxVECz75IQL/FoUdvxRlDMOBBUhe8q
0CpPzsKZ3U6c+GrLNVruW4RY7gRC3sj9nL4quOXyCggei8O7aKCGxI9hihQg6Oy7
4x5YbEvOOOnX1b6kKkWx3G6xZeYyNW028V0aLaSLO9rfOvQZs/8=
=Vf3s
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: