Hi Nilesh, Nilesh Patra, on 2021-10-22: > looks like C++17 has removed the provision to specify custom > exceptions, and there are a lot of errors like the one above. > In this case, does it makes sense to force C++14 standard > (with chnages in d/rules or with patches) in such cases and > ask upstream to clean these up? Or do I miss a relatively easy > solutions? It depends. If I read correctly the porting guide to Gcc 11 [1] and if the number of occurrence of the issue is reasonable, then you can just patch the throw(BadOptionSetting) occurrences to replace them by noexcept(false). If the number of occurrences is too high to make a patch viable, then similarly to mothur, the advice from Aaron M. Ucko applies: informing upstream and temporarily getting back to C++14 is probably the saner course of action. [1]: https://gcc.gnu.org/gcc-11/porting_to.html In hope this helps, Have a nice day, :) -- Étienne Mollier <emollier@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity.
Attachment:
signature.asc
Description: PGP signature