Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 0A2B7780E90 for ; Mon, 29 Nov 2021 14:58:15 +0000 (UTC) Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salkield.uk; s=key1; t=1638197895; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ePZmbnXTA74lCvrGIygWmYHB4q9GVMaC6fsznfYJnCg=; b=gOCrmXMfbzi0k48vmo/9FpUXIayk96T8MTcWvZvagrtcNcsilpvmhL8FntU3/mq/9GI55+ AsTqHYg19NNk2bO46hVg/4dflL73qiJgnsxW7coLX5aioGN33BMBpGKLn3Hwlffa/gT62T 3mSSrPhZsOBXC+p+nPGKCtCwwq6Z57o= Subject: Re: [PATCH v2] testing/hdf4: new aport X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Edd Salkield To: alpine-aports@lists.alpinelinux.org Date: Mon, 29 Nov 2021 14:58:14 +0000 In-Reply-To: <163795873462.14324.16389014921358879731.gitlab.27817.36ed4f9943c44bac014f5eec6cfea5dadf3eb309@listserv.local> References: <163795873462.14324.16389014921358879731.gitlab.27817.36ed4f9943c44bac014f5eec6cfea5dadf3eb309@listserv.local> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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.