> On 11 May 2026, at 22:50, Willy Tarreau <[email protected]> wrote:
> 
> Interesting, what was the last haproxy version that didn't cause this
> warning ? Because the last version changed very little in theory so I
> don't see what could cause a change of includes for example. We'll have
> to address it anyway, but I'm just suprised by the change.



Hmm... probably FreeBSD -dev machine I am using to compile/test was updated... 
few days ago 3.2.18 was compiling without warnings, but it is probably due to 
older FreeBSD (and bundled clang) versions...

Reply via email to