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

2019-05-29 Thread Dmitry Sivachenko
> 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 > > > > https://cirrus-ci.com/task/5162023978008576 > > > > should we

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

2019-05-29 Thread Илья Шипицин
ср, 29 мая 2019 г. в 15:25, Dmitry Sivachenko : > > > > 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

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

2019-05-29 Thread Dmitry Sivachenko
> 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

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

2019-05-29 Thread Илья Шипицин
ср, 29 мая 2019 г. в 07:36, Willy Tarreau : > Hi Ilya, > > On Mon, May 27, 2019 at 01:40:42AM +0500, ??? wrote: > > Hello, > > > > I added freebsd-11 to cirrus-ci > > > > https://cirrus-ci.com/task/5162023978008576 > > > > should we fix it before 2.0 release ? > > As I mentioned on the

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

2019-05-28 Thread Willy Tarreau
Hi Ilya, On Mon, May 27, 2019 at 01:40:42AM +0500, ??? wrote: > Hello, > > I added freebsd-11 to cirrus-ci > > https://cirrus-ci.com/task/5162023978008576 > > should we fix it before 2.0 release ? As I mentioned on the github issue, if you look closer to the logs, you see that it's

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

2019-05-26 Thread Илья Шипицин
Hello, I added freebsd-11 to cirrus-ci https://cirrus-ci.com/task/5162023978008576 should we fix it before 2.0 release ? cheers, Ilya Shipitsin