Hi Bob,
On Mon, Jun 10, 2019 at 09:54:29PM +, Zakharychev, Bob wrote:
> FWIW: after a bit of experimentation and a quick dumb behavior comparison
> program I found that FD_SET is compiled incorrectly by GCC 8.3.0 under Cygwin
> with optimization level of -O2 and up. I compared native FD_SET/FD
Willy,
> > Looks like it decided that non-letter characters had to be encoded.
> > We're using FD_ISSET() to look up the characters in the character
> > encoding map because this was convenient in the past, but maybe it's
> > time to have a native implementation of a bit address lookup and get
>On Tue, Jun 04, 2019 at 09:46:04PM +, Zakharychev, Bob wrote:
>> I mean it returns 0. What happens is that as soon as the other side
>> (haproxy) terminates, poll() starts returning immediately with
>> positive return value and POLLIN being the only flag set in
>> fd->revents as if there's
Bob,
we have added very basic cygwin CI
https://travis-ci.com/haproxy/haproxy/jobs/205561046
it is "build only". feel free to improve it :)
ср, 5 июн. 2019 г. в 02:49, Zakharychev, Bob :
> Willy,
>
> On Tue, Jun 04, 2019 at 05:52:12PM +, Zakharychev, Bob wrote:
> >> Finally got VTest compi
On Tue, Jun 04, 2019 at 09:46:04PM +, Zakharychev, Bob wrote:
> I mean it returns 0. What happens is that as soon as the other side (haproxy)
> terminates, poll() starts returning immediately with positive return value
> and POLLIN being the only flag set in fd->revents as if there's something
Willy,
On Tue, Jun 04, 2019 at 05:52:12PM +, Zakharychev, Bob wrote:
>> Finally got VTest compiling and working as expected (I think) under Cygwin.
>> config.h had to be adjusted and vtc_syslog.c needed
>> included, but nothing big. However, there's some weird poll() behavior
>> where it ne
Hi Bob,
On Tue, Jun 04, 2019 at 05:52:12PM +, Zakharychev, Bob wrote:
> Finally got VTest compiling and working as expected (I think) under Cygwin.
> config.h had to be adjusted and vtc_syslog.c needed included,
> but nothing big. However, there's some weird poll() behavior where it never
> r
\.1""
I’ve no idea why it logs literals encoded like this and what should be changed
in log configuration or maybe in build options to get it logging in expected
format.
Bob
From: Илья Шипицин
Sent: Monday, June 3, 2019 4:21 PM
To: Zakharychev, Bob
Cc: HAProxy
Subject: Re: cygw
e" resolved that
>
> cpp -v /dev/null -o /dev/null
>
>
>
> This should print the search path – we can then verify that /usr/include
> and other dirs are in it.
>
>
>
> Bob
>
>
>
> *From:* Илья Шипицин
> *Sent:* Monday, June 3, 2019 4:09 PM
>
: Илья Шипицин
Sent: Monday, June 3, 2019 4:09 PM
To: Zakharychev, Bob
Cc: HAProxy
Subject: Re: cygwin compilation error
I use the following command to build environment:
https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L10
"poll.h" is located in /usr/include
http
> ZLib, OpenSSL and Lua 5.3 by enabling corresponding flags though I didn’t
> run any tests), so something must be missing in your build environment.
> Most system headers should be in /usr/include if cygwin-devel is installed,
> so you might want to start with checking if expected header
i is an
ephemeral environment. it is built from scratch every time.
I use the following command to build environment:
https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L10
"poll.h" is located in /usr/include
https://travis-ci.com/chipitsine/haproxy/builds
xy
Subject: Re: cygwin compilation error
пн, 3 июн. 2019 г. в 20:00, Gil Bahat
mailto:bahat@gmail.com>>:
poll.h seems to be present at cygwin-devel:
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=poll.h&arch=x86_64
hope that helps.
cygwin-devel is installed
https://travis-
пн, 3 июн. 2019 г. в 20:00, Gil Bahat :
> poll.h seems to be present at cygwin-devel:
> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=poll.h&arch=x86_64
>
> hope that helps.
>
>
cygwin-devel is installed
https://travis-ci.com/chipitsine/haproxy/builds/114061737#L165-L172
> Regards,
>
> Gi
poll.h seems to be present at cygwin-devel:
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=poll.h&arch=x86_64
hope that helps.
Regards,
Gil
On Mon, Jun 3, 2019 at 5:53 PM Илья Шипицин wrote:
>
>
> пн, 3 июн. 2019 г. в 17:56, Willy Tarreau :
>
>> Hi Ilya,
>>
>> On Mon, Jun 03, 2019 at 01:57
пн, 3 июн. 2019 г. в 17:56, Willy Tarreau :
> Hi Ilya,
>
> On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote:
> > Hello, Gil Bahat!
> >
> > can you help with troubleshooting?
> >
> > I created some basic cygwin CI:
> >
> > https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L2
Hi Ilya,
On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote:
> Hello, Gil Bahat!
>
> can you help with troubleshooting?
>
> I created some basic cygwin CI:
>
> https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L25-L30
>
> it fails with
>
> src/ev_poll.c:16:10: fatal erro
I forgot to notice - haproxy is very close to 2.0 release (about 2 weeks or
so).
we wish to be sure it works on cygwin before 2.0 released
пн, 3 июн. 2019 г. в 13:57, Илья Шипицин :
> Hello, Gil Bahat!
>
> can you help with troubleshooting?
>
> I created some basic cygwin CI:
>
> https://github.c
Hello, Gil Bahat!
can you help with troubleshooting?
I created some basic cygwin CI:
https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L25-L30
it fails with
src/ev_poll.c:16:10: fatal error: poll.h: No such file or directory
#include
^~~~
compilation terminated.
mak
it turns out 1.8.20 does compile neatly, this should suffice for us for the
time being. this is also a strong indication that whatever needs fixing is
minor enough.
Gil
On Sun, May 12, 2019 at 11:12 AM Willy Tarreau wrote:
> On Sun, May 12, 2019 at 09:26:18AM +0300, Gil Bahat wrote:
> > none of
On Sun, May 12, 2019 at 09:26:18AM +0300, Gil Bahat wrote:
> none of these work for me to resolve the problem. guess it's a bit more
> complicated than that.
OK, thanks for trying at least.
willy
none of these work for me to resolve the problem. guess it's a bit more
complicated than that.
On Wed, May 8, 2019 at 8:49 AM Willy Tarreau wrote:
> Hi,
>
> On Mon, May 06, 2019 at 12:54:47PM +0300, Gil Bahat wrote:
> > Hi,
> >
> > is cygwin still supported anymore?
>
> Well, we never know :-)
Hello!
On Wed, May 08, 2019 at 10:13:38PM +, Zakharychev, Bob wrote:
> I wouldn't bother even trying to add support for BoringSSL - they themselves
> discourage people from doing so in their mission statement:
>
> "Although BoringSSL is an open source project, it is not intended for general
>
Ilya Shipitsin wrote on Wed, 08 May 2019 03:22:20 -0700:
>I guess the same would be with BoringSSL. It exposes OPENSSL_VERSION_NUMBER
>and it is not openssl itself.
>
>yes, we can add warning.
I wouldn't bother even trying to add support for BoringSSL - they themselves
discourage people from doi
ср, 8 мая 2019 г. в 14:50, Willy Tarreau :
> On Wed, May 08, 2019 at 02:06:31PM +0500, ??? wrote:
> > > Ilya, could you please instead change the test like this and test
> again :
> > >
> > > -#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x10101000L)
> > > +#if defined(USE_OPENS
On Wed, May 08, 2019 at 02:06:31PM +0500, ??? wrote:
> > Ilya, could you please instead change the test like this and test again :
> >
> > -#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x10101000L)
> > +#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x1010100fL)
> >
>
>
ср, 8 мая 2019 г. в 13:55, Willy Tarreau :
> On Wed, May 08, 2019 at 01:13:56PM +0500, ??? wrote:
> > > libressl ? My understanding of this thing is that this problem is not
> > > easy to detect by accident and causes a mess for people who reload
> often.
> > > If libressl is affected by
On Wed, May 08, 2019 at 01:13:56PM +0500, ??? wrote:
> > libressl ? My understanding of this thing is that this problem is not
> > easy to detect by accident and causes a mess for people who reload often.
> > If libressl is affected by this we probably need to find a different
> > fix. And
Frederic, can you help with some "haproxy reg test getting started" doc ?
ср, 8 мая 2019 г. в 13:13, Илья Шипицин :
>
>
> ср, 8 мая 2019 г. в 13:03, Willy Tarreau :
>
>> Hi Ilya,
>>
>> On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote:
>> > From ad9961e92c692430272c9088a49759c889dac6f
ср, 8 мая 2019 г. в 13:03, Willy Tarreau :
> Hi Ilya,
>
> On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote:
> > From ad9961e92c692430272c9088a49759c889dac6f1 Mon Sep 17 00:00:00 2001
> > From: Ilya Shipitsin
> > Date: Wed, 8 May 2019 11:32:02 +0500
> > Subject: [PATCH] BUILD: do not u
Hi Ilya,
On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote:
> From ad9961e92c692430272c9088a49759c889dac6f1 Mon Sep 17 00:00:00 2001
> From: Ilya Shipitsin
> Date: Wed, 8 May 2019 11:32:02 +0500
> Subject: [PATCH] BUILD: do not use "RAND_keep_random_devices_open" when
> building again
I messed up with commit message. One more try
ср, 8 мая 2019 г. в 11:33, Илья Шипицин :
> small fix
>
> ср, 8 мая 2019 г. в 11:12, Willy Tarreau :
>
>> On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote:
>> > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau :
>> >
>> > > On Wed, May 08, 2019 at
small fix
ср, 8 мая 2019 г. в 11:12, Willy Tarreau :
> On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote:
> > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau :
> >
> > > On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote:
> > > > travis-ci supports windows builds.
> > >
> > > cool!
On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote:
> ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau :
>
> > On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote:
> > > travis-ci supports windows builds.
> >
> > cool!
> >
>
> my current roadmap is
>
> 1) patch fixes SSL variants (alr
ср, 8 мая 2019 г. в 11:06, Willy Tarreau :
> On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote:
> > travis-ci supports windows builds.
>
> cool!
>
my current roadmap is
1) patch fixes SSL variants (already sent to list). without it we are NOT
building LibreSSL at all (i.e. we use defa
On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote:
> travis-ci supports windows builds.
cool!
> I will add such build a bit later (after
> we settle with current travis-ci fixes)
...and this cygwin build issue :-)
Willy
travis-ci supports windows builds. I will add such build a bit later (after
we settle with current travis-ci fixes)
ср, 8 мая 2019 г. в 10:52, Willy Tarreau :
> Hi,
>
> On Mon, May 06, 2019 at 12:54:47PM +0300, Gil Bahat wrote:
> > Hi,
> >
> > is cygwin still supported anymore?
>
> Well, we never
Hi,
On Mon, May 06, 2019 at 12:54:47PM +0300, Gil Bahat wrote:
> Hi,
>
> is cygwin still supported anymore?
Well, we never know :-) I mean, we're always open to fixes to make it
work as long as they don't impact other platforms.
> the target seems to be present in the
> Makefiles and I'd love
Hi,
is cygwin still supported anymore? the target seems to be present in the
Makefiles and I'd love to be able to use it. I'm running into what seems to
be a workable linker error:
$ make TARGET=cygwin
LD haproxy
src/http_act.o:http_act.c:(.rdata+0x340): multiple definition of
`.weak.ist_u
39 matches
Mail list logo
