Your message dated Tue, 01 Jul 2025 03:49:45 +0000
with message-id <[email protected]>
and subject line Bug#1107056: fixed in libhdf4 4.3.1-1~exp1
has caused the Debian Bug report #1107056,
regarding libhdf4 FTCBFS: gfortran dependency not satisfiable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1107056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107056
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libhdf4
Version: 4.3.0-1
Tags: patch
User: [email protected]
Usertags: ftcbfs
libhdf4 fails to cross build from source, because its gfortran build
dependency is not satisfiable. In general, bare toolchain dependencies
are not compatible with cross compilation, because they do not indicate
the architecture they are used for. In this case, gfortran-for-host
should be used.
Note that gfortran-for-host does not provide a bare gfortran. For using
it, it must be invoked as ${DEB_HOST_GNU_TYPE}-gfortran. All other
alternatives regress some other use case. Hence I propose letting dpkg's
buildtools.mk initialize F77.
With these changes, we may run configure, but that fails detecting
whether szip provides an encoder. It invokes SZ_encoder_enabled() and
this is not something we can do during cross compilation. Recent
versions always have encoder support, so I suggest guessing this during
cross builds.
With that additional change, configure passes, but make still fails. It
runs ncgen during build for ctest0 and ftest0. Both are check programs
not needed in a nocheck build, but the upstream build system insists
building them. For one thing, mfhdf/ncgen/Makefile.am adds them to
noinst_PROGRAMS (which it likely should not do). For another
config/conclude.am explicitly adds $(chk_TESTS) to all-local so even
then check_PROGRAMS are built with the all target. I tried removing
them from the nocheck build, but I did not find a good way to achieve
that. Thus leaving this aspect unaddressed for the moment. Let me know
if you have good ideas.
I note that the patch is meant for forky, not trixie. And then even if
you leave the ncgen aspect unaddressed, please close this bug when
addressing the Build-Dependency.
Helmut
diff --minimal -Nru libhdf4-4.3.0/debian/changelog
libhdf4-4.3.0/debian/changelog
--- libhdf4-4.3.0/debian/changelog 2024-04-09 20:42:32.000000000 +0200
+++ libhdf4-4.3.0/debian/changelog 2025-05-31 17:49:16.000000000 +0200
@@ -1,3 +1,10 @@
+libhdf4 (4.3.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Improve cross building: Use gfortran-for-host. (Closes: #-1)
+
+ -- Helmut Grohne <[email protected]> Sat, 31 May 2025 17:49:16 +0200
+
libhdf4 (4.3.0-1) unstable; urgency=medium
* Team upload.
diff --minimal -Nru libhdf4-4.3.0/debian/control libhdf4-4.3.0/debian/control
--- libhdf4-4.3.0/debian/control 2024-04-09 20:42:13.000000000 +0200
+++ libhdf4-4.3.0/debian/control 2025-05-31 17:47:51.000000000 +0200
@@ -8,7 +8,7 @@
chrpath,
debhelper-compat (= 13),
flex,
- gfortran,
+ gfortran-for-host,
libaec-dev,
libjpeg-dev,
libtirpc-dev,
diff --minimal -Nru libhdf4-4.3.0/debian/patches/cross.patch
libhdf4-4.3.0/debian/patches/cross.patch
--- libhdf4-4.3.0/debian/patches/cross.patch 1970-01-01 01:00:00.000000000
+0100
+++ libhdf4-4.3.0/debian/patches/cross.patch 2025-05-31 17:49:16.000000000
+0200
@@ -0,0 +1,26 @@
+--- libhdf4-4.3.0.orig/configure.ac
++++ libhdf4-4.3.0/configure.ac
+@@ -845,15 +845,16 @@
+ else
+ exit(1);
+ }
+- ]])],[CAN_ENCODE="yes"],[CAN_ENCODE="no"],[])
+-
+- ## Report szip encoder test results
+- if test "X$CAN_ENCODE" = "Xyes"; then
++ ]])],[
+ AC_MSG_RESULT([yes])
+- fi
+- if test "X$CAN_ENCODE" = "Xno"; then
++ CAN_ENCODE="yes"
++ ],[
+ AC_MSG_RESULT([no])
+- fi
++ CAN_ENCODE="no"
++ ],[
++ AC_MSG_RESULT([cross compiling. guessing yes])
++ CAN_ENCODE="yes"
++ ])
+
+ ## Add "szip" to external filter list
+ if test "X$CAN_ENCODE" = "Xyes"; then
diff --minimal -Nru libhdf4-4.3.0/debian/patches/series
libhdf4-4.3.0/debian/patches/series
--- libhdf4-4.3.0/debian/patches/series 2024-04-09 20:42:02.000000000 +0200
+++ libhdf4-4.3.0/debian/patches/series 2025-05-31 17:49:16.000000000 +0200
@@ -1,3 +1,4 @@
enablesharedfortran.diff
reproducible-builds.patch
szlib.patch
+cross.patch
diff --minimal -Nru libhdf4-4.3.0/debian/rules libhdf4-4.3.0/debian/rules
--- libhdf4-4.3.0/debian/rules 2024-04-09 20:42:02.000000000 +0200
+++ libhdf4-4.3.0/debian/rules 2025-05-31 17:49:16.000000000 +0200
@@ -9,12 +9,11 @@
export DEB_BUILD_MAINT_OPTIONS=hardening=+all
include /usr/share/dpkg/architecture.mk
+include /usr/share/dpkg/buildtools.mk
include /usr/share/dpkg/pkg-info.mk
UPSTREAM_VERSION = $(shell echo $(DEB_VERSION_UPSTREAM) | sed -e 's/\+.*//')
-DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
-
RELEASE := $(UPSTREAM_VERSION)
PACKAGE := libhdf4
SOVER := 0
@@ -22,9 +21,6 @@
DESTDIR := $(CURDIR)/debian/tmp
DESTDIR_ALT := $(CURDIR)/debian/tmp-alt
-F77 := gfortran
-CC := gcc
-CXX := g++
LIBS := -ljpeg -lz -lm
export DEB_FFLAGS_MAINT_APPEND += -fallow-argument-mismatch
--- End Message ---
--- Begin Message ---
Source: libhdf4
Source-Version: 4.3.1-1~exp1
Done: Bas Couwenberg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libhdf4, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg <[email protected]> (supplier of updated libhdf4 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 01 Jul 2025 05:29:49 +0200
Source: libhdf4
Architecture: source
Version: 4.3.1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project <[email protected]>
Changed-By: Bas Couwenberg <[email protected]>
Closes: 1097195 1107056
Changes:
libhdf4 (4.3.1-1~exp1) experimental; urgency=medium
.
* Team upload.
* New upstream release.
(closes: #1097195)
* Bump Standards-Version to 4.7.2, no changes.
* Fix old FSF address in copyright file.
* Add get-orig-source script for upstream git snapshots.
* Drop -alt variant, it replaced the variant with netcdf & fortran support.
(closes: #1107056)
* Don't include .la file in -dev package.
* Remove generated files in clean target.
* Replace obsolete Breaks/Conflicts/Replaces.
* Drop obsolete patches.
Checksums-Sha1:
14bb004d643b75961f1ce67685a35114c61de394 2299 libhdf4_4.3.1-1~exp1.dsc
7ef99b3bedcc5cd365b33f57cbac1da364d28bb2 9328847 libhdf4_4.3.1.orig.tar.gz
73638e35b610a43a40f9decb17b8e19784c33752 36972
libhdf4_4.3.1-1~exp1.debian.tar.xz
fa3674716cf1500259bba40b936ad1ecfc7bb8ec 9386
libhdf4_4.3.1-1~exp1_amd64.buildinfo
Checksums-Sha256:
f70879f215ee77e1373115afaa3fefd30ada79087fcb999ab4b895b3d2ea8580 2299
libhdf4_4.3.1-1~exp1.dsc
6dc3b8af610526788bf78fb3982b25a80abfc94e37ce0c3ae2929b5e9c937093 9328847
libhdf4_4.3.1.orig.tar.gz
a91affac732d62a186b9f23dfcec1d60f685d1aa597a698d12814828fa85285a 36972
libhdf4_4.3.1-1~exp1.debian.tar.xz
8a2616ec998fb9f25a8c05901dbe6e774a26a08528be3607472e9761b2432eca 9386
libhdf4_4.3.1-1~exp1_amd64.buildinfo
Files:
2110de01ec208a92f900e6c4f03397da 2299 graphics optional
libhdf4_4.3.1-1~exp1.dsc
90106abf6d5bd6dcc3649cdfa1c8fad4 9328847 graphics optional
libhdf4_4.3.1.orig.tar.gz
f01ab0fc4a78ee9d98072d526b6e2663 36972 graphics optional
libhdf4_4.3.1-1~exp1.debian.tar.xz
636cf6b3216382282f0e49b15a1b5405 9386 graphics optional
libhdf4_4.3.1-1~exp1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmhjVy4ACgkQZ1DxCuiN
SvGIEA/7Bf+EKGdOmzzpXp+8xyz1SmmkAgIz96ejzng2ScQD8Fud3ALE9N9NH8aa
CZOEPycy/mkn18ffQKVinyDGNNFuzlffdIH/3S3mzZo5J7HTbt4Ub1PDnmaNO5O4
ZeutWmm42lAPzNjjuS+QTiaRS+uEV6cObuYYYvO+S7l3lQRx1GhQ00zLrCDleBUU
0xIdPLoJuWixRntGcpaUhxJupYQtdOBUVdtG1Ff64QCLoP1ud1roLvNOeHKDAh2M
WEhlU+vQsDk3SpvMnqlhb/XmL+LC/zy5CooUO7sTfmcvvOVUKtThMw2S3qg+4p6r
ex1KJ5sXpABTY8CjZZwNEi0MGtYZ47PR6wQigV7Uu2ozaD2+J88SYUv00VZCVQyJ
T7Cc2GmH1dD/gPE7gKaW/D/s0hzmVqF2XcSwg9xJmdFyoEKoREB6fhFREnYeqdqK
9Al2Q8GfNjQAgI8PR+aEF86yHmPs7S6TXKpFAgRI57UAQylTorH8iqH2K/nZ0Sm+
eT/Cz1kZjflhVMXIRatrNqJBJ5NpgCOP6PM6C7keBjUVcmPSV7ISx9HLhwPyWxcv
wY6TAFOflJGiV0M+agheKDtKDvmd50yTAbqn76oo34s74l7tTFnZ0dMi6V/+s/Pu
DF62x/YECSJObFZ+HaPhN5CW4iE6L6tfS4VYryjXpDUvnA0ItXM=
=Bdtq
-----END PGP SIGNATURE-----
pgp4WIkE73bJT.pgp
Description: PGP signature
--- End Message ---
