Received: from listserv.local (listserv [172.16.8.22])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTP id 81675780E90;
	Mon, 29 Nov 2021 14:58:23 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Edd Salkield <edd@salkield.uk>
From: mailinglist-bot <no-reply@dispatch.alpinelinux.org>
Cc: alpine-aports@lists.alpinelinux.org
In-Reply-To: 
 <163795873462.14324.16389014921358879731.gitlab.27817.36ed4f9943c44bac014f5eec6cfea5dadf3eb309@listserv.local>
Subject: Re: [PATCH v2] testing/hdf4: new aport
Date: Mon, 29 Nov 2021 14:58:23 -0000
Message-ID: 
 <163819790350.14324.5711378711444502446.gitlab.27817.36ed4f9943c44bac014f5eec6cfea5dadf3eb309@listserv.local>

Edd Salkield <edd@salkield.uk> replied via email:

```
I had a quick look around, and found that Fedora applies some downstream
patches to get hdf4 compiling on s390 and various ARM processes:
https://src.fedoraproject.org/rpms/hdf/tree/rawhide  We could consider
including some of these to see if it allows the build to succeed
instead.

If we were to do this, what would be the process to bring these patch
files in?  We could source them from Fedora, or have them included
locally.

Also, is there a way for me to test out whether this causes the builds
to succeed without resubmitting patches repeatedly?  I don't have access
to all the necessary hardware to do it all my end, and I'd ideally like
to submit some builds directly to the servers.


```

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27817#note_195473