From: Andreas Enge <andreas@enge.fr>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add hdf4
Date: Sun, 16 Oct 2016 17:05:19 +0200 [thread overview]
Message-ID: <20161016150519.GA29166@solar> (raw)
In-Reply-To: <20161014.110029.603260973900204345.post@thomasdanckaert.be>
Hi Thomas,
On Fri, Oct 14, 2016 at 11:00:29AM +0200, Thomas Danckaert wrote:
> as far as I understand, the header hdfi.h defines fixed width datatypes such
> as float64, uint8, int32, ... depending on the detected architecture, and
> it's not detecting mips and arm properly.
>
> I've checked, and see that Debian has a number patches for this and related
> issues
thanks for your comments! I picked a (rather large) patch from Debian
modifying hdfi.h, and the package now builds on arm. I pushed this, and
we will see for mips once hydra tries to build it (there is also a mips
specific patch on debian).
> Ideally, HDF4 maintainers would fix this in a future release. I can try to
> contact them.
That would be nice, assuming that hdf4 is still maintained.
Andreas
next prev parent reply other threads:[~2016-10-16 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 8:57 [PATCH] gnu: Add hdf4 Thomas Danckaert
2016-10-12 12:54 ` Ludovic Courtès
2016-10-12 18:50 ` Thomas Danckaert
2016-10-12 20:28 ` Ludovic Courtès
2016-10-14 8:11 ` Andreas Enge
2016-10-14 11:13 ` Thomas Danckaert
[not found] ` <20161014.110029.603260973900204345.post@thomasdanckaert.be>
2016-10-16 15:05 ` Andreas Enge [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-23 17:22 Jeremy Robst
2016-05-23 18:17 ` Leo Famulari
2016-05-24 13:20 ` Jeremy Robst
2016-05-24 19:06 ` Eric Bavier
2016-05-25 17:42 ` Jeremy Robst
2016-05-27 17:19 ` Leo Famulari
2016-05-28 14:32 ` Ludovic Courtès
2016-05-29 17:36 ` Jeremy Robst
2016-05-29 22:07 ` Ludovic Courtès
2016-06-02 14:43 ` Eric Bavier
2016-06-02 14:58 ` Jeremy Robst
2016-06-03 8:37 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161016150519.GA29166@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).