Bug#717825: please allow ghostscript to cross build

2013-07-25 Thread Matthias Klose
Package: ghostscript
Version: 9.05~dfsg-6.3
Severity: wishlist
User: debian-cr...@lists.debian.org
Usertags: cross-build
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

Please allow ghostscript to cross build. There are unfortunately many packages
having ghostscript in their build dependencies, not in their indep build
dependencies.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51f12236.4010...@ubuntu.com



Bug#717826: ghostscript ftbfs on arm64

2013-07-25 Thread Matthias Klose
Package: ghostscript
Version: 9.05~dfsg-6.3
Severity: normal
User: debian-...@lists.debian.org
Usertags: arm64
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch

Currently ftbfs on arm64, the symbols files needing an update. patch attached.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51f123a1.3000...@ubuntu.com



Bug#717827: ghostscript: please provide a staged build for ghostscript

2013-07-25 Thread Matthias Klose
Package: ghostscript
Version: 9.05~dfsg-6.3
Severity: wishlist
User: debian-cr...@lists.debian.org
Usertags: staged-build
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch

ghostscript would benefit from a staged build (DEB_STAGE=stage1), eliminating
the cyclic dependency with cups. This should set the dependencies right, and not
build ghostscript-cups.

Also please consider not to run the license check for stage1 builds, or maybe
disable it for arch any only builds.  I did stop it after two hours waiting on a
slow platform ...


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51f1249d.5040...@ubuntu.com



Bug#717826: Acknowledgement (ghostscript ftbfs on arm64)

2013-07-25 Thread Matthias Klose

diff -Nru ghostscript-9.07~dfsg2/debian/changelog 
ghostscript-9.07~dfsg2/debian/changelog
--- ghostscript-9.07~dfsg2/debian/changelog 2013-04-01 13:59:13.0 
+0200
+++ ghostscript-9.07~dfsg2/debian/changelog 2013-07-25 15:04:58.0 
+0200
@@ -1,3 +1,9 @@
+ghostscript (9.07~dfsg2-0ubuntu4) saucy; urgency=low
+
+  * Adjust symbols file for Aarch64.
+
+ -- Matthias Klose   Wed, 24 Jul 2013 23:17:37 +0200
+
 ghostscript (9.07~dfsg2-0ubuntu3) raring; urgency=low
 
   * 
debian/patches/020130401-852e545-pxl-xl-driver-produced-drawing-commands-without-setting-color-space.patch:
diff -Nru ghostscript-9.07~dfsg2/debian/libgs__VER__.symbols.in 
ghostscript-9.07~dfsg2/debian/libgs__VER__.symbols.in
--- ghostscript-9.07~dfsg2/debian/libgs__VER__.symbols.in   2012-06-06 
21:17:18.0 +0200
+++ ghostscript-9.07~dfsg2/debian/libgs__VER__.symbols.in   2013-07-25 
01:18:37.0 +0200
@@ -1,5 +1,5 @@
 libgs.so.__VER__ libgs__VER__ #MINVER#
 #include "symbols.common"
 (arch=linux-any)#include "symbols.common_linux"
-(arch=!any-alpha !any-amd64 !any-ia64 !any-ppc64 !any-s390x 
!any-sparc64)#include "symbols.common_32bit"
-(arch=any-alpha any-amd64 any-armel any-i386 any-ia64 any-mipsel any-sh3 
any-sh4)#include "symbols.common_le"
+(arch=!any-alpha !any-amd64 !any-arm64 !any-ia64 !any-ppc64 !any-s390x 
!any-sparc64)#include "symbols.common_32bit"
+(arch=any-alpha any-amd64 any-armel any-arm64 any-i386 any-ia64 any-mipsel 
any-sh3 any-sh4)#include "symbols.common_le"


Bug#793223: brlaser: change of type in system_error might break with GCC-5

2015-07-22 Thread Matthias Klose
Package: src:brlaser
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: gcc-pr66145

GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed
upstream in time for the GCC defaults change.  The work around is to
rebuild the affected packages after GCC 5 is the default compiler.
Please look at the code and decide, if the package is affected. If
not, please just close the issue.  If it's a real issue, I'll add
the packages affected to libstdc++6's Breaks attributes, with the
version of the package at the time of the defaults change.

See 
https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29
for further information.

To build with GCC 5,install the gcc, g++, gfortran, ... packages
from experimental (apt-get -t experimental install g++).


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1zhu91-9b...@paradis.debian.org



Bug#813043: please multiarchify the libhpmud library packages

2016-01-28 Thread Matthias Klose

Package: src:hplip
Version: 3.15.11+repack0-1
Tags: patch
User: d...@debian.org
Usertags: multiarch

patch at
http://launchpadlibrarian.net/235584730/hplip_3.15.11+repack0-1_3.15.11+repack0-1ubuntu1.diff.gz



Bug#770266: libgs9: please convert to multiarch

2016-09-17 Thread Matthias Klose
On 17.09.2016 16:08, Jonas Smedegaard wrote:
> i Till (and others),
> 
> Quoting Till Kamppeter (2016-09-17 00:50:45)
>> I have now re-applied multi-arch to Ubuntu's Ghostscript package which 
>> is nearly identical to Debian's current Ghostscript package. So I 
>> attach the debdiff and hope with this you will easily able to add 
>> multi-arch functionality to Debian's Ghostscript package.
>>
>> I am very grateful if you apply this so that I can keep the delta 
>> between Debian's and Ubuntu's Ghostscript packages low.
> 
> Thanks for the suggested patch.
> 
> I am worried, however, about the following phrase at 
> https://wiki.debian.org/Multiarch/Implementation:
> 
>> If your -dev package contains headers which vary across architectures 
>> then it cannot be marked as Multi-Arch: same until a policy decision 
>> is made about architecture-dependant headers and the toolchain is 
>> updated.
> 
> Did you test that the multi-arch packages work in a multi-arch 
> environment?  Looking at the symbols file, it seems headers do vary.

The encoding of symbols has nothing to do with the header files, I also can't
see any generated header files which differ on different architectures.  If the
latter should be the cause, these surely can be moved into the multiarch include
directory.



Bug#912847: ghostscript ftbfs on amd64, not installable, breaking many binary-all builds

2018-11-04 Thread Matthias Klose
Package: src:ghostscript
Version: 9.25~dfsg-6
Severity: serious
Tags: sid buster

ghostscript ftbfs on amd64, not installable, breaking many binary-all builds

https://buildd.debian.org/status/fetch.php?pkg=ghostscript&arch=amd64&ver=9.25~dfsg-6&stamp=1541195477&raw=0


make[4]: Entering directory '/<>'
make[4]: 'soobj/aux/genarch' is up to date.
make[4]: Leaving directory '/<>'
/usr/bin/make -f Makefile GS_DOT_O= REALMAIN_OBJ= GS_XE=./sobin/libgs.so.9.25
GPCL_XE=./sobin/libno_gpcl6.so.9.25 GXPS_XE=./sobin/libno_gxps.so.9.25
GPDL_XE=./sobin/libno_gpdl.so.9.25 DISPLAY_DEV=./soobj/display.dev
STDIO_IMPLEMENTATION=c BUILDDIRPREFIX=so GENOPT='' GS_LDFLAGS='-Wl,-z,relro
-shared -Wl,-soname=libgs.so.9'\
 PCL_LDFLAGS='-Wl,-z,relro   -shared -Wl,-soname=libno_gpcl6.so.9'
XPS_LDFLAGS='-Wl,-z,relro   -shared -Wl,-soname=libno_gxps.so.9' \
 PDL_LDFLAGS='-Wl,-z,relro   -shared -Wl,-soname=libno_gpdl.so.9'
CFLAGS='-fPIC  -O2 -fPIC \
 -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wstrict-prototypes -Wundef
-Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -fno-strict-aliasing
-Werror=declaration-after-statement -fno-builtin -fno-common -Werror=return-type
-DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1
-DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1
-DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1  -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -DHAVE_RESTRICT=1 -DUSE_LIBPAPER
-I/usr/include/x86_64-linux-gnu  -fno-strict-aliasing -DHAVE_POPEN_PROTO=1
-DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/lib/ghostscript/9.25\" ' 
prefix=/usr
make[4]: Entering directory '/<>'
make[4]: Leaving directory '/<>'
/usr/bin/make -f Makefile DISPLAY_DEV=./soobj/display.dev STDIO_IMPLEMENTATION=c
BUILDDIRPREFIX=so GENOPT='' LDFLAGS='-Wl,-z,relro  '\
 CFLAGS='-fPIC  -O2 -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wstrict-prototypes
-Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings
-fno-strict-aliasing -Werror=declaration-after-statement -fno-builtin
-fno-common -Werror=return-type -DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1
-DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_LIBDL=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1  -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -DHAVE_RESTRICT=1 -DUSE_LIBPAPER
-I/usr/include/x86_64-linux-gnu  -fno-strict-aliasing -DHAVE_POPEN_PROTO=1
-DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/lib/ghostscript/9.25\" ' 
prefix=/usr\
 ./sobin/gsc ./sobin/gsx -so-loader -so-loader -so-loader
make[4]: Entering directory '/<>'
/usr/bin/ld: ./soobj/dxmainc.o: file not recognized: file truncated
collect2: error: ld returned 1 exit status
make[4]: *** [base/unix-dll.mak:178: sobin/gsx] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>'
make[3]: *** [base/unix-dll.mak:296: so-subtarget] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [base/unix-dll.mak:301: install-so] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [base/unix-dll.mak:327: soinstall] Error 2
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:103:
debian/stamp-makefile-install] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2



Bug#925663: cups-bjnp: ftbfs with GCC-9

2019-03-27 Thread Matthias Klose
Package: src:cups-bjnp
Version: 2.0.1-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/cups-bjnp_2.0.1-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
checking for netinet/in.h... (cached) yes
checking for arpa/nameser.h... yes
checking for netdb.h... (cached) yes
checking for resolv.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make[1]: Leaving directory '/<>'
   dh_auto_build -a
make -j4
make[1]: Entering directory '/<>'
make  all-am
make[2]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp.o `test -f 'bjnp.c' || echo './'`bjnp.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-runloop.o `test -f 'bjnp-runloop.c' || 
echo './'`bjnp-runloop.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-io.o `test -f 'bjnp-io.c' || echo 
'./'`bjnp-io.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-debug.o `test -f 'bjnp-debug.c' || echo 
'./'`bjnp-debug.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-utils.o `test -f 'bjnp-utils.c' || echo 
'./'`bjnp-utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-discover.o `test -f 'bjnp-discover.c' 
|| echo './'`bjnp-discover.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-commands.o `test -f 'bjnp-commands.c' 
|| echo './'`bjnp-commands.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-levels.o `test -f 'bjnp-levels.c' || 
echo './'`bjnp-levels.c
In file included from /usr/include/string.h:494,
 from /usr/include/cups/http.h:25,
 from /usr/include/cups/ipp.h:23,
 from /usr/include/cups/cups.h:32,
 from bjnp.h:22,
 from bjnp-commands.c:21:
In function 'strncpy',
inlined from 'bjnp_set_command_header' at bjnp-commands.c:40:5,
inlined from 'bjnp_defaults_set_command_header' at bjnp-commands.c:52:5,
inlined from 'get_printer_id' at bjnp-commands.c:155:5:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: 
'__builtin_strncpy' output truncated before terminating nul copying 4 bytes 
from a string of the same length [-Werror=stringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^

Bug#938631: tea4cups: Python2 removal in sid/bullseye

2019-08-30 Thread Matthias Klose
Package: src:tea4cups
Version: 3.14~alpha0+svn3576-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:tea4cups

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.



Bug#957061: c2esp: ftbfs with GCC-10

2020-04-17 Thread Matthias Klose
Package: src:c2esp
Version: 27-6
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/c2esp_27-6_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
configure: *
configure: *** Any missing dependencies are listed below ***
configure: cups version is 1.6 or later - OK
configure: *
configure: LIBS=-ljbig -lz -lcupsfilters -lcups 
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating doc/Makefile
config.status: creating scripts/Makefile
config.status: creating ppd/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
   dh_auto_build
make -j4
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 --pedantic -Wall 
-std=c99 -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o c2esp.o c2esp.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 --pedantic -Wall 
-std=c99 -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o c2espcommon.o 
c2espcommon.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 --pedantic -Wall 
-std=c99 -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o c2espC.o 
c2espC.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 --pedantic -Wall 
-std=c99 -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o command2esp.o 
command2esp.c
c2esp.c: In function ‘output_jbig’:
c2esp.c:405:5: warning: variable ‘rc’ set but not used 
[-Wunused-but-set-variable]
  405 | int rc;
  | ^~
c2esp.c: In function ‘main’:
c2esp.c:1041:4: warning: ‘ppdOpenFile’ is deprecated: Use cupsCopyDestInfo and 
friends instead. [-Wdeprecated-declarations]
 1041 |ppd = ppdOpenFile(getenv("PPD"));
  |^~~
In file included from /usr/include/cupsfilters/driver.h:28,
 from c2esp.c:46:
/usr/include/cups/ppd.h:389:20: note: declared here
  389 | extern ppd_file_t *ppdOpenFile(const char *filename) 
_CUPS_DEPRECATED_1_6_MSG("Use cupsCopyDestInfo and friends instead.");
  |^~~
c2esp.c:1047:3: warning: ‘ppdClose’ is deprecated: Use cupsCopyDestInfo and 
friends instead. [-Wdeprecated-declarations]
 1047 |   ppdClose(ppd);
  |   ^~~~
In file included from /usr/include/cupsfilters/driver.h:28,
 from c2esp.c:46:
/usr/include/cups/ppd.h:364:14: note: declared here
  364 | extern void  ppdClose(ppd_file_t *ppd) _CUPS_DEPRECATED_1_6_MSG("Use 
cupsCopyDestInfo and friends instead.");
  |  ^~~~
gcc --pedantic -Wall -std=c99 -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,--as-needed -o command2esp command2esp.o c2espcommon.o  -ljbig -lz 
-lcupsfilters -lcups 
/usr/bin/ld: c2espcommon.o:./src/c2espcommon.c:45: multiple definition of 
`DoBack'; command2esp.o:./src/command2esp.c:66: first defined here
/usr/bin/ld: c2espcommon.o:./src/c2espcommon.c:49: multiple definition of 
`StartTime'; command2esp.o:./src/command2esp.c:61: first defined here
/usr/bin/ld: c2espcommon.o:./src/c2espcommon.h:38: multiple definition of 
`BackBuf'; command2esp.o:./src/c2espcommon.h:38: first defined here
/usr/bin/ld: c2espcommon.o:./src/c2espcommon.h:39: multiple definition of 
`BlackPercent'; command2esp.o:./src/c2espcommon.h:39: first defined here
/usr/bin/ld: c2espcommon.o:./src/c2espcommon.h:39: multiple definition of 
`ColourPercent'; command2esp.o:./src/c2espcommon

Bug#957695: pnm2ppa: ftbfs with GCC-10

2020-04-17 Thread Matthias Klose
Package: src:pnm2ppa
Version: 1.13-9
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/pnm2ppa_1.13-9_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
 from ../pnm2ppa.c:24:
In function ‘strncpy’,
inlined from ‘main’ at ../pnm2ppa.c:872:5:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
In function ‘strncpy’,
inlined from ‘main’ at ../pnm2ppa.c:848:5:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
In function ‘strncpy’,
inlined from ‘main’ at ../pnm2ppa.c:821:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
gcc -DHAVE_CONFIG_H -I. -I..  -DSYSCONFDIR='"/etc"' -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DLANG_ENG -Wall 
-Wall -Wsign-compare -Wfloat-equal -Wformat-security -g -O2 -DNDEBUG -c -o 
cutswath.o ../cutswath.c
../cutswath.c: In function ‘ppa_print_page’:
../cutswath.c:465:28: warning: comparison of integer expressions of different 
signedness: ‘int’ and ‘enum ’ [-Wsign-compare]
  465 |  if (!gUnimode && last_dir == prev->direction){
  |^~
../cutswath.c:505:28: warning: comparison of integer expressions of different 
signedness: ‘int’ and ‘enum ’ [-Wsign-compare]
  505 |  if (!gUnimode && last_dir == prev->direction){
  |^~
../cutswath.c:541:31: warning: comparison of integer expressions of different 
signedness: ‘int’ and ‘enum ’ [-Wsign-compare]
  541 | if (!gUnimode && last_dir == prev->direction){
  |   ^~
../cutswath.c: In function ‘read_black_image’:
../cutswath.c:780:34: warning: variable ‘after_color’ set but not used 
[-Wunused-but-set-variable]
  780 |   BOOLEAN  got_nonblank = false, after_color = false, ignore_color = 
false;
  |  ^~~
../cutswath.c: In function ‘r2l_black_sweep’:
../cutswath.c:1080:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 1080 |   int i, j , width, evenlines, oddlines;
  |^~~~
../cutswath.c: In function ‘l2r_black_sweep’:
../cutswath.c:1219:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 1219 |   int i, j , width, evenlines, oddlines;
  |^~~~
../cutswath.c: In function ‘l2r_color_sweep’:
../cutswath.c:1931:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 1931 |   int i, j , width, evenlines, oddlines;
  |^~~~
../cutswath.c: In function ‘r2l_color_sweep’:
../cutswath.c:2154:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 2154 |   int i, j , width, evenlines, oddlines;
  |^~~~
gcc -DHAVE_CONFIG_H -I. -I..  -DSYSCONFDIR='"/etc"' -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DLANG_ENG -Wall 
-Wall -Wsign-compare -Wfloat-equal -Wformat-se

Bug#957716: ptouch-driver: ftbfs with GCC-10

2020-04-17 Thread Matthias Klose
Package: src:ptouch-driver
Version: 1.4.2-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ptouch-driver_1.4.2-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
configure: WARNING: unrecognized options: --disable-maintainer-mode
make[1]: Leaving directory '/<>'
   dh_auto_build -O--parallel
make -j4
make[1]: Entering directory '/<>'
make  all-am
make[2]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I.  -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o rastertoptch-rastertoptch.o `test -f 
'rastertoptch.c' || echo './'`rastertoptch.c
rastertoptch.c: In function ‘parse_options’:
rastertoptch.c:482:3: warning: ‘ppdOpenFile’ is deprecated: Use 
cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
  482 |   ppd = ppdOpenFile(getenv("PPD"));
  |   ^~~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:389:20: note: declared here
  389 | extern ppd_file_t *ppdOpenFile(const char *filename) 
_CUPS_DEPRECATED_1_6_MSG("Use cupsCopyDestInfo and friends instead.");
  |^~~
rastertoptch.c:489:5: warning: ‘ppdLastError’ is deprecated: Use 
cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
  489 | status = ppdLastError(&linenum);
  | ^~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:403:21: note: declared here
  403 | extern ppd_status_t ppdLastError(int *line) 
_CUPS_DEPRECATED_1_6_MSG("Use cupsCopyDestInfo and friends instead.");
  | ^~~~
rastertoptch.c:491:5: warning: ‘ppdErrorString’ is deprecated: Use 
cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
  491 | fprintf(stderr, "DEBUG: %s on line %d.\n", ppdErrorString(status), 
linenum);
  | ^~~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:398:20: note: declared here
  398 | extern const char *ppdErrorString(ppd_status_t status) 
_CUPS_DEPRECATED_1_6_MSG("Use cupsCopyDestInfo and friends instead.");
  |^~
rastertoptch.c:495:3: warning: ‘ppdMarkDefaults’ is deprecated: Use 
cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
  495 |   ppdMarkDefaults(ppd);
  |   ^~~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:384:14: note: declared here
  384 | extern void  ppdMarkDefaults(ppd_file_t *ppd) 
_CUPS_DEPRECATED_1_6_MSG("Use cupsCopyDestInfo and friends instead.");
  |  ^~~
rastertoptch.c:496:3: warning: ‘cupsMarkOptions’ is deprecated: Use 
cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
  496 |   cupsMarkOptions(ppd, num_options, cups_options);
  |   ^~~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:362:13: note: declared here
  362 | extern int  cupsMarkOptions(ppd_file_t *ppd, int num_options, 
cups_option_t *options) _CUPS_DEPRECATED_1_6_MSG("Use cupsCopyDestInfo and 
friends instead.");
  | ^~~
rastertoptch.c:499:5: warning: ‘ppdFindMarkedChoice’ is deprecated: Use 
cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
  499 | ppd_choice_t *choice = ppdFindMarkedChoice(ppd, "RollFedMedia");
  | ^~~~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:377:22: note: declared here
  377 | extern ppd_choice_t *ppdFindMarkedChoice(ppd_file_t *ppd,
  |  ^~~
rastertoptch.c:560:3: warning: ‘ppdClose’ is deprecated: Use cupsCopyDestInfo 
and friends instead. [-Wdeprecated-declarations]
  560 |   ppdClose(ppd);
  |   ^~~~
In file included from rastertoptch.c:315:
/usr/include/cups/ppd.h:364:14: note: declared here
  364 | extern void  ppdClose(ppd_file_t *ppd) _CUPS_DEPRECATED_1_

Bug#984045: dymo-cups-drivers: ftbfs with GCC-11

2021-03-03 Thread Matthias Klose
Package: src:dymo-cups-drivers
Version: 1.4.0-9
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/dymo-cups-drivers_1.4.0-9_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  |   ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
 from /usr/include/c++/11/deque:60,
 from /usr/include/cppunit/Message.h:11,
 from /usr/include/cppunit/Exception.h:5,
 from /usr/include/cppunit/TestCaller.h:4,
 from /usr/include/cppunit/extensions/HelperMacros.h:9,
 from TestLabelWriterLanguageMonitor.h:24,
 from TestLabelWriterLanguageMonitor.cpp:21:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum 
class std::byte’
  404 |   enum class byte : unsigned char;
  |  ^~~~
In file included from ../../common/PrinterDriver.h:24,
 from ../LabelWriterDriver.h:25,
 from TestLabelWriterLanguageMonitor.h:25,
 from TestLabelWriterLanguageMonitor.cpp:21:
../../common/CommonTypedefs.h:31:29: note: ‘typedef unsigned 
char DymoPrinterDriver::byte’
   31 | typedef unsigned char   byte;
  | ^~~~
TestLabelWriterLanguageMonitor.cpp:335:3: error: reference to ‘byte’ is 
ambiguous
  335 |   byte OutputPrinterData2[] =
  |   ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
 from /usr/include/c++/11/deque:60,
 from /usr/include/cppunit/Message.h:11,
 from /usr/include/cppunit/Exception.h:5,
 from /usr/include/cppunit/TestCaller.h:4,
 from /usr/include/cppunit/extensions/HelperMacros.h:9,
 from TestLabelWriterLanguageMonitor.h:24,
 from TestLabelWriterLanguageMonitor.cpp:21:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum 
class std::byte’
  404 |   enum class byte : unsigned char;
  |  ^~~~
In file included from ../../common/PrinterDriver.h:24,
 from ../LabelWriterDriver.h:25,
 from TestLabelWriterLanguageMonitor.h:25,
 from TestLabelWriterLanguageMonitor.cpp:21:
../../common/CommonTypedefs.h:31:29: note: ‘typedef unsigned 
char DymoPrinterDriver::byte’
   31 | typedef unsigned char   byte;
  | ^~~~
TestLabelWriterLanguageMonitor.cpp:340:25: error: ‘PrinterData’ was not 
declared in this scope; did you mean ‘PrinterData2’?
  340 |   buffer_t PrinterData2(PrinterData, PrinterData + sizeof(PrinterData));
  | ^~~
  | PrinterData2
In file included from /usr/include/cppunit/TestCase.h:6,
 from /usr/include/cppunit/TestCaller.h:5,
 from /usr/include/cppunit/extensions/HelperMacros.h:9,
 from TestLabelWriterLanguageMonitor.h:24,
 from TestLabelWriterLanguageMonitor.cpp:21:
TestLabelWriterLanguageMonitor.cpp:352:14: error: ‘OutputPrinterData1’ was not 
declared in this scope
  352 | buffer_t(OutputPrinterData1, OutputPrinterData1 + 
sizeof(OutputPrinterData1)),
  |  ^~
TestLabelWriterLanguageMonitor.cpp:366:14: error: ‘OutputPrinterData2’ was not 
declared in this scope; did you mean ‘PrinterData2’?
  366 | buffer_t(OutputPrinterData2, OutputPrinterData2 + 
sizeof(OutputPrinterData

Bug#1012908: cups-bjnp: ftbfs with GCC-12

2022-06-16 Thread Matthias Klose
Package: src:cups-bjnp
Version: 2.0.3-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/cups-bjnp_2.0.3-3_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking types of arguments for select... int,fd_set *,struct timeval *
checking for string.h... (cached) yes
checking for fcntl.h... yes
checking for arpa/inet.h... yes
checking for netdb.h... yes
checking for netinet/in.h... yes
checking for sys/socket.h... (cached) yes
checking for sys/time.h... yes
checking for sys/timeb.h... yes
checking for wchar.h... yes
checking for cups/cups.h... yes
checking for cups/backend.h... yes
checking for cups/http.h... yes
checking for sys/types.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for arpa/nameser.h... yes
checking for netdb.h... (cached) yes
checking for resolv.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
make  all-am
make[2]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp.o `test -f 'bjnp.c' || echo './'`bjnp.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-runloop.o `test -f 'bjnp-runloop.c' || 
echo './'`bjnp-runloop.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-io.o `test -f 'bjnp-io.c' || echo 
'./'`bjnp-io.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-debug.o `test -f 'bjnp-debug.c' || echo 
'./'`bjnp-debug.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-utils.o `test -f 'bjnp-utils.c' || echo 
'./'`bjnp-utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-discover.o `test -f 'bjnp-discover.c' 
|| echo './'`bjnp-discover.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-commands.o `test -f 'bjnp-commands.c' 
|| echo './'`bjnp-commands.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-levels.o `t

Bug#1012916: dymo-cups-drivers: ftbfs with GCC-12

2022-06-16 Thread Matthias Klose
Package: src:dymo-cups-drivers
Version: 1.4.0-11
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/dymo-cups-drivers_1.4.0-11_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  598 | operator<<(basic_ostream<_CharT, _Traits>& __out, const _CharT* __s)
  | ^~~~
/usr/include/c++/12/ostream:598:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   mismatched types ‘const 
_CharT*’ and ‘std::vector’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(basic_ostream<_CharT, _Traits>&, const char*)’
  302 | operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s)
  | ^~~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const std::vector’) to type ‘const char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:615:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const char*)’
  615 | operator<<(basic_ostream& __out, const char* __s)
  | ^~~~
/usr/include/c++/12/ostream:615:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const std::vector’) to type ‘const char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:628:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const signed char*)’
  628 | operator<<(basic_ostream& __out, const signed char* 
__s)
  | ^~~~
/usr/include/c++/12/ostream:628:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const std::vector’) to type ‘const signed char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:633:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const unsigned char*)’
  633 | operator<<(basic_ostream& __out, const unsigned 
char* __s)
  | ^~~~
/usr/include/c++/12/ostream:633:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const std::vector’) to type ‘const unsigned char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:754:5: note: candidate: ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&)’
  754 | operator<<(_Ostream&& __os, const _Tp& __x)
  | ^~~~
/usr/include/c++/12/ostream:754:5: note:   template argument 
deduction/substitution failed:
/usr/include/c++/12/ostream: In substitution of ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&) [with _Ostream = 
std::__cxx11::basic_ostringstream&; _Tp = std::vector]’:
/usr/include/cppunit/tools/StringHelper.h:25:9:   required from ‘typename 
std::enable_if<(! std::is_enum<_Tp>::value), std::__cxx11::basic_string 
>::type CppUnit::StringHelper::toString(const T&) [with T = 
std::vector; typename std::enable_if<(! 
std::is_enum<_Tp>::value), std::__cxx11::basic_string >::type = 
std::__cxx11::basic_string]’
/usr/include/cppunit/TestAssert.h:74:50:   required from ‘static std::string 
CppUnit::assertion_traits::toString(const T&) [with T = std::vector; std::string = std::__cxx11::basic_string]’
/usr/include/cppunit/TestAssert.h:168:58:   required from ‘void 
CppUnit::assertEqua

Bug#1015378: cups-bjnp: ftbfs with LTO (link time optimization) enabled

2022-07-19 Thread Matthias Klose
Package: src:cups-bjnp
Version: 2.0.3-3
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/cups-bjnp_2.0.3-3_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
checking for sys/time.h... yes
checking for sys/timeb.h... yes
checking for wchar.h... yes
checking for cups/cups.h... yes
checking for cups/backend.h... yes
checking for cups/http.h... yes
checking for sys/types.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for arpa/nameser.h... yes
checking for netdb.h... (cached) yes
checking for resolv.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
make  all-am
make[2]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp.o 
`test -f 'bjnp.c' || echo './'`bjnp.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
bjnp-bjnp-runloop.o `test -f 'bjnp-runloop.c' || echo './'`bjnp-runloop.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-io.o 
`test -f 'bjnp-io.c' || echo './'`bjnp-io.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
bjnp-bjnp-debug.o `test -f 'bjnp-debug.c' || echo './'`bjnp-debug.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
bjnp-bjnp-utils.o `test -f 'bjnp-utils.c' || echo './'`bjnp-utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
bjnp-bjnp-discover.o `test -f 'bjnp-discover.c' || echo './'`bjnp-discover.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
bjnp-bjnp-commands.o `test -f 'bjnp-commands.c' || echo './'`bjnp-commands.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
bjnp-bjnp-levels.o `test -f 'bjnp-levels.c' || echo './'`bjnp-levels.c
gcc -Wall  -Werror  -g -O2 -ffile-prefix-map=/<>=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security  
-flto=auto -ffat-lto-objects -Wl,-z,relro -o bjnp bjnp-bjnp.o 
bjnp-bjnp-runloop.o bjnp-bjnp-io.o bjnp-bjnp-debug.o bjnp-bjnp-utils.o 
bjnp-bjnp-discover.o bjnp-bjnp-commands.o bjnp-bjnp-levels.o -lcups 
In function ‘bjnp_backendGetDeviceID’,
inlined from ‘bjnp_backendRunLoop’ at bjnp-runloop.c:256:29,
inlined from ‘main’ at bjnp.c:394:18:
bjnp-io.c:505:31: error: writing 1 byte into 

Bug#1037613: cups-bjnp: ftbfs with GCC-13

2023-06-14 Thread Matthias Klose
Package: src:cups-bjnp
Version: 2.0.3-4
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/cups-bjnp_2.0.3-4_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking types of arguments for select... int,fd_set *,struct timeval *
checking for string.h... (cached) yes
checking for fcntl.h... yes
checking for arpa/inet.h... yes
checking for netdb.h... yes
checking for netinet/in.h... yes
checking for sys/socket.h... (cached) yes
checking for sys/time.h... yes
checking for sys/timeb.h... yes
checking for wchar.h... yes
checking for cups/cups.h... yes
checking for cups/backend.h... yes
checking for cups/http.h... yes
checking for sys/types.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for arpa/nameser.h... yes
checking for netdb.h... (cached) yes
checking for resolv.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
make  all-am
make[2]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp.o `test -f 'bjnp.c' || echo './'`bjnp.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-runloop.o `test -f 'bjnp-runloop.c' || 
echo './'`bjnp-runloop.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-io.o `test -f 'bjnp-io.c' || echo 
'./'`bjnp-io.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-debug.o `test -f 'bjnp-debug.c' || echo 
'./'`bjnp-debug.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-utils.o `test -f 'bjnp-utils.c' || echo 
'./'`bjnp-utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-discover.o `test -f 'bjnp-discover.c' 
|| echo './'`bjnp-discover.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-commands.o `test -f 'bjnp-commands.c' 
|| echo './'`bjnp-commands.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bjnp-bjnp-levels.o `test -f 'bjnp-levels.c' || 
echo './'`bjnp-levels.c
In function ‘strstrtok’,
inlined from ‘report_ink_status_messages’ at bjnp-levels.c:451:13,
inlined from ‘bjnp_report_levels’ at bjnp-levels.c:653:12:
bjnp-levels.c:307:14: error: storing the address of local variable ‘warnings’ 
in ‘next’ [-Werror=dangling-pointer=]
  307 | next = in;
  | ~^~~~
bjnp-levels.c: In funct

Bug#1074996: ghostscript: ftbfs with GCC-14

2024-07-03 Thread Matthias Klose
Package: src:ghostscript
Version: 10.03.1~dfsg-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/ghostscript_10.03.1~dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf_r6 -oper zpdf_r6
./soobj/aux/echogs -e .dev -w- -l-obj ./soobj/pdf -include ./soobj/psbase 
./soobj/dps2lib
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/dps2read 
./soobj/pdffonts ./soobj/psl3
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/psl2lib 
./soobj/pdfread
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/fmd5 ./soobj/fsha2
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/farc4 
./soobj/faes.dev
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/type2
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/pdfops
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/pdf_r6
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/cff
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -include ./soobj/ttfont
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -functiontype 4
./soobj/aux/echogs -e .dev -a-  ./soobj/pdf -emulator PDF
gcc  -DHAVE_MKSTEMP -DHAVE_FILE64 -DHAVE_FSEEKO -DHAVE_MKSTEMP64 
-DHAVE_FONTCONFIG -DHAVE_LIBIDN -DHAVE_SETLOCALE -DHAVE_SSE2  -DHAVE_BSWAP32 
-DHAVE_BYTESWAP_H -DHAVE_STRERROR -DHAVE_ISNAN -DHAVE_ISINF  
-DHAVE_PREAD_PWRITE=1 -DGS_RECURSIVE_MUTEXATTR=PTHREAD_MUTEX_RECURSIVE -O2 
-DNDEBUG -fPIC  -fvisibility=hidden 
-DGSDLLEXPORT="__attribute__((visibility(\"default\")))" -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations 
-Wmissing-prototypes -Wwrite-strings -fno-strict-aliasing 
-Werror=declaration-after-statement -fno-builtin -fno-common 
-Werror=return-type -Wno-unused-local-typedefs -DHAVE_STDINT_H=1 
-DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" 
-D__USE_UNIX98=1 -DHAVE_SNPRINTF  -DBUILD_PDF=1 -I./pdf -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
 -Werror=format-security -fcf-protection -DHAVE_RESTRICT=1  -DUSE_LIBPAPER 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp   -fno-strict-aliasing 
-DHAVE_POPEN_PROTO=1   -DSHARE_JPX=1 -I/usr/include/openjpeg-2.5  
-DUSE_OPENJPEG_JP2  -DPDF_INCLUDED -I./pdf -I./soobj -I./pcl/pl -I./base 
-Isrc/lib -I./jpegxr -Isrc -Isrc/src/lib/openjp2 -Isrc -c 
./pdf/pdf_loop_detect.c -o ./soobj/pdf_loop_detect.o
gcc  -DHAVE_MKSTEMP -DHAVE_FILE64 -DHAVE_FSEEKO -DHAVE_MKSTEMP64 
-DHAVE_FONTCONFIG -DHAVE_LIBIDN -DHAVE_SETLOCALE -DHAVE_SSE2  -DHAVE_BSWAP32 
-DHAVE_BYTESWAP_H -DHAVE_STRERROR -DHAVE_ISNAN -DHAVE_ISINF  
-DHAVE_PREAD_PWRITE=1 -DGS_RECURSIVE_MUTEXATTR=PTHREAD_MUTEX_RECURSIVE -O2 
-DNDEBUG -fPIC  -fvisibility=hidden 
-DGSDLLEXPORT="__attribute__((visibility(\"default\")))" -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations 
-Wmissing-prototypes -Wwrite-strings -fno-strict-aliasing 
-Werror=declaration-after-statement -fno-builtin -fno-common 
-Werror=return-type -Wno-unused-local-typedefs -DHAVE_STDINT_H=1 
-DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" 
-D__USE_UNIX98=1 -DHAVE_SNPRINTF  -DBUILD_PDF=1 -I./pdf -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
 -Werror=format-security -fcf-protection -DHAVE_RESTRICT=1  -DUSE_LIBPAPER 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp   -fno-strict-aliasing 
-DHAVE_POPEN_PROTO=1   -DSHARE_JPX=1 -I/usr/include/openjpeg-2.5  
-DUSE_OPENJPEG_JP2  -DPDF_INCLUDED -I./pdf -I./soobj -I./pcl/pl -I./base 
-Isrc/lib -I./jpegxr -Isrc -Isrc/src/lib/o

Bug#1075056: gutenprint: ftbfs with GCC-14

2024-07-03 Thread Matthias Klose
Package: src:gutenprint
Version: 5.3.4.20220624T01008808d602-2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/gutenprint_5.3.4.20220624T01008808d602-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41:
/usr/include/gimp-2.0/libgimp/gimpdrawable.h:52:16: note: declared here
   52 | GimpDrawable * gimp_drawable_get(gint32 
drawable_ID);
  |^
print.c:254:3: warning: ‘gimp_gamma’ is deprecated [-Wdeprecated-declarations]
  254 |   stp_set_float_parameter(gimp_vars.v, "AppGamma", gimp_gamma());
  |   ^~~
/usr/include/gimp-2.0/libgimp/gimp.h:348:16: note: declared here
  348 | gdoublegimp_gamma(void) G_GNUC_CONST;
  |^~
print.c:514:7: warning: ‘gimp_tile_cache_ntiles’ is deprecated 
[-Wdeprecated-declarations]
  514 |   gimp_tile_cache_ntiles ((drawable->height + gimp_tile_width () - 
1) /
  |   ^~
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:63:
/usr/include/gimp-2.0/libgimp/gimptile.h:60:9: note: declared here
   60 | voidgimp_tile_cache_ntiles (gulong ntiles);
  | ^~
print.c:517:7: warning: ‘gimp_tile_cache_ntiles’ is deprecated 
[-Wdeprecated-declarations]
  517 |   gimp_tile_cache_ntiles ((drawable->width + gimp_tile_width () - 
1) /
  |   ^~
/usr/include/gimp-2.0/libgimp/gimptile.h:60:9: note: declared here
   60 | voidgimp_tile_cache_ntiles (gulong ntiles);
  | ^~
print.c:539:3: warning: ‘gimp_drawable_detach’ is deprecated 
[-Wdeprecated-declarations]
  539 |   gimp_drawable_detach (drawable);
  |   ^~~~
/usr/include/gimp-2.0/libgimp/gimpdrawable.h:54:16: note: declared here
   54 | void   gimp_drawable_detach (GimpDrawable  
*drawable);
  |^~~~
make[4]: *** [Makefile:558: print.o] Error 1
make[4]: *** Waiting for unfinished jobs
print-image-gimp.c: In function ‘Image_GimpDrawable_new’:
print-image-gimp.c:155:3: warning: ‘gimp_pixel_rgn_init’ is deprecated: Use 
'gimp_drawable_get_buffer' instead [-Wdeprecated-declarations]
  155 |   gimp_pixel_rgn_init(&(im->rgn), drawable, 0, 0,
  |   ^~~
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:57,
 from print_gimp.h:41:
/usr/include/gimp-2.0/libgimp/gimppixelrgn.h:48:11: note: declared here
   48 | void  gimp_pixel_rgn_init   (GimpPixelRgn  *pr,
  |   ^~~
print-image-gimp.c:165:7: warning: ‘gimp_image_get_cmap’ is deprecated: Use 
'gimp_image_get_colormap' instead [-Wdeprecated-declarations]
  165 |   im->cmap = gimp_image_get_cmap(image_ID, &(im->ncolors));
  |   ^~
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:47:
/usr/include/gimp-2.0/libgimp/gimpimage.h:49:16: note: declared here
   49 | guchar   * gimp_image_get_cmap(gint32  
image_ID,
  |^~~
print-image-gimp.c: In function ‘Image_get_row’:
print-image-gimp.c:244:5: warning: ‘gimp_pixel_rgn_get_col’ is deprecated: Use 
'gegl_buffer_get' instead [-Wdeprecated-declarations]
  244 | gimp_pixel_rgn_get_col(&(im->rgn), inter,
  | ^~
/usr/include/gimp-2.0/libgimp/gimppixelrgn.h:74:11: note: declared here
   74 | void  gimp_pixel_rgn_get_col(GimpPixelRgn  *pr,
  |   ^~
print-image-gimp.c:247:5: warning: ‘gimp_pixel_rgn_get_row’ is deprecated: Use 
'gegl_buffer_get' instead [-Wdeprecated-declarations]
  247 | gimp_pixel_rgn_get_row(&(im->rgn), inter,
  | ^~
/usr/include/gimp-2.0/libgimp/gimppixelr

Bug#1075069: hplip: ftbfs with GCC-14

2024-07-03 Thread Matthias Klose
Package: src:hplip
Version: 3.22.10+dfsg0-5
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/hplip_3.22.10+dfsg0-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
prnt/hpcups/genPCLm.cpp:1261:60: warning: ‘%s’ directive output may be 
truncated writing up to 255 bytes into a region of size 237 
[-Wformat-truncation=]
 1261 | snprintf(pOutStr,OUT_STR_SIZE,"%%  media-type: 
%s\n",m_pPCLmSSettings->userMediaType); writeStr2OutBuff(pOutStr);
  |^~
In function ‘int snprintf(char*, size_t, const char*, ...)’,
inlined from ‘void PCLmGenerator::writeJobTicket()’ at 
prnt/hpcups/genPCLm.cpp:1261:10:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:35: note: 
‘__builtin___snprintf_chk’ output between 21 and 276 bytes into a destination 
of size 256
   54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ~^~~
   55 |__glibc_objsize (__s), __fmt,
  |~
   56 |__va_arg_pack ());
  |~
prnt/hpcups/genPCLm.cpp: In member function ‘void 
PCLmGenerator::writeJobTicket()’:
prnt/hpcups/genPCLm.cpp:1262:62: warning: ‘%s’ directive output may be 
truncated writing up to 255 bytes into a region of size 235 
[-Wformat-truncation=]
 1262 | snprintf(pOutStr,OUT_STR_SIZE,"%%  media-source: 
%s\n",inputBin); writeStr2OutBuff(pOutStr);
  |  ^~

In function ‘int snprintf(char*, size_t, const char*, ...)’,
inlined from ‘void PCLmGenerator::writeJobTicket()’ at 
prnt/hpcups/genPCLm.cpp:1262:10:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:35: note: 
‘__builtin___snprintf_chk’ output between 23 and 278 bytes into a destination 
of size 256
   54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ~^~~
   55 |__glibc_objsize (__s), __fmt,
  |~
   56 |__va_arg_pack ());
  |~
prnt/hpcups/genPCLm.cpp: In member function ‘void 
PCLmGenerator::writeJobTicket()’:
prnt/hpcups/genPCLm.cpp:1263:55: warning: ‘%s’ directive output may be 
truncated writing up to 255 bytes into a region of size 242 
[-Wformat-truncation=]
 1263 | snprintf(pOutStr,OUT_STR_SIZE,"%%  sides: %s\n",duplex); 
writeStr2OutBuff(pOutStr);
  |   ^~~~
In function ‘int snprintf(char*, size_t, const char*, ...)’,
inlined from ‘void PCLmGenerator::writeJobTicket()’ at 
prnt/hpcups/genPCLm.cpp:1263:10:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:35: note: 
‘__builtin___snprintf_chk’ output between 16 and 271 bytes into a destination 
of size 256
   54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ~^~~
   55 |__glibc_objsize (__s), __fmt,
  |~
   56 |__va_arg_pack ());
  |~
prnt/hpcups/genPCLm.cpp: In member function ‘void 
PCLmGenerator::writeJobTicket()’:
prnt/hpcups/genPCLm.cpp:1265:60: warning: ‘%s’ directive output may be 
truncated writing up to 255 bytes into a region of size 237 
[-Wformat-truncation=]
 1265 | snprintf(pOutStr,OUT_STR_SIZE,"%%  output

Bug#1075248: magicfilter: ftbfs with GCC-14

2024-07-03 Thread Matthias Klose
Package: src:magicfilter
Version: 1.2-67
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/magicfilter_1.2-67_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
gpgv:issuer "deb...@alteholz.de"
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for 
./magicfilter_1.2-67.dsc: no acceptable signature found
dpkg-source: info: extracting magicfilter in /<>
dpkg-source: info: unpacking magicfilter_1.2.orig.tar.gz
dpkg-source: info: unpacking magicfilter_1.2-67.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 01-create-magicfilterconfig.patch
dpkg-source: info: applying 02-autotools-support.patch
dpkg-source: info: applying 03-make-ghostscript-quiet.patch
dpkg-source: info: applying 04-support-for-eglibc2.10.patch
dpkg-source: info: applying 05-main-magicfilter-changes.patch
dpkg-source: info: applying 10-additional-core-filter-support.patch
dpkg-source: info: applying 11-additional-printer-filters.patch

Check disk space


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-61e4467e-759e-4936-a504-10f37405d307
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package magicfilter
dpkg-buildpackage: info: source version 1.2-67
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Thorsten Alteholz 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
rm -f config.sub config.guess
rm -f build
[ ! -f Makefile ] || /usr/bin/make distclean || /usr/bin/make -f Makefile.in 
distclean
rm -rf *~ filters/*~ debian/tmp debian/*~ debian/files debian/substvars
rm -rf debian/tmp
 debian/rules binary
ln -sf /usr/share/misc/config.sub .
ln -sf /usr/share/misc/config.guess .
rm -f config.cache
GZIP=/bin/gzip BZIP2=/bin/bzip2 ./configure --prefix=/usr \
--infodir=/usr/share/info \
--mandir=/usr/share/man \
--bindir=/usr/sbin
creating cache ./config.cache
checking for gcc... x86_64-linux-gnu-gcc
checking whether the C compiler (x86_64-linux-gnu-gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot 
create executables.
make: *** [debian/rules:31: build] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Bug#1097625: pnm2ppa: ftbfs with GCC-15

2025-02-17 Thread Matthias Klose
Package: src:pnm2ppa
Version: 1.13-13
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/pnm2ppa_1.13-13_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html

[...]
../ppa.c:478:40: warning: comparison of integer expressions of different 
signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
  478 | if (compressed_len > final_len)
  |^
../ppa.c:485:24: warning: comparison of integer expressions of different 
signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
  485 | if (compressed_len > final_len)
  |^
make[3]: *** [Makefile:627: dither.o] Error 1
../cutswath.c: In function ‘read_black_image’:
../cutswath.c:780:34: warning: variable ‘after_color’ set but not used 
[-Wunused-but-set-variable]
  780 |   BOOLEAN  got_nonblank = false, after_color = false, ignore_color = 
false;
  |  ^~~
../cutswath.c: In function ‘r2l_black_sweep’:
../cutswath.c:1080:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 1080 |   int i, j , width, evenlines, oddlines;
  |^~~~
../ppa.c: In function ‘ppa_print_sweep’:
../ppa.c:670:10: warning: comparison of integer expressions of different 
signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
  670 |i < nozzle_data_size; i++, pc += 16) {
  |  ^
../cutswath.c: In function ‘l2r_black_sweep’:
../cutswath.c:1219:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 1219 |   int i, j , width, evenlines, oddlines;
  |^~~~
make[3]: *** [Makefile:627: ppa.o] Error 1
../cutswath.c: In function ‘l2r_color_sweep’:
../cutswath.c:1931:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 1931 |   int i, j , width, evenlines, oddlines;
  |^~~~
../cutswath.c: In function ‘r2l_color_sweep’:
../cutswath.c:2154:32: warning: variable ‘oddlines’ set but not used 
[-Wunused-but-set-variable]
 2154 |   int i, j , width, evenlines, oddlines;
  |^~~~
In file included from ../pnm2ppa.c:34:
../global.h:30:3: error: cannot use keyword ‘false’ as enumeration constant
   30 | { false = 0, true = 1 }
  |   ^
../global.h:30:3: note: ‘false’ is a keyword with ‘-std=c23’ onwards
In file included from ../gamma.c:26:
../global.h:30:3: error: cannot use keyword ‘false’ as enumeration constant
   30 | { false = 0, true = 1 }
  |   ^
../global.h:30:3: note: ‘false’ is a keyword with ‘-std=c23’ onwards
In file included from ../image.c:29:
../global.h:30:3: error: cannot use keyword ‘false’ as enumeration constant
   30 | { false = 0, true = 1 }
  |   ^
../global.h:30:3: note: ‘false’ is a keyword with ‘-std=c23’ onwards
../pnm2ppa.c: In function ‘print_pnm’:
../pnm2ppa.c:120:13: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  120 | fgets (line, 1024, fptr);
  | ^~~~
../image.c: In function ‘remallocBuffer’:
../image.c:280:60: warning: comparison of integer expressions of different 
signedness: ‘size_t’ {aka ‘long unsigned int’} and ‘int’ [-Wsign-compare]
  280 | if (image->bufpos + image->buflines * linesize + bytes < 
image->bufsize)
  |^
../image.c:294:64: warning: comparison of integer expressions of different 
signedness: ‘size_t’ {aka ‘long unsigned int’} and ‘int’ [-Wsign-compare]
  294 | if (image->bufpos + image->buflines * linesize + bytes < 
image->bufsize)
  |^

Bug#1096830: ifhp: ftbfs with GCC-15

2025-02-17 Thread Matthias Klose
Package: src:ifhp
Version: 3.5.20-20
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/ifhp_3.5.20-20_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html

[...]
./ifhp.conf.in >ifhp.conf
if [ "src" = po ] ; then \
for i in po/Makefile* ; do \
if [ -f "$i" ] ; then \
if grep '^mkinstalldirs.*=.*case' $i ; then \
echo "fixing broken $i which causes wrong path to mkinstalldirs 
to be used"; \
perl -spi -e 's:^mkinstalldirs\s*=\s*.*:mkinstalldirs = 
\$(SHELL) \$(MKINSTALLDIRS):' $i; \
fi \
fi \
done \
fi
if [ "src" != po -o "no" != "no" ] ; then \
cd src; /usr/bin/make localedir=/usr/share/locale \
DESTDIR= all ; \
fi
make[2]: Entering directory '/build/reproducible-path/ifhp-3.5.20/src'
x86_64-linux-gnu-gcc -g -W -Wall -Werror -Wno-unused  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/ifhp-3.5.20=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wno-unused-parameter 
-Wno-implicit-fallthrough -g -W -Wall -Werror -Wno-unused  -DHAVE_CONFIG_H -I. 
-I.. -I.  -DIFHP_CONF=\"/etc/ifhp.conf\" -DLOCALEDIR=\"/usr/share/locale\"   -c 
-o ifhp.o ifhp.c
ifhp.c: In function ‘plp_signal’:
ifhp.c:1792:24: error: assignment to ‘__sighandler_t’ {aka ‘void (*)(int)’} 
from incompatible pointer type ‘plp_sigfunc_t’ {aka ‘int (*)(int)’} 
[-Wincompatible-pointer-types]
 1792 | act.sa_handler = func;
  |^
In file included from /usr/include/x86_64-linux-gnu/sys/param.h:28,
 from portable.h:283,
 from ifhp.h:21,
 from ifhp.c:14:
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
  |^~
portable.h:545:24: note: ‘plp_sigfunc_t’ declared here
  545 | typedef plp_signal_t (*plp_sigfunc_t)(int) ;
  |^
ifhp.c:1799:24: error: returning ‘void (*)(int)’ from a function with 
incompatible return type ‘plp_sigfunc_t’ {aka ‘int (*)(int)’} 
[-Wincompatible-pointer-types]
 1799 | return (SIG_ERR);
  |^
portable.h:545:24: note: ‘plp_sigfunc_t’ declared here
  545 | typedef plp_signal_t (*plp_sigfunc_t)(int) ;
  |^
ifhp.c:1801:16: error: cast between incompatible function types from 
‘__sighandler_t’ {aka ‘void (*)(int)’} to ‘plp_signal_t (*)(int)’ {aka ‘int 
(*)(int)’} [-Werror=cast-function-type]
 1801 | return (plp_sigfunc_t) oact.sa_handler;
  |^
ifhp.c: In function ‘plp_signal_break’:
ifhp.c:1819:24: error: assignment to ‘__sighandler_t’ {aka ‘void (*)(int)’} 
from incompatible pointer type ‘plp_sigfunc_t’ {aka ‘int (*)(int)’} 
[-Wincompatible-pointer-types]
 1819 | act.sa_handler = func;
  |^
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
  |^~
portable.h:545:24: note: ‘plp_sigfunc_t’ declared here
  545 | typedef plp_signal_t (*plp_sigfunc_t)(int) ;
  |^
ifhp.c:1826:24: error: returning ‘void (*)(int)’ from a function with 
incompatible return type ‘plp_sigfunc_t’ {aka ‘int (*)(int)’} 
[-Wincompatible-pointer-types]
 1826 | return (SIG_ERR);
  |^
portable.h:545:24: note: ‘plp_sigfunc_t’ declared here
  545 | typedef plp_signal_t (*plp_sigfunc_t)(int) ;
  |^
ifhp.c:1828:16: error: cast between incompatible function types from 
‘__sighandler_t’ {aka ‘void (*)(int)’} to ‘plp_signal_t

Bug#1096838: ink: ftbfs with GCC-15

2025-02-17 Thread Matthias Klose
Package: src:ink
Version: 0.5.3-6
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/ink_0.5.3-6_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html

[...]
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking how to run the C preprocessor... gcc -E
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking for rpmbuild... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for inklevel.h... yes
checking for get_ink_level in -linklevel... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating ink.spec
config.status: creating ink.1
config.status: creating config.h
config.status: executing depfiles commands
   dh_auto_build
make -j8
make[1]: Entering directory '/build/reproducible-path/ink-0.5.3'
make  all-am
make[2]: Entering directory '/build/reproducible-path/ink-0.5.3'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/ink-0.5.3=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIE 
-c -o ink.o ink.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/ink-0.5.3=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIE 
-c -o malloc.o malloc.c
malloc.c:6:7: warning: conflicting types for built-in function ‘malloc’; 
expected ‘void *(long unsigned int)’ [-Wbuiltin-declaration-mismatch]
6 | void *malloc ();
  |   ^~
malloc.c:5:1: note: ‘malloc’ is declared in header ‘’
4 | #include 
  +++ |+#include 
5 | 
malloc.c: In function ‘rpl_malloc’:
malloc.c:16:10: error: too many arguments to function ‘malloc’; expected 0, 
have 1
   16 |   return malloc (n);
  |  ^~  ~
malloc.c:6:7: note: declared here
6 | void *malloc ();
  |   ^~
make[2]: *** [Makefile:450: malloc.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory '/build/reproducible-path/ink-0.5.3'
make[1]: *** [Makefile:327: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/ink-0.5.3'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Bug#1096702: ghostscript: ftbfs with GCC-15

2025-02-17 Thread Matthias Klose
Package: src:ghostscript
Version: 10.04.0~dfsg-2
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/ghostscript_10.04.0~dfsg-2_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html

[...]
checking for working fork... yes
checking for working vfork... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking whether lstat correctly handles trailing slash... yes
checking whether stat accepts an empty string... no
checking for bzero... yes
checking for dup2... yes
checking for floor... yes
checking for gettimeofday... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for mkdir... yes
checking for mkfifo... yes
checking for modf... yes
checking for pow... yes
checking for putenv... yes
checking for rint... yes
checking for setenv... yes
checking for sqrt... yes
checking for strchr... yes
checking for strrchr... yes
checking for strspn... yes
checking for strstr... yes
checking minimum memory pointer alignment... done
checking for sqrtf... yes
checking for strnlen... yes
checking byteswap support... yes
checking for byteswap.h... yes
checking whether to explicitly disable strict aliasing... yes
configure: creating ./config.status
config.status: creating Makefile
make[1]: Leaving directory '/build/reproducible-path/ghostscript-10.04.0~dfsg'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/reproducible-path/ghostscript-10.04.0~dfsg'
dh_auto_build -- so 
make -j1 so
make[2]: Entering directory '/build/reproducible-path/ghostscript-10.04.0~dfsg'
make -f Makefile so-subtarget BUILDDIRPREFIX=so
make[3]: Entering directory '/build/reproducible-path/ghostscript-10.04.0~dfsg'
make -f Makefile GS_DOT_O= REALMAIN_OBJ= GS_XE=./sobin/libgs.so.10.04 
GPCL_XE=./sobin/libno_gpcl6.so.10.04 GXPS_XE=./sobin/libno_gxps.so.10.04 
GPDF_XE=./sobin/libno_gpdf.so.10.04 GPDL_XE=./sobin/libno_gpdl.so.10.04 
DISPLAY_DEV=./soobj/display.dev BUILDDIRPREFIX=so GENOPT='' 
LDFLAGS='-Wl,-z,relro  '\
 CFLAGS='-O2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
-Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes 
-Wwrite-strings -fno-strict-aliasing -Werror=declaration-after-statement 
-fno-builtin -fno-common -Werror=return-type -Wno-unused-local-typedefs 
-DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 
-DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1 
-DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1 -DHAVE_SNPRINTF  
-DBUILD_PDF=1 -I./pdf -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/ghostscript-10.04.0~dfsg=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -DHAVE_RESTRICT=1  -DUSE_LIBPAPER 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp   -fno-strict-aliasing 
-DHAVE_POPEN_PROTO=1  ' prefix=/usr\
 directories
make[4]: Entering directory '/build/reproducible-path/ghostscript-10.04.0~dfsg'
make[4]: Leaving directory '/build/reproducible-path/ghostscript-10.04.0~dfsg'
make -f Makefile GS_DOT_O= REALMAIN_OBJ= GS_XE=./sobin/libgs.so.10.04 
GPCL_XE=./sobin/libno_gpcl6.so.10.04 GXPS_XE=./sobin/libno_gxps.so.10.04 
GPDF_XE=./sobin/libno_gpdf.so.10.04 GPDL_XE=./sobin/libno_gpdl.so.10.04 
DISPLAY_DEV=./soobj/display.dev BUILDDIRPREFIX=so GENOPT='' 
LDFLAGS='-Wl,-z,relro  '\
 CFLAGS='-O2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
-Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes 
-Wwrite-strings -fno-strict-aliasing -Werror=declaration-after-statement 
-fno-builtin -fno-common -Werror=return-type -Wno-unused-local-typedefs 
-DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 
-DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1 
-DGX_C

Bug#1097795: rlpr: ftbfs with GCC-15

2025-02-17 Thread Matthias Klose
Package: src:rlpr
Version: 2.06-2
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/rlpr_2.06-2_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html

[...]
error.c:46:6: warning: conflicting types for built-in function ‘exit’; expected 
‘void(int)’ [-Wbuiltin-declaration-mismatch]
   46 | void exit ();
  |  ^~~~
error.c:30:1: note: ‘exit’ is declared in header ‘’
   29 | #  include 
  +++ |+#include 
   30 | #  define VA_START(args, lastarg) va_start(args, lastarg)
error.c:82:7: error: conflicting types for ‘strerror’; have ‘char *(void)’
   82 | char *strerror ();
  |   ^~~~
In file included from error.c:25:
/usr/include/string.h:419:14: note: previous declaration of ‘strerror’ with 
type ‘char *(int)’
  419 | extern char *strerror (int __errnum) __THROW;
  |  ^~~~
error.c: In function ‘error’:
error.c:143:30: error: too many arguments to function ‘strerror’; expected 0, 
have 1
  143 | fprintf (stderr, ": %s", strerror (errnum));
  |  ^~~~  ~~
error.c:82:7: note: declared here
   82 | char *strerror ();
  |   ^~~~
error.c:147:5: error: too many arguments to function ‘exit’; expected 0, have 1
  147 | exit (status);
  | ^~~~  ~~
error.c:46:6: note: declared here
   46 | void exit ();
  |  ^~~~
error.c: In function ‘error_at_line’:
error.c:211:30: error: too many arguments to function ‘strerror’; expected 0, 
have 1
  211 | fprintf (stderr, ": %s", strerror (errnum));
  |  ^~~~  ~~
error.c:82:7: note: declared here
   82 | char *strerror ();
  |   ^~~~
error.c:215:5: error: too many arguments to function ‘exit’; expected 0, have 1
  215 | exit (status);
  | ^~~~  ~~
error.c:46:6: note: declared here
   46 | void exit ();
  |  ^~~~
In file included from xstrtol.c:57:
xstrtol.c: In function ‘xstrtol’:
xstrtol.h:10:21: warning: old-style function definition [-Wold-style-definition]
   10 | #  define __xstrtol xstrtol
  | ^~~
xstrtol.c:73:1: note: in expansion of macro ‘__xstrtol’
   73 | __xstrtol (s, ptr, base, val, valid_suffixes)
  | ^
xstrtol.h:11:20: error: too many arguments to function ‘strtol’; expected 0, 
have 3
   11 | #  define __strtol strtol
  |^~
xstrtol.c:89:9: note: in expansion of macro ‘__strtol’
   89 |   tmp = __strtol (s, p, base);
  | ^~~~
xstrtol.h:11:20: note: declared here
   11 | #  define __strtol strtol
  |^~
xstrtol.c:68:21: note: in expansion of macro ‘__strtol’
   68 | __unsigned long int __strtol ();
  | ^~~~
make[3]: *** [Makefile:221: error.o] Error 1
make[3]: *** [Makefile:221: xstrtol.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/rlpr-2.06/lib'
make[2]: *** [Makefile:189: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/rlpr-2.06'
make[1]: *** [Makefile:142: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/rlpr-2.06'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2