On Saturday, December 04 2021, Petter Reinholdtsen wrote: > [Stefano Rivera] >> Presumably resolved in 2.0.0 in NEW, that doesn't use autoconf any more. > > Perhaps, but as NEW processing these days take a long time, as a user of > the library I would prefer a fix for 1.2.14-1 in the mean time. > > The easiest fix seem to be to bypass the c++ standard detector which > fail in configure.ac, causing the problematic test for C++17, while both > C++11 and C++14 would work, by adding --with-cxx-standard=14 like this: > > --- rules.orig 2021-12-04 07:42:25.578757615 +0100 > +++ rules 2021-12-04 07:37:18.662074573 +0100 > @@ -13,7 +13,8 @@ > PYTHON3=$(shell py3versions -vr) > ALLPY=$(PYTHON3) > > -CONFIGURE_ARGS = --with-libiconv > --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) > +CONFIGURE_ARGS = --with-libiconv > --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \ > + --with-cxx-standard=14 > > %: > dh $@ --with python3 > > It would also help a lot if the next upload is a source only upload.
Thanks for the patch, Petter. I agree that it's a good compromise in order to make the package build again, especially considering that version 2 is already in NEW. I tried building libtorrent-rasterbar with your patch, but found that there was yet another problem happening: its Jamfile wasn't working with Python 3.10, which is already in the archive. I went ahead and filed a bug report, and the upstream was very quick in fixing it. Anyway, the package builds locally now, so I'm going to take the liberty to upload an NMU to DELAYED/5. Andrew, feel free to remove it from the queue if you'd like to tackle this upload yourself. If/when the NMU is accepted, I will "gbp push" what I have locally so that the git repo stays in sync. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/
signature.asc
Description: PGP signature
