Your message dated Sat, 30 Aug 2025 10:05:17 +0000
with message-id <[email protected]>
and subject line Bug#1086592: fixed in libtool 2.5.4-5
has caused the Debian Bug report #1086592,
regarding libtool FTCBFS: unsatisfiable gfortran dependency
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.)
--
1086592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086592
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libtool
Version: 2.4.7-7
Tags: patch
User: [email protected]
Usertags: cross-satisfiability
libtool cannot be cross built from source, because its gfortran
dependency is not satisfiable. What is being requested here is a host
architecture fortran compiler running on the host architecture. As it
also depends on a C compiler (again for the host architecture) we arrive
at a conflict with the build architecture C compiler implied in
build-essential.
The matter is fairly old and dubbed "toolchain dependency cross
translation". After so many years, this has been solved in principle via
introducing -for-host packages to gcc. In essence, we now annotated
toolchain dependencies with a -for-build or -for-host suffix depending
what we use them for. So we just replace gfortran with
gfortran-for-host, right?
Unfortunately, no. When we pull a -for-host package, cross building will
work, because autotools prefixes host tools with a host triplet. Once
attempting a native build, autotools will not do so and thus failing to
find gfortran as gfortran-for-host only provides a triplet-prefixed name
for gfortran and autotools does not attempt to use it by that name. We
can fix this aspect by forcing a triplet-prefixed name.
So that's what I propose. Actually go for gfortran-for-host and use
<triplet>-gfortran even for native builds. What do you think?
Helmut
diff --minimal -Nru libtool-2.4.7/debian/changelog
libtool-2.4.7/debian/changelog
--- libtool-2.4.7/debian/changelog 2023-07-17 17:03:58.000000000 +0200
+++ libtool-2.4.7/debian/changelog 2024-10-31 17:47:25.000000000 +0100
@@ -1,3 +1,11 @@
+libtool (2.4.7-7.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: Use gfortran-for-host. (Closes: #-1)
+ + As a result gfortran must be triplet-prefixed even in native builds.
+
+ -- Helmut Grohne <[email protected]> Thu, 31 Oct 2024 17:47:25 +0100
+
libtool (2.4.7-7) unstable; urgency=medium
* Remove obsole Breaks: for oldstable , Provides: libltdl7-dev
diff --minimal -Nru libtool-2.4.7/debian/control libtool-2.4.7/debian/control
--- libtool-2.4.7/debian/control 2023-07-17 17:03:58.000000000 +0200
+++ libtool-2.4.7/debian/control 2024-10-31 17:47:13.000000000 +0100
@@ -1,7 +1,7 @@
Source: libtool
Build-Depends: debhelper-compat (= 13),
file,
- gfortran | fortran95-compiler,
+ gfortran-for-host | fortran95-compiler,
automake (>= 1:1.14.1-3),
autoconf (>= 2.69-7),
help2man,
diff --minimal -Nru libtool-2.4.7/debian/rules libtool-2.4.7/debian/rules
--- libtool-2.4.7/debian/rules 2023-07-17 17:03:58.000000000 +0200
+++ libtool-2.4.7/debian/rules 2024-10-31 17:47:25.000000000 +0100
@@ -15,6 +15,12 @@
include /usr/share/dpkg/buildflags.mk
include /usr/share/dpkg/pkg-info.mk
+# Always use triplet-prefixed tools with gfortran-for-host.
+ifeq ($(origin FC),default)
+export FC := $(DEB_HOST_GNU_TYPE)-gfortran
+endif
+export F77 ?= $(FC)
+
# libltdl needs to conform to policy
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
INSTALL_PROGRAM += -s
--- End Message ---
--- Begin Message ---
Source: libtool
Source-Version: 2.5.4-5
Done: Alastair McKinstry <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libtool, 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.
Alastair McKinstry <[email protected]> (supplier of updated libtool 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: Sat, 30 Aug 2025 10:36:25 +0100
Source: libtool
Architecture: source
Version: 2.5.4-5
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry <[email protected]>
Changed-By: Alastair McKinstry <[email protected]>
Closes: 982873 1048097 1086592
Changes:
libtool (2.5.4-5) unstable; urgency=medium
.
[ Alastair McKinstry ]
* Clean more autogenerated files for repeated builds. Closes: #1048097
* Drop Suggests: gck-jdk. Closes: #982873
.
[ Helmut Grohe ]
* Fix FTCBFS: Use gfortran-for-host. (Closes: #1086592)
As a result gfortran must be triplet-prefixed even in native builds.
Checksums-Sha1:
b402b6346bded7b3e21147ba819575da2f71d48e 2240 libtool_2.5.4-5.dsc
1e932765ea54b6d81ee013590f3d0ec5a02a2b79 37704 libtool_2.5.4-5.debian.tar.xz
Checksums-Sha256:
ecf5fee3409acad48933f6790e2efa9918057f306b0cd66fc5b082abde4e88ba 2240
libtool_2.5.4-5.dsc
292129751c8af28b8c05e4854cf58dd67f88a926cb5bb1bb0ceb6b2c61c89a1e 37704
libtool_2.5.4-5.debian.tar.xz
Files:
bd6964ba98fc1d526a7dffeb391c92ec 2240 devel optional libtool_2.5.4-5.dsc
3404cdb85a7823a4ce536c356c4b3622 37704 devel optional
libtool_2.5.4-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmiyyg8ACgkQy+a7Tl2a
06UJ8A/+Mwz19OPG+yuQLRlRp1AX5XzCYod7ry3WzogJ1Hmvu9z6hOnik47ivHAi
bL9EQduHqI/m5Q2ih4lwLvhNzF2KQw2/zWxJK+04RM242RPxkJiE4YwqLPfh73YQ
zlRlSrWxIQOUUo/tgGUDmJz6EHUHYRQKKCrQn66GAhgCIFrYZEO4KDEdoLGPoNQM
Q/2zLAvVl7txUiHyb/7t5Hv3/LuqmJUZTvnEN0Mnd8Lv3X0L7GbO/8VFKyc5Lbmz
f5fEFTWOf9IDXNNSJaK3efkUJou9VXi+fw2bYqkslhK2hWqAtez3arvr6Tdwx6hB
apd1UtT07CzAXZqvc7UcrRWGWop0PL1NzC3eQzcMi9q/beWpUTwDd//x1Pkoj1jI
TDyW5JvqSN7ZfFR3M3/FMyYODP3YiXTJzz9EhzqtvyQahTDB9rwHb84jRMy4Ye5T
oGURm6qnDkZNvwWWrkNikgYjWDFewnPrCgq1Cvuc9QEFUvDqZDow5fxzC75mAcyC
epQ3/QruZIaR1BR1qtfI/YDKNEdnWzE1UlpfaTzWAIDOX7KfsAba9/umlzOY7747
LAvhniSlLppRCqrwCqKa1J+8BkvJv9YSW7gEylsQKu3bt9SrE57eIrtyjgrl6GkU
2ODF9gcJd9apu7MXrZJJOngfQyHIQvlUspG0ad5KQDyLqnCRlWA=
=UQ5x
-----END PGP SIGNATURE-----
pgp1sgOhvpG__.pgp
Description: PGP signature
--- End Message ---
