On Tue, 29 Oct 2024 at 14:52:17 +0100, Dennis van Dok wrote:
> https://buildd.debian.org/status/fetch.php?pkg=lcmaps&arch=amd64&ver=1.6.6-3.1%2Bb2&stamp=1730151515&file=log
>
> libtool sets [_FILE_OFFSET_BITS] to an empty string. What I think was supposed
> to happen is not defining this at all; leaving it empty makes the expression
> syntax
> invalid.
libtool is not choosing to set this to an empty string: some higher-level
component (perhaps Autoconf or Automake or the package-specific build
system) is asking libtool to set _FILE_OFFSET_BITS empty (by giving it the
command-line option "-D_FILE_OFFSET_BITS="), and libtool is obediently
passing on that option to gcc.
I recently uploaded dbus_1.14.10-6 which is another
autoconf/automake/libtool package, and that built successfully on all
release and -ports architectures (except for alpha and hppa where it has
not been tried yet), so it seems like this is not a completely general
problem with autoconf/automake/libtool or with dpkg-buildflags.
I would suggest looking for the root cause in some higher-level component
or in the lcmaps package itself.
smcv
