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

Bug#898475: astropy: Please support riscv64, problem with cfitsio



Source: astropy
Version: 3.0-3
Severity: normal
User: debian-riscv@lists.debian.org
Usertags: riscv64

Hi,

This package FTBFS under riscv64:

  https://buildd.debian.org/status/fetch.php?pkg=astropy&arch=riscv64&ver=3.0-3&stamp=1525457671&raw=0

The thing that it complains about is cfitsio not being ported:
==========================================================
RuntimeError: unknown error 1.

/tmp/astropy-test-uxz2amon/lib/python3.6/site-packages/docs/io/fits/usage/unfamiliar.rst:512: UnexpectedException
 61 failed, 10491 passed, 201 skipped, 58 xfailed, 4 xpassed in 7626.39 seconds 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 Byteswapping is not being done correctly on this system.
 Check the MACHINE and BYTESWAPPED definitions in fitsio2.h
 Please report this problem to the CFITSIO developers.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
...
==========================================================


However, src:cfitsio is ready for riscv64:

  https://packages.qa.debian.org/c/cfitsio/news/20180406T195008Z.html

  cfitsio (3.430-2) unstable; urgency=medium
  .
    * Add 10-riscv.patch to add support for riscv64.


src:astropy contains an embedded copy of cfitsio, so perhaps it's using this
copy instead of the one in the system (it has "libcfitsio-dev | libcfitsio3-dev"
in the build-dependencies):

  https://sources.debian.org/src/astropy/3.0-3/cextern/cfitsio/lib/cfileio.c/?hl=4072#L4071


So if it's possible to use the one in the system it would be great, it should
fix both problems (riscv64 support, and other ports in the future, and using an
embedded copy).


BTW, src:astropy builds python3-astropy (note the '3'), and not sure what's the
relationship between this one and python-astropy (for Python 2), but the latter
also built fine in this architecture.


Thanks and cheers.
--
Manuel A. Fernandez Montecelo <mafm@debian.org>


Reply to: