Re: Problems with haproxy 1.7.3 on FreeBSD 11.0-p8

> On 15 Mar 2017, at 00:17, Willy Tarreau wrote: > > Matthias, > > I could finally track the problem down to a 5-year old bug in the > connection handler. It already used to affect Unix sockets but it > requires so rare a set of options and even then its occurrence rate > is so

Re: HaProxy Hang

e https://www.mail-archive.com/haproxy@formilux.org/msg25067.html (in the same thread) > > Thanks > Dave > > On 3 March 2017 at 14:15, Dmitry Sivachenko <trtrmi...@gmail.com> wrote: > > > On 03 Mar 2017, at 17:07, David King <king.c.da...@googlemail.com> wro

Re: Problems with haproxy 1.7.3 on FreeBSD 11.0-p8

> On 12 Mar 2017, at 11:34, Matthias Fechner wrote: > > > I checked the port again and there is one patch applied to haproxy, but > it is a different file, so it should not cause the patch to fail, but > maybe can cause other problems. > --- src/hlua_fcn.c.orig 2016-12-17

Re: FreeBSD CPU Affinity

> On 16 Aug 2017, at 17:24, Mark Staudinger wrote: > > Hi Folks, > > Running HAProxy-1.7.8 on FreeBSD-11.0. Working with nbproc=2 to separate > HTTP and HTTPS portions of the config. Hello, are you installing haproxy form FreeBSD ports? I just tried your

Re: FreeBSD CPU Affinity

> On 16 Aug 2017, at 17:40, Mark Staudinger <mark.staudin...@nyi.net> wrote: > > On Wed, 16 Aug 2017 10:35:05 -0400, Dmitry Sivachenko <trtrmi...@gmail.com> > wrote: > >> Hello, >> >> are you installing haproxy form FreeBSD ports? >> >

Re: Fix building haproxy with recent LibreSSL

> On 04 Jul 2017, at 11:04, Willy Tarreau <w...@1wt.eu> wrote: > > Hi Dmitry, > > [CCing Bernard, the patch's author] > > On Mon, Jul 03, 2017 at 12:34:52AM +0300, Dmitry Sivachenko wrote: >> Hello, >> >> can you please take a look at proposed

Re: Fix building haproxy with recent LibreSSL

> On 04 Jul 2017, at 11:04, Willy Tarreau <w...@1wt.eu> wrote: > > Hi Dmitry, > > [CCing Bernard, the patch's author] > > On Mon, Jul 03, 2017 at 12:34:52AM +0300, Dmitry Sivachenko wrote: >> Hello, >> >> can you please take a look at proposed

Fix building haproxy with recent LibreSSL

Hello, can you please take a look at proposed patch to fix build of haproxy with recent version of LibreSSL? https://www.mail-archive.com/haproxy@formilux.org/msg25819.html Thanks.

Re: FreeBSD CPU Affinity

> On 16 Aug 2017, at 18:32, Olivier Houchard wrote: > > > > I think I know what's going on. > Can you try the attached patch ? > > Thanks ! > > Olivier > <0001-MINOR-Fix-CPU-usage-on-FreeBSD.patch> Also, it would be probably correct thing to check return code from

USE_GETSOCKNAME obsoleted?

Hello, in Makefile I see some logic around USE_GETSOCKNAME define. But as far as I see, in sources you use getsockname() unconditionally. Is this an obsoleted define which should be removed from Makefile? Thanks.

[PATCH]: CLEANUP/MINOR: retire obsoleted USE_GETSOCKNAME build option

Hello, this is a patch to nuke obsoleted USE_GETSOCKNAME build option. Thanks! 0001-CLEANUP-MINOR-retire-USE_GETSOCKNAME-build-option.patch Description: Binary data

How to add custom options to CFLAGS

Hello, Right now we have in the Makefile: Common CFLAGS # These CFLAGS contain general optimization options, CPU-specific optimizations # and debug flags. They may be overridden by some distributions which prefer to # set all of them at once instead of playing with the CPU and DEBUG

Re: How to add custom options to CFLAGS

> On 07 Jun 2017, at 11:41, Willy Tarreau <w...@1wt.eu> wrote: > > Hi Dmitry, > > On Sun, Jun 04, 2017 at 02:54:23PM +0300, Dmitry Sivachenko wrote: >>> Same here, and it's important not to create confusion on the way >>> CFLAGS are computed. >>>

Re: How to add custom options to CFLAGS

> On 04 Jun 2017, at 14:37, Willy Tarreau <w...@1wt.eu> wrote: > > On Sat, Jun 03, 2017 at 10:36:04AM +0200, Aleksandar Lazic wrote: >> Hi Dmitry Sivachenko, >> >> Dmitry wrote on: >> >>> Hello, >> >>> Right now we have in the

Re: [ANNOUNCE] haproxy-1.8-rc1 : the last mile

> On 01 Nov 2017, at 02:20, Willy Tarreau wrote: > > Hi all! > Hello, several new warnings from clang, some look meaningful: cc -Iinclude -Iebtree -Wall -O2 -pipe -fstack-protector -fno-strict-aliasing -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv

Re: haproxy-1.8 build failure on FreeBSD/i386 (clang)

> On 11 Feb 2018, at 13:49, Franco Fichtner <fra...@opnsense.org> wrote: > > Hi, > >> On 11. Feb 2018, at 7:05 AM, Dmitry Sivachenko <trtrmi...@gmail.com> wrote: >> >> src/proto_http.c:(.text+0x1209): undefined reference to >> `__atomic_fetch_ad

haproxy-1.8 build failure on FreeBSD/i386 (clang)

Hello, haproxy-1.8 does not build on FreeBSD/i386 (clang): src/proto_http.o: In function `http_perform_server_redirect': src/proto_http.c:(.text+0x1209): undefined reference to `__atomic_fetch_add_8' src/proto_http.o: In function `http_wait_for_request': src/proto_http.c:(.text+0x275a):

Re: haproxy-1.8 build failure on FreeBSD/i386 (clang)

> On 12 Feb 2018, at 17:37, David CARLIER wrote: > > I think I m the one behing this relatively recent change ... why not adding > in the condition the architecture ? e.g. !defined(__clang__) && > !defined(__i386__) ... something like this... > > Hope it is useful. >

Re: haproxy-1.8 build failure on FreeBSD/i386 (clang)

> On 14 February 2018 at 11:09, Dmitry Sivachenko <trtrmi...@gmail.com> wrote: >> What about this change? >> >> --- work/haproxy-1.8.4/include/common/hathreads.h 2018-02-08 >> 13:05:15.0 + >> +++ /tmp/hathreads.h2018-02-14 11:06

Re: haproxy-1.8 build failure on FreeBSD/i386 (clang)

> On 21 Feb 2018, at 16:33, David CARLIER wrote: > > Might be irrelevant idea, but is it not possible to detect it via simple code > test into the Makefile eventually ? Did you mean configure? :)

Re: Fix building without NPN support

> On 15 Feb 2018, at 17:58, Bernard Spil wrote: > > On 2018-02-15 15:03, Lukas Tribus wrote: >> Hello, >> On 15 February 2018 at 13:42, Bernard Spil wrote: >>> Hello HAProxy maintainers, >>> https://github.com/Sp1l/haproxy/tree/20180215-fix-no-NPN >>> Fix

Re: Fix building haproxy 1.8.5 with LibreSSL 2.6.4

> On 07 Apr 2018, at 17:38, Emmanuel Hocdet wrote: > > > I Andy > >> Le 31 mars 2018 à 16:43, Andy Postnikov a écrit : >> >> I used to rework previous patch from Alpinelinux to build with latest stable >> libressl >> But found no way to run tests with

Re: [ANNOUNCE] haproxy-1.9-dev3

> On 29 Sep 2018, at 21:41, Willy Tarreau wrote: > > Ah, a small change is that we now build with -Wextra after having addressed > all warnings reported up to gcc 7.3 and filtered a few useless ones. Hello, here are some warnings from clang version 6.0.0: cc -Iinclude -Iebtree -Wall -Wextra

Re: upcoming 2.0 release: freebsd-11 seem to be broken ?

> On 29 May 2019, at 13:31, Илья Шипицин wrote: > > > > ср, 29 мая 2019 г. в 15:25, Dmitry Sivachenko : > > > > On 26 May 2019, at 23:40, Илья Шипицин wrote: > > > > Hello, > > > > I added freebsd-11 to cirrus-ci > > > >

Re: upcoming 2.0 release: freebsd-11 seem to be broken ?

> On 26 May 2019, at 23:40, Илья Шипицин wrote: > > Hello, > > I added freebsd-11 to cirrus-ci > > https://cirrus-ci.com/task/5162023978008576 > > should we fix it before 2.0 release ? > BTW, latest -dev release does not build at all on FreeBSD (I tried FreeBSD-12): cc -Iinclude

compile issues on FreeBSD/i386

Hello! I am trying to compile haproxy-2.2-dev10 on FreeBSD-12/i386 (i386 is important here) with clang version 9.0.1. I get the following linker error: LD haproxy ld: error: undefined symbol: __atomic_fetch_add_8 >>> referenced by backend.c >>>

Re: [ANNOUNCE] haproxy-2.0.16

> On 17 Jul 2020, at 17:34, Christopher Faulet wrote: > > > Hi, > > HAProxy 2.0.16 was released on 2020/07/17. It added 45 new commits after > version > 2.0.15. Hello, Here are new compile problems since 2.0.14 (FreeBSD/amd64, clang version 10.0.0) 1) new warnings: src/log.c:1692:10:

Re: [ANNOUNCE] haproxy-2.0.16

> On 18 Jul 2020, at 12:40, Илья Шипицин wrote: > > What is freebsd version? > It was 13.0-CURRENT, but after you asked I also tried 12.1-STABLE (clang version is also 10.0.0): the same warnings/error.

fetching layer 7 samples with tcp mode frontend

Hello! Consider the following config excerpt: frontend test-fe mode tcp use_backend test-be1 if { path -i -m end /set } What is the notion of "path" sample at frontend working in TCP mode? We experimented with haproxy-1.5.18 on Linux sending HTTP queries with path ending with "/set"

Re: [ANNOUNCE] haproxy-2.3.7

> On 16 Mar 2021, at 18:01, Christopher Faulet wrote: > > Hi, > > HAProxy 2.3.7 was released on 2021/03/16. It added 62 new commits > after version 2.3.6. > > This release is mainly about two subjects : The fix of bugs into the > resolvers part, mainly revealed since the last release and

Re: [ANNOUNCE] haproxy-2.3.7

> On 19 Mar 2021, at 19:13, Willy Tarreau wrote: > > > Grrr... And C compiler authors are still wondering why people hate C > when it's that their compilers are this pedantic :-( > > Could you please try to append a 'U' after "0x8000" in > include/haproxy/task-t.h, > like this: > >

Re: [ANNOUNCE] haproxy-2.5-dev7

> On 12 Sep 2021, at 13:06, Willy Tarreau wrote: > > Hi, > > HAProxy 2.5-dev7 was released on 2021/09/12. It added 39 new commits > after version 2.5-dev6. Hello, there is a new warning in -dev branch (on FreeBSD): admin/halog/fgets2.c:38:30: warning: '__GLIBC__' is not defined,

Re: [ANNOUNCE] haproxy-2.4.9

On 24 Nov 2021, at 12:57, Christopher Faulet wrote: > > > Hi, > > HAProxy 2.4.9 was released on 2021/11/23. It added 36 new commits > after version 2.4.8. > Hello, version 2.4.9 fails to build with OpenSSL turned off: src/server.c:207:51: error: no member named 'ssl_ctx' in 'struct

Re: [ANNOUNCE] haproxy-2.4.9

> On 25 Nov 2021, at 13:09, Willy Tarreau wrote: > > Please try the two attached patches. They re-backport something that > we earlier failed to backport that simplifies the ugly ifdefs everywhere > that virtually break every single backport related to SSL. > > For me they work with/without

Re: [ANNOUNCE] haproxy-2.4.9

> On 25 Nov 2021, at 13:29, Amaury Denoyelle wrote: > > Dmitry, the patches that Willy provided you should fix the issue. Now, > do you need a 2.4.10 to be emitted early with it or is it possible for > you to keep the patches in your tree so we can have a more substantial > list of change for

Fix haproxy build on recent FreeBSD

tch to fix that.Please consider including it into the tree.Thanks. patch-src_tools.c Description: Binary data Begin forwarded message:From: Brooks Davis Subject: Re: About libc/libsys splitDate: 28 February 2024, 21:59:36 GMT+3To: Dmitry Sivachenko The attached patch is a more correct solution.  haprox

<    1   2