Your message dated Thu, 14 May 2026 22:23:28 +0200
with message-id <[email protected]>
and subject line autoconf fixed in sid
has caused the Debian Bug report #1133503,
regarding idba: ftbfs with GCC-16
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.)


-- 
1133503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133503
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:idba
Version: 1.1.3-8
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: ftbfs-gcc-16

Hi,

idba fails to build in a test rebuild on at least amd64 and arm64 with
gcc-16/g++-16, but builds properly with gcc-15/g++-15. The severity of this
report will be raised before the forky release.

The full build log can be found at:
https://people.debian.org/~ema/gcc-16-rebuilds/output-1/idba_arm64.build.xz

The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

Common build failures include unused (but set) variables, array subscripts
partly outside array bounds, and new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-16/porting_to.html

Please only close this issue after double-checking that the package can be
built correctly with GCC 16.

Please do not reassign this bug to another package. If a fix in another package
is required, then file a bug for the other package (or clone), and mark this
bug as blocked by the bug in the other package.

[...]


  845 |   class IteratorImpl<std::index_sequence<I...>>
      |                           ^~~~~~~~~~~~~~
/usr/include/gtest/internal/gtest-param-util.h:845:27: note: 
‘std::index_sequence’ is only available from C++14 onwards
/usr/include/gtest/internal/gtest-param-util.h:845:27: error: ‘index_sequence’ 
is not a member of ‘std’ [-Wtemplate-body]
/usr/include/gtest/internal/gtest-param-util.h:845:27: note: 
‘std::index_sequence’ is only available from C++14 onwards
/usr/include/gtest/internal/gtest-param-util.h:845:43: error: expected 
parameter pack before ‘...’ [-Wtemplate-body]
  845 |   class IteratorImpl<std::index_sequence<I...>>
      |                                           ^~~
/usr/include/gtest/internal/gtest-param-util.h:845:43: error: template argument 
1 is invalid [-Wtemplate-body]
/usr/include/gtest/internal/gtest-param-util.h:845:46: error: expected 
unqualified-id before ‘>’ token [-Wtemplate-body]
  845 |   class IteratorImpl<std::index_sequence<I...>>
      |                                              ^~
/usr/include/gtest/internal/gtest-param-util.h:936:38: error: 
‘make_index_sequence’ is not a member of ‘std’ [-Wtemplate-body]
  936 |   using Iterator = IteratorImpl<std::make_index_sequence<sizeof...(T)>>;
      |                                      ^~~~~~~~~~~~~~~~~~~
/usr/include/gtest/internal/gtest-param-util.h:936:38: note: 
‘std::make_index_sequence’ is only available from C++14 onwards
/usr/include/gtest/internal/gtest-param-util.h:936:38: error: 
‘make_index_sequence’ is not a member of ‘std’ [-Wtemplate-body]
/usr/include/gtest/internal/gtest-param-util.h:936:38: note: 
‘std::make_index_sequence’ is only available from C++14 onwards
/usr/include/gtest/internal/gtest-param-util.h:936:69: error: template argument 
1 is invalid [-Wtemplate-body]
  936 |   using Iterator = IteratorImpl<std::make_index_sequence<sizeof...(T)>>;
      |                                                                     ^
/usr/include/gtest/internal/gtest-param-util.h: In member function 
‘testing::internal::ParamIteratorInterface<std::tuple<_Elements ...> >* 
testing::internal::CartesianProductGenerator<T>::Begin() const’:
/usr/include/gtest/internal/gtest-param-util.h:835:16: error: expected 
type-specifier before ‘Iterator’ [-Wtemplate-body]
  835 |     return new Iterator(this, generators_, false);
      |                ^~~~~~~~
/usr/include/gtest/internal/gtest-param-util.h:835:16: error: expected ‘;’ 
before ‘Iterator’ [-Wtemplate-body]
/usr/include/gtest/internal/gtest-param-util.h: In member function 
‘testing::internal::ParamIteratorInterface<std::tuple<_Elements ...> >* 
testing::internal::CartesianProductGenerator<T>::End() const’:
/usr/include/gtest/internal/gtest-param-util.h:838:16: error: expected 
type-specifier before ‘Iterator’ [-Wtemplate-body]
  838 |     return new Iterator(this, generators_, true);
      |                ^~~~~~~~
/usr/include/gtest/internal/gtest-param-util.h:838:16: error: expected ‘;’ 
before ‘Iterator’ [-Wtemplate-body]
/usr/include/gtest/internal/gtest-param-util.h: At global scope:
/usr/include/gtest/internal/gtest-param-util.h:1053:21: error: ‘remove_cv_t’ in 
namespace ‘std’ does not name a template type; did you mean ‘remove_cv’? 
[-Wtemplate-body]
 1053 |   using type = std::remove_cv_t<std::remove_reference_t<P>>;
      |                     ^~~~~~~~~~~
      |                     remove_cv
/usr/include/gtest/internal/gtest-param-util.h: In instantiation of ‘class 
testing::internal::ValueArray<bool, bool>’:
/usr/include/gtest/gtest-param-test.h:360:61:   required from here
  360 | inline internal::ParamGenerator<bool> Bool() { return Values(false, 
true); }
      |                                                       
~~~~~~^~~~~~~~~~~~~
/usr/include/gtest/internal/gtest-param-util.h:819:20: error: 
‘testing::internal::ValueArray<Ts>::v_’ has incomplete type
  819 |   FlatTuple<Ts...> v_;
      |                    ^~
/usr/include/gtest/internal/gtest-internal.h:1212:7: note: declaration of 
‘class testing::internal::FlatTuple<bool, bool>’
 1212 | class FlatTuple
      |       ^~~~~~~~~
/usr/include/gtest/gtest-param-test.h:483:56: error: missing template arguments 
before ‘(’ token
  483 |           typename StdFunction = 
decltype(std::function(std::declval<Func>()))>
      |                                                        ^
/usr/include/gtest/gtest-param-test.h:493:56: error: missing template arguments 
before ‘(’ token
  493 |           typename StdFunction = 
decltype(std::function(std::declval<Func>()))>
      |                                                        ^
/usr/include/gtest/gtest-param-test.h:494:1: error: ‘ConvertGenerator’ function 
uses ‘auto’ type specifier without trailing return type
  494 | auto ConvertGenerator(Gen&& gen, Func&& f) {
      | ^~~~
/usr/include/gtest/gtest-param-test.h:494:1: note: deduced return type only 
available with ‘-std=c++14’ or ‘-std=gnu++14’
/usr/include/gtest/gtest.h:301:30: error: ‘std::enable_if_t’ has not been 
declared
  301 |   template <typename T, std::enable_if_t<std::is_convertible<T, 
int64_t>::value,
      |                              ^~~~~~~~~~~
/usr/include/gtest/gtest.h:301:30: note: ‘std::enable_if_t’ is only available 
from C++14 onwards
/usr/include/gtest/gtest.h:301:41: error: expected ‘>’ before ‘<’ token
  301 |   template <typename T, std::enable_if_t<std::is_convertible<T, 
int64_t>::value,
      |                                         ^
make[3]: *** [Makefile:696: gtest_main.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/idba-1.1.3/test'
make[2]: *** [Makefile:1238: check-am] Error 2
make[2]: Leaving directory '/build/reproducible-path/idba-1.1.3/test'
make[1]: *** [debian/rules:24: override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/reproducible-path/idba-1.1.3'
make: *** [debian/rules:10: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2

--- End Message ---
--- Begin Message ---
Hi,

these bugs were blocked by #1133694 in autoconf.

autoconf 0.73-1 was fixed and 0.73-2 got uploaded to unstable now so those bugs 
can be closed.
(I also closed the autoconf one properly now)

Regards,

Rene

--- End Message ---

Reply via email to