Hi Markus,
Thanks for your reaction.
>I have just rebuilt freeciv 2.4.3 in a clean cowbuilder chroot on
>amd64 and I have got no error message.
> Are you sure that you didn't change anything else in debian/rules or
> elsewhere?
To be asolutely sure, I have just rebuilt freeciv, using freshly
downloaded source packages, in a fresh directory, and I got the same
results. If you are interested, I can send you the full build log, or
just the output of configure if that's sufficient.
> The freeciv-qt binary is not built on my system.
One difference would be, that the clean cowbuilder chroot will not have
any qt development files installed, as they are not essential for
building anything at all, nor a build-dependency of freeciv, so there
will be no way the freeciv-qt binary *can* be built, even if there
were a strong urge to build it if possible...
It seems that currently, all clients are being requested:
-------------------------------------------------------------------
dh_auto_configure -- \
--cache-file=/tmp/freeciv/freeciv-2.4.3/config.cache \
--sysconfdir=/etc \
--prefix=/usr \
--datadir=\${prefix}/share/games \
--bindir=\${prefix}/games \
--enable-debug=no \
--enable-client=all \ <============
--with-ggz-server=no \
--with-ggz-client=no \
--enable-ipv6=yes \
--enable-sys-lua \
--disable-silent-rules
-------------------------------------------------------------------
Which presumably includes (would include) the qt client.
Apparently, the configure step does not fail if the qt client is
requested, and the qt headers etc. were not found...
Kind regards,
Rogier.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
