Bug#798221: gnugk: build logs do not show compiler command-line

[Jan Willamowius]

Hi,

the silent build is cause by the Makefile of PTLib that H323Plus and in
turn GnuGk includes.

You can make the build show the command line if update the build script
to call "VERBOSE=1 make" instead of make.

Also, GnuGk doesn't use a C++ Mysql lib. It only uses the C
client header.

Actually, the gnugk executable doesn't depend on any of the database
libraries: The headers are needed in the compile, but the libraries are
loaded dynamically at runtime, so one doesn't need to install all
database libraries, just the one the user wants to use.

Regards,
Jan

-- 
Jan Willamowius, Founder of the GNU Gatekeeper Project
EMail  : jan at willamowius.de
Website: http://www.gnugk.org
Support: http://www.willamowius.com/gnugk-support.html

Relaxed Communications GmbH
Frahmredder 91
22393 Hamburg
Geschäftsführer: Jan Willamowius
HRB 125261 (Amtsgericht Hamburg)
USt-IdNr: DE286003584


Simon McVittie wrote:
> Package: gnugk
> Version: 2:3.6-1
> Severity: normal
> 
> While investigating why gnugk, gnuift and opennebula have Build-Depends
> on libmysql++-dev but no Depends on libmysql++3, I noticed that gnugk
> is built with "silent rules":
> 
> [CC] singleton.cxx
> Processing file manual.sgml
> [CC] job.cxx
> make[3]: Leaving directory '/«PKGBUILDDIR»/docs/manual'
> [CC] yasocket.cxx
> [CC] h323util.cxx
> [CC] Toolkit.cxx
> 
> This makes it impossible to get useful QA information from buildd
> logs such as:
> <https://buildd.debian.org/status/fetch.php?pkg=gnugk&arch=amd64&ver=2%3A3.6-1%2Bb1&stamp=1441323361>
> 
> Please make the log show compiler command-lines. For CMake projects,
> you can usually do this by passing -DCMAKE_VERBOSE_MAKEFILE=TRUE
> to cmake (or by passing that to dh_auto_configure after the "--" token),
> or by passing VERBOSE=1 to make.
> 
>     S
> 
>