Your message dated Fri, 27 Aug 2021 15:06:25 -0400
with message-id <[email protected]>
and subject line Re: zxing-cpp: ftbfs with GCC-11
has caused the Debian Bug report #984404,
regarding zxing-cpp: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
984404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984404
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:zxing-cpp
Version: 1.1.1-2
Severity: normal
Tags: sid bookworm
User: [email protected]
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/zxing-cpp_1.1.1-2_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.
[...]
Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
to a directory containing one of the above files. If "Qt5" provides a
separate development package or SDK, be sure it has been installed.
-- Configuring done
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_EXPORT_NO_PACKAGE_REGISTRY
-- Build files have been written to: /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
dh_auto_build
cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<<PKGBUILDDIR>> -B/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/CMakeFiles
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make -f core/CMakeFiles/ZXing.dir/build.make core/CMakeFiles/ZXing.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends
"Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/core
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core/CMakeFiles/ZXing.dir/DependInfo.cmake
--color=
Dependee
"/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core/CMakeFiles/ZXing.dir/DependInfo.cmake"
is newer than depender
"/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core/CMakeFiles/ZXing.dir/depend.internal".
Dependee
"/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core/CMakeFiles/CMakeDirectoryInformation.cmake"
is newer than depender
"/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core/CMakeFiles/ZXing.dir/depend.internal".
Scanning dependencies of target ZXing
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make -f core/CMakeFiles/ZXing.dir/build.make core/CMakeFiles/ZXing.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 1%] Building CXX object core/CMakeFiles/ZXing.dir/src/BarcodeFormat.cpp.o
[ 2%] Building CXX object core/CMakeFiles/ZXing.dir/src/BitArray.cpp.o
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core && /usr/bin/c++ -DZXing_EXPORTS
-I/<<PKGBUILDDIR>>/core/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -Wall -Wextra -Wno-missing-braces -ffloat-store
-std=c++14 -o CMakeFiles/ZXing.dir/src/BarcodeFormat.cpp.o -c
/<<PKGBUILDDIR>>/core/src/BarcodeFormat.cpp
[ 2%] Building CXX object core/CMakeFiles/ZXing.dir/src/BitMatrix.cpp.o
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core && /usr/bin/c++ -DZXing_EXPORTS
-I/<<PKGBUILDDIR>>/core/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -Wall -Wextra -Wno-missing-braces -ffloat-store
-std=c++14 -o CMakeFiles/ZXing.dir/src/BitArray.cpp.o -c
/<<PKGBUILDDIR>>/core/src/BitArray.cpp
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core && /usr/bin/c++ -DZXing_EXPORTS
-I/<<PKGBUILDDIR>>/core/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -Wall -Wextra -Wno-missing-braces -ffloat-store
-std=c++14 -o CMakeFiles/ZXing.dir/src/BitMatrix.cpp.o -c
/<<PKGBUILDDIR>>/core/src/BitMatrix.cpp
[ 3%] Building CXX object core/CMakeFiles/ZXing.dir/src/BitMatrixIO.cpp.o
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/core && /usr/bin/c++ -DZXing_EXPORTS
-I/<<PKGBUILDDIR>>/core/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -Wall -Wextra -Wno-missing-braces -ffloat-store
-std=c++14 -o CMakeFiles/ZXing.dir/src/BitMatrixIO.cpp.o -c
/<<PKGBUILDDIR>>/core/src/BitMatrixIO.cpp
In file included from /<<PKGBUILDDIR>>/core/src/BitMatrix.cpp:21:
/<<PKGBUILDDIR>>/core/src/Pattern.h: In function ‘bool
ZXing::IsRightGuard(const ZXing::PatternView&, const ZXing::FixedPattern<N,
SUM, IS_SPARCE>&, float, float)’:
/<<PKGBUILDDIR>>/core/src/Pattern.h:210:54: error: ‘numeric_limits’ is not a
member of ‘std’
210 | int spaceInPixel = view.isAtLastBar() ?
std::numeric_limits<int>::max() : *view.end();
| ^~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/core/src/Pattern.h:210:69: error: expected primary-expression
before ‘int’
210 | int spaceInPixel = view.isAtLastBar() ?
std::numeric_limits<int>::max() : *view.end();
| ^~~
/<<PKGBUILDDIR>>/core/src/Pattern.h:210:69: error: expected ‘:’ before ‘int’
210 | int spaceInPixel = view.isAtLastBar() ?
std::numeric_limits<int>::max() : *view.end();
| ^~~
| :
/<<PKGBUILDDIR>>/core/src/Pattern.h:210:69: error: expected primary-expression
before ‘int’
210 | int spaceInPixel = view.isAtLastBar() ?
std::numeric_limits<int>::max() : *view.end();
| ^~~
/<<PKGBUILDDIR>>/core/src/Pattern.h: In function ‘ZXing::PatternView
ZXing::FindLeftGuard(const ZXing::PatternView&, int, Pred)’:
/<<PKGBUILDDIR>>/core/src/Pattern.h:218:59: error: ‘numeric_limits’ is not a
member of ‘std’
218 | if (window.isAtFirstBar() && isGuard(window,
std::numeric_limits<int>::max()))
| ^~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/core/src/Pattern.h:218:74: error: expected primary-expression
before ‘int’
218 | if (window.isAtFirstBar() && isGuard(window,
std::numeric_limits<int>::max()))
|
^~~
make[3]: *** [core/CMakeFiles/ZXing.dir/build.make:111:
core/CMakeFiles/ZXing.dir/src/BitMatrix.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:162: core/CMakeFiles/ZXing.dir/all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:163: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install
--strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:18: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Version: 1.2.0-1
Confirmed to be fixed in zxing-cpp/1.2.0-1.
Thanks,
Boyuan Yang
On Wed, 03 Mar 2021 16:19:04 +0000 Matthias Klose <[email protected]> wrote:
> Package: src:zxing-cpp
> Version: 1.1.1-2
> Severity: normal
> Tags: sid bookworm
> User: [email protected]
> 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/zxing-cpp_1.1.1-2_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.
>
> [...]
> Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
> to a directory containing one of the above files. If "Qt5" provides a
> separate development package or SDK, be sure it has been installed.
>
>
> -- Configuring done
> -- Generating done
> CMake Warning:
> Manually-specified variables were not used by the project:
>
> CMAKE_EXPORT_NO_PACKAGE_REGISTRY
>
>
> -- Build files have been written to: /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
> dh_auto_build
> cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-
program=true" VERBOSE=1
> make[1]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> /usr/bin/cmake -S/<<PKGBUILDDIR>> -B/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu --
check-build-system CMakeFiles/Makefile.cmake 0
> /usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/obj-x86_64-linux-
gnu/CMakeFiles /<<PKGBUILDDIR>>/obj-x86_64-linux-
gnu//CMakeFiles/progress.marks
> make -f CMakeFiles/Makefile2 all
signature.asc
Description: This is a digitally signed message part
--- End Message ---
