Bug#790349: bs1770gain: Fail to build when clock_t is not long int

2015-06-28 Thread Petter Reinholdtsen
Package: bs1770gain Version: 0.4.5-1 Severity: wishlist Tags: patch I noticed a build failure on the non-official x32 architecture, build log available from URL: http://buildd.debian-ports.org/status/fetch.php?pkg=bs1770gainarch=x32ver=0.4.5-1stamp=1435292575 . The build fail like this:

Bug#790349: bs1770gain: Fail to build when clock_t is not long int

2015-06-28 Thread Peter Belkner
Many thanks. On 28.06.2015 13:23, Petter Reinholdtsen wrote: Based on the information available from URL: http://stackoverflow.com/questions/1083142/what-s-the-correct-way-to-use-printf-to-print-a-clock-t , refering to URL:

Bug#790349: bs1770gain: Fail to build when clock_t is not long int

2015-06-28 Thread Fabian Greffrath
Am Sonntag, den 28.06.2015, 13:23 +0200 schrieb Petter Reinholdtsen: bs1770gain.c: In function 'main': bs1770gain.c:647:5: error: format '%ld' expects argument of type 'long int', but argument 3 has type 'clock_t' [-Werror=format=] fprintf(stderr, Duration: %ld ms.\n,(t2

Bug#790349: bs1770gain: Fail to build when clock_t is not long int

2015-06-28 Thread Petter Reinholdtsen
[Fabian Greffrath] Again, this issue isn't *so* severe that it would justify a FTBFS. I don't understand why you do not simply strip -Werror off the CFLAGS? It is a question of code quality. For some of us, ensuring the code build without any warning is a mean to raise the quality of the code.