Am Sonntag, den 04.03.2018, 11:40 +0100 schrieb Christian Grothoff:
> Might be fixed in f60a569e..a7b25581, please let me know if not (or
> rather Evgeny, as he'll know better what to do ;-)).
Building for MinGW is not magic, here is my build script that you can
use to build the prerequisites and
> On 03/04/2018 10:34 AM, Tim Ruehsen wrote:
> > Hi,
> >
> > just saw that the wget2 MinGW build breaks since a while. Could you
> > have a look ?
> >
> > With Best Regards, Tim
> >
> >
> > In file included from internal.h:32:0,
> &g
Hi,
just saw that the wget2 MinGW build breaks since a while. Could you
have a look ?
With Best Regards, Tim
In file included from internal.h:32:0,
from action_continue.c:25:
../../src/include/microhttpd2.h: In function ‘MHD_daemon_create’:
../../src/include/microhttpd2.h:277:2
These leaks (below) seem to be the last thing to prevent the Gitlab CI
runner from succeeding. When working I can start adding an Alpine
runner (using musl instead of GNU libc).
I saw in the code that you are already doing some fuzzing.
If you are interested, I could integrate fuzzing directly wit
Am Freitag, den 02.03.2018, 22:07 +0100 schrieb Christian Grothoff:
> On 02/27/2018 10:39 AM, Tim Rühsen wrote:
> > $ CC=gcc CFLAGS="-O0 -g -ggdb3 -fno-omit-frame-pointer
> > -fsanitize=undefined" ./configure
> >
> > $ make clean
> > $ make check
> > $ grep runtime src/*/*.log
> >
> > src/microht
Am Mittwoch, den 21.02.2018, 20:38 +0100 schrieb Christian Grothoff:
> On 02/21/2018 12:15 PM, Tim Rühsen wrote:
> > > Generally, I would like
> > > to end up with a setup where the entire CI configuration is also
> > > in a
> > > Git repo and can be easily collaboratively improved. So if you
> > >
