Bug#1133513: libe-book: ftbfs with GCC-16

>> checking how to run the C++ preprocessor... g++ -std=gnu++11 -E
>> checking for ld used by g++ -std=gnu++11... /usr/bin/x86_64-linux-gnu-ld -m elf_x86_64
>> checking if the linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) is GNU ld... yes
>> checking whether the g++ -std=gnu++11 linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes
>> checking for g++ -std=gnu++11 option to produce PIC... -fPIC -DPIC
>> checking if g++ -std=gnu++11 PIC flag -fPIC -DPIC works... yes
>> checking if g++ -std=gnu++11 static flag -static works... yes
>> checking if g++ -std=gnu++11 supports -c -o file.o... yes
>> checking if g++ -std=gnu++11 supports -c -o file.o... (cached) yes
>> checking whether the g++ -std=gnu++11 linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes
>> checking dynamic linker characteristics... (cached) GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking whether g++ -std=gnu++11 supports C++11 features by default... yes
>>
>> Looks like it.
>>
>> That of course breaks. Now the question is why autoconf unhelpfully adds that with gcc 16...
>> CC'ing the autoconf maintainer. I see 2.72-6 removing debian/patches/fix-cxx-stdcxx-test.diff but according to the debdiff it was not applied before anyway...

Aha.

https://savannah.gnu.org/support/index.php?110879

(thanks to #libreoffice-dev)

Regards,
  
  
Rene