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

2021-11-08 Thread Hamid Nassiby
Hi all, The problem can be fixed following these steps: 1. Revert the commit ff8928540e0d720b8a08ee4227c1bbadc2c1e733 (now, that is the last commit). 2. Apply this patch: >--- a/Makefile >+++ b/Makefile >@@ -118,8 +118,8 @@ endif ># > OBJECTS=$(patsubst %.cpp,%.o,$(wildcard $(addsuffix

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

2021-11-08 Thread Aaron M. Ucko
Andreas Tille writes: > which has an incomplete number of arguments that is interrupted > by '/usr/bin/ld') That looks like it might simply be an artifact of different buffering policies for standard output and standard error; I expect you'll find the remainder of the command line later on.

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

2021-11-08 Thread Andreas Tille
Am Mon, Oct 25, 2021 at 09:16:30PM -0400 schrieb Aaron M. Ucko: > Andreas Tille writes: > > > I'm wondering why the makefile stopped working just because a new compiler > > version is used. :-( > > Along the way, you pulled in a new upstream version, whose makefile > evidently wasn't quite

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

2021-10-25 Thread Aaron M. Ucko
Andreas Tille writes: > I'm wondering why the makefile stopped working just because a new compiler > version is used. :-( Along the way, you pulled in a new upstream version, whose makefile evidently wasn't quite right. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)

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

2021-10-25 Thread Andreas Tille
Am Fri, Oct 22, 2021 at 07:46:35AM -0400 schrieb Aaron M. Ucko: > > # 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,$(subdirs > >

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

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

2021-10-22 Thread Andreas Tille
Hi Aaron, Am Thu, Oct 21, 2021 at 04:21:26PM -0400 schrieb Aaron M. Ucko: > > No, because std::byte supports far too few operations [1]. Instead, I'd > suggest encouraging upstream to rename their type, and meanwhile locally > patching source/uchime_src/makefile to add -std=c++14 to CXXFLAGS, >

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

2021-10-21 Thread Étienne Mollier
Hi Andreas, Andreas Tille, on 2021-10-21: > In file included from addtargets2.cpp:3: > myutils.h:176:1: error: reference to 'byte' is ambiguous Since C++ 2017, the std::byte type is defined: > 176 | byte *ReadAllStdioFile(FILE *f, off_t ); > | ^~~~ > In file included from

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

2021-10-21 Thread Aaron M. Ucko
Steffen Möller writes: > My C++ skills are a bit rosty but would removing the typedef for byte > solve the problem? No, because std::byte supports far too few operations [1]. Instead, I'd suggest encouraging upstream to rename their type, and meanwhile locally patching

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

2021-10-21 Thread Steffen Möller
On 21.10.21 20:21, Étienne Mollier wrote: Hi Andreas, Andreas Tille, on 2021-10-21: In file included from addtargets2.cpp:3: myutils.h:176:1: error: reference to 'byte' is ambiguous Since C++ 2017, the std::byte type is defined: 176 | byte *ReadAllStdioFile(FILE *f, off_t ); |

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

2021-10-21 Thread Andreas Tille
Control: tags -1 help Hi, I've solved one gcc-11 issue that was mentioned in this bug report but now there are other gcc-11 issues that go beyond my C++ knowledge: ... g++ -g -O2 -ffile-prefix-map=/build/mothur-1.46.1=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11