[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/pipexec_2.5.5-2_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 whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
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 whether to build with debug information... no
checking whether to build with profiling support... no
checking whether to build with coverage... 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
config.status: executing libtool commands
dh_auto_build
make -j8
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make all-am
make[2]: Entering directory '/<<PKGBUILDDIR>>'
bash ./build/version-gen.sh .
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/pipexec.o src/pipexec.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/logging.o src/logging.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/version.o src/version.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/command_info.o src/command_info.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/pipe_info.o src/pipe_info.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/ptee.o src/ptee.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/peet.o src/peet.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o test/ptest.o test/ptest.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Werror -O3 -c -o src/app_version.o src/app_version.c
/bin/bash ./libtool --tag=CC --mode=link gcc -std=c99 -Wall -Wextra -Werror -O3 -Wl,-z,relro -o test/ptest test/ptest.o
In function ‘pipes_end_info_parse’,
inlined from ‘pipe_info_parse’ at src/pipe_info.c:59:11:
src/pipe_info.c:17:10: error: dangling pointer ‘colon’ to ‘end_fd’ may be used [-Werror=dangling-pointer=]
17 | *colon = '\0';
| ~~~~~~~^~~~~~
src/pipe_info.c: In function ‘pipe_info_parse’:
src/pipe_info.c:19:9: note: ‘end_fd’ declared here
19 | char *end_fd;
| ^~~~~~
In function ‘pipes_end_info_parse’,
inlined from ‘pipe_info_parse’ at src/pipe_info.c:59:11:
src/pipe_info.c:20:14: error: dangling pointer ‘colon’ to ‘end_fd’ may be used [-Werror=dangling-pointer=]
20 | pend->fd = strtol(colon + 1, &end_fd, 10);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/pipe_info.c: In function ‘pipe_info_parse’:
src/pipe_info.c:19:9: note: ‘end_fd’ declared here
19 | char *end_fd;
| ^~~~~~
/bin/bash ./libtool --tag=CC --mode=link gcc -std=c99 -Wall -Wextra -Werror -O3 -Wl,-z,relro -o bin/ptee src/version.o src/app_version.o src/ptee.o
/bin/bash ./libtool --tag=CC --mode=link gcc -std=c99 -Wall -Wextra -Werror -O3 -Wl,-z,relro -o bin/peet src/version.o src/app_version.o src/peet.o
libtool: link: gcc -std=c99 -Wall -Wextra -Werror -O3 -Wl,-z -Wl,relro -o test/ptest test/ptest.o
cc1: all warnings being treated as errors
make[2]: *** [Makefile:824: src/pipe_info.o] Error 1
make[2]: *** Waiting for unfinished jobs....
libtool: link: gcc -std=c99 -Wall -Wextra -Werror -O3 -Wl,-z -Wl,relro -o bin/peet src/version.o src/app_version.o src/peet.o
libtool: link: gcc -std=c99 -Wall -Wextra -Werror -O3 -Wl,-z -Wl,relro -o bin/ptee src/version.o src/app_version.o src/ptee.o
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:589: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2