[libmicrohttpd] Clang build fails

2018-02-21 Thread Tim Rühsen
Hi, currently, clang can't build latest master. It because of a missing prototype for MHD_init() in src/lib/init.c. Clang errors at that point while gcc just emits a warning. Anyways, this breaks building the dependency chain for Wget2 fuzzing :-( Do you make a CI build before pushing to maste

Re: [libmicrohttpd] Clang build fails

2018-02-21 Thread Christian Grothoff
Hi, Build issue should be fixed in Git now. IIRC, our CI (Buildbot) is not (yet) setup to build with clang, but also it doesn't send out proper notifications on failures in the first place, so it is right now of limited use. Help with setting up better CIs would always be welcome, albeit I perso

Re: [libmicrohttpd] Clang build fails

2018-02-21 Thread Tim Rühsen
On 02/21/2018 10:28 AM, Christian Grothoff wrote: > Hi, > > Build issue should be fixed in Git now. Thanks ! > IIRC, our CI (Buildbot) is not (yet) setup to build with clang, but also > it doesn't send out proper notifications on failures in the first place, > so it is right now of limited use.

[libmicrohttpd] 回复:Re: Any MHD_ContentReaderCallback Example Code

2018-02-21 Thread lingweicai
Thanks Christian. Can I create a MHD_response, by the crc callback to print a circleq ( a circle queue,generated with Macro functions /sys/queue.h ), my crc callback is like this : ssize_tcrc (void *cls, uint64_t pos, char *buf, size_t max){    struct circleq_user  * cq_user_ptr = cls; // if la

Re: [libmicrohttpd] Clang build fails

2018-02-21 Thread 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 have time >> and energy to make that happen, great ;-) > > Gitlab allows exactly that, bu

Re: [libmicrohttpd] Clang build fails

2018-02-21 Thread Tim Ruehsen
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 > > >