Re: strnstr errors in tests while on NetBSD

2021-01-26 Thread Riccardo Mottola
Hi, Riccardo Mottola wrote: > The situation on NetBSD/amd64/libobj2 s now: > > 7767 Passed tests >   46 Failed files >   32 Dashed hopes >    8 Failed tests > > > The situation on NetBSD/sparc64/gcc is now: > > 9398 Passed tests >   54 Failed tests >   46 Dashed hopes >   14 Skipped sets On NetBS

Re: strnstr errors in tests while on NetBSD

2021-01-26 Thread Riccardo Mottola
Hi Richard, Richard Frith-Macdonald wrote: > I don't know how that could fail 'many tests', because the only place in the > entire sourcecode that uses strnstr is the GSMime tests. > For that file, I simply changed the local function name to avoid conflict > with the BSD function. ineed there a

Re: strnstr errors in tests while on NetBSD

2021-01-22 Thread Richard Frith-Macdonald
> On 22 Jan 2021, at 07:26, Riccardo Mottola wrote: > > Hi, > > while building tests on NetBSD/sparc I saw that many tests failed for > this reason: > > build.m:7:1: error: conflicting types for 'strnstr' > strnstr(const uint8_t *buf, unsigned len, const uint8_t *str) > ^ > In file include

strnstr errors in tests while on NetBSD

2021-01-21 Thread Riccardo Mottola
Hi, while building tests on NetBSD/sparc I saw that many tests failed for this reason: build.m:7:1: error: conflicting types for 'strnstr'  strnstr(const uint8_t *buf, unsigned len, const uint8_t *str)  ^ In file included from /home/multix/gnustep-svc/libs-base/Headers/GNUstepBase/GSConfig.h:430: