Re: Bug#984243: Help: mothur: ftbfs with GCC-11

2021-10-22 Thread Aaron M. Ucko
Andreas Tille writes: > OK, I've implemented this in my last commit. Great, thanks! > Isn't > > # Get the list of all .cpp files, rename to .o files > # > OBJECTS=$(patsubst %.cpp,%.o,$(wildcard $(addsuffix *.cpp,$(subdirs > OBJECTS+=$(patsubst %.c,%.o,$(wildcard $(addsuffix *.c,$(s

Re: disulfinder: ftbfs with GCC-11

2021-10-22 Thread Nilesh Patra
On Wed, 03 Mar 2021 16:11:37 + Matthias Klose wrote: BRNN/RNNs/Options.h:69:5: error: ISO C++17 does not allow dynamic exception specifications 69 | throw(BadOptionSetting); | ^ BRNN/RNNs/Options.h:143:5: error: ISO C++17 does not allow dynamic exception specifications 1

Re: disulfinder: ftbfs with GCC-11

2021-10-22 Thread Nilesh Patra
On 10/22/21 9:23 PM, Étienne Mollier wrote: 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 wi

Re: disulfinder: ftbfs with GCC-11

2021-10-22 Thread Étienne Mollier
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 ups