Hi, On Sat, Aug 20, 2022 at 06:22:17PM -0500, Dirk Eddelbuettel wrote:
On 19 August 2022 at 07:21, Bo YU wrote: | Source: tiledb-r | Version: 0.15.0-1 | Severity: normal | Tags: ftbfs, patch | User: debian-ri...@lists.debian.org | Usertags: riscv64 | X-Debbugs-Cc: debian-ri...@lists.debian.org | | Dear Maintainer, | | The tiledb-r has a ftbfs on riscv64 due to missing -latomic explicitly | after 0.13.0-1: | | https://buildd.debian.org/status/logs.php?pkg=tiledb-r&arch=riscv64 | | The full buildd log failed is here: | https://buildd.debian.org/status/fetch.php?pkg=tiledb-r&arch=riscv64&ver=0.15.0-1&stamp=1660431861&raw=0 | | The patch attached is trying to fix issue as you suggested. | And I'll check if there are other r-cran-* packages with similar problems also. Ok I'll deal with it (and I am actually upstream for it so I can do it in a local debian/patches file or upstream) -- the proper way is in configure.ac conditional on the architecture. So what is the proper architecture name for riscv64, and please remind me what the best way to determine it is (uname -m ? Or uname -p ? Or uname -i ?)
There is only usefully for $(uname -m) for riscv64 hadreware now.
vimer@unmatched:~/build/08/33_gridengine$ uname -m
riscv64
vimer@unmatched:~/build/08/33_gridengine$ uname -p
unknown
vimer@unmatched:~/build/08/33_gridengine$ uname -i
unknown
BTW, I saw the solution is ok also.
ifeq ($(DEB_HOST_ARCH),riscv64)
# do something
endif
Is it ok for our case?
Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
-- Regards, -- Bo YU
signature.asc
Description: PGP signature
