Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-04 Thread Willy Tarreau
On Thu, Apr 04, 2019 at 12:48:55PM +, Overbey, Patrick (Sioux Falls) wrote:
> That worked great. Thanks Willy!

Nice, thanks for your feedback!
Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-04 Thread Overbey, Patrick (Sioux Falls)
That worked great. Thanks Willy!

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, April 03, 2019 10:01 PM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




On Wed, Apr 03, 2019 at 09:49:34PM +, Overbey, Patrick (Sioux Falls) wrote:
> Actually, here is the error. The warning was just the last thing that printed 
> to the screen.
>
> In file included from /usr/include/netinet/tcp.h:113,
>  from include/common/compat.h:32,
>  from src/connection.c:15:
> src/connection.c: In function 'conn_recv_netscaler_cip':
> src/connection.c:792:10: error: expected '=', ',', ';', 'asm' or 
> '__attribute__' before '.' token
>   uint8_t ip_v;
>   ^~~~
> src/connection.c:792:10: error: expected expression before '.' token
> src/connection.c:860:2: error: 'ip_ff' undeclared (first use in this 
> function); did you mean 'ip_fv'?
>   ip_v = (*line & 0xf0) >> 4;

Ah so I forgot to backport a few AIX-specific patches! And I'm seeing that I 
somewhat messed up with the unsetenv fix as the define on the command line was 
included as part of a previous one. I'm sorry, that's fixed now. Let's try 
again :-)

Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Willy Tarreau
On Wed, Apr 03, 2019 at 09:49:34PM +, Overbey, Patrick (Sioux Falls) wrote:
> Actually, here is the error. The warning was just the last thing that printed 
> to the screen.
> 
> In file included from /usr/include/netinet/tcp.h:113,
>  from include/common/compat.h:32,
>  from src/connection.c:15:
> src/connection.c: In function 'conn_recv_netscaler_cip':
> src/connection.c:792:10: error: expected '=', ',', ';', 'asm' or 
> '__attribute__' before '.' token
>   uint8_t ip_v;
>   ^~~~
> src/connection.c:792:10: error: expected expression before '.' token
> src/connection.c:860:2: error: 'ip_ff' undeclared (first use in this 
> function); did you mean 'ip_fv'?
>   ip_v = (*line & 0xf0) >> 4;

Ah so I forgot to backport a few AIX-specific patches! And I'm seeing
that I somewhat messed up with the unsetenv fix as the define on the
command line was included as part of a previous one. I'm sorry, that's
fixed now. Let's try again :-)

Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Overbey, Patrick (Sioux Falls)
Actually, here is the error. The warning was just the last thing that printed 
to the screen.

In file included from /usr/include/netinet/tcp.h:113,
 from include/common/compat.h:32,
 from src/connection.c:15:
src/connection.c: In function 'conn_recv_netscaler_cip':
src/connection.c:792:10: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '.' token
  uint8_t ip_v;
  ^~~~
src/connection.c:792:10: error: expected expression before '.' token
src/connection.c:860:2: error: 'ip_ff' undeclared (first use in this function); 
did you mean 'ip_fv'?
  ip_v = (*line & 0xf0) >> 4;
  ^~~~

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, April 03, 2019 3:50 PM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




On Wed, Apr 03, 2019 at 08:40:35PM +, Overbey, Patrick (Sioux Falls) wrote:
> It looks the same to me. Thanks.
>
> In file included from src/connection.c:17:
> src/connection.c: In function '__initcb_1302':
> include/common/initcall.h:128:11: warning: cast between incompatible 
> function ty

At least the line has changed, indicating that the macro correctly made its way 
to the code. I need to scratch my head now.


> pes from 'void (*)(struct sample_fetch_kw_list *)' to 'void (*)(void 
> *, void *, void *)' [-Wcast-function-type]
>.fct  = (void (*)(void *,void *,void *))function,  \
>^
> include/common/initcall.h:146:2: note: in expansion of macro 
> '__DECLARE_INITCALL '
>   __DECLARE_INITCALL(__VA_ARGS__)
>   ^~
> include/common/initcall.h:158:2: note: in expansion of macro 
> '_DECLARE_INITCALL'
>
>   _DECLARE_INITCALL(stage, __LINE__, function, arg1, 0, 0)
>   ^
> src/connection.c:1302:1: note: in expansion of macro 'INITCALL1'
>  INITCALL1(STG_REGISTER, sample_register_fetches, 
> _fetch_keywords);  ^
> gmake: *** [Makefile:996: src/connection.o] Error 1

Note, I'm only seeing a warning and not the error here. So I don't understand 
why the compilation stopped. And I don't understand why the warning above 
wasn't automatically disabled since the compiler supports it.

Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Willy Tarreau
On Wed, Apr 03, 2019 at 08:40:35PM +, Overbey, Patrick (Sioux Falls) wrote:
> It looks the same to me. Thanks.
> 
> In file included from src/connection.c:17:
> src/connection.c: In function '__initcb_1302':
> include/common/initcall.h:128:11: warning: cast between incompatible function 
> ty

At least the line has changed, indicating that the macro correctly made its
way to the code. I need to scratch my head now.


> pes from 'void (*)(struct sample_fetch_kw_list *)' to 'void (*)(void *, void 
> *,
> void *)' [-Wcast-function-type]
>.fct  = (void (*)(void *,void *,void *))function,  \
>^
> include/common/initcall.h:146:2: note: in expansion of macro 
> '__DECLARE_INITCALL
> '
>   __DECLARE_INITCALL(__VA_ARGS__)
>   ^~
> include/common/initcall.h:158:2: note: in expansion of macro 
> '_DECLARE_INITCALL'
> 
>   _DECLARE_INITCALL(stage, __LINE__, function, arg1, 0, 0)
>   ^
> src/connection.c:1302:1: note: in expansion of macro 'INITCALL1'
>  INITCALL1(STG_REGISTER, sample_register_fetches, _fetch_keywords);
>  ^
> gmake: *** [Makefile:996: src/connection.o] Error 1

Note, I'm only seeing a warning and not the error here. So I don't understand
why the compilation stopped. And I don't understand why the warning above wasn't
automatically disabled since the compiler supports it.

Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Overbey, Patrick (Sioux Falls)
It looks the same to me. Thanks.

In file included from src/connection.c:17:
src/connection.c: In function '__initcb_1302':
include/common/initcall.h:128:11: warning: cast between incompatible function ty
pes from 'void (*)(struct sample_fetch_kw_list *)' to 'void (*)(void *, void *,
void *)' [-Wcast-function-type]
   .fct  = (void (*)(void *,void *,void *))function,  \
   ^
include/common/initcall.h:146:2: note: in expansion of macro '__DECLARE_INITCALL
'
  __DECLARE_INITCALL(__VA_ARGS__)
  ^~
include/common/initcall.h:158:2: note: in expansion of macro '_DECLARE_INITCALL'

  _DECLARE_INITCALL(stage, __LINE__, function, arg1, 0, 0)
  ^
src/connection.c:1302:1: note: in expansion of macro 'INITCALL1'
 INITCALL1(STG_REGISTER, sample_register_fetches, _fetch_keywords);
 ^
gmake: *** [Makefile:996: src/connection.o] Error 1

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, April 03, 2019 3:34 PM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




On Wed, Apr 03, 2019 at 08:20:50PM +, Overbey, Patrick (Sioux Falls) wrote:
> Sorry, Willy. I'm still having the same troubles after the changes.

Then there's something I'm missing because it works for me here (with and 
without the option, I verified that I had different symbols in the output), and 
in addition the reported line number in initcall.h (105) belongs to the case 
where USE_OBSOLETE_LINKER is *not* defined.

Could you please double-check and send again the copy of the error you get with 
this latest commit ? It might look similar but be slightly different, 
indicating something else is needed.

Thanks,
Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Willy Tarreau
On Wed, Apr 03, 2019 at 08:20:50PM +, Overbey, Patrick (Sioux Falls) wrote:
> Sorry, Willy. I'm still having the same troubles after the changes.

Then there's something I'm missing because it works for me here (with and
without the option, I verified that I had different symbols in the output),
and in addition the reported line number in initcall.h (105) belongs to the
case where USE_OBSOLETE_LINKER is *not* defined.

Could you please double-check and send again the copy of the error you get
with this latest commit ? It might look similar but be slightly different,
indicating something else is needed.

Thanks,
Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Overbey, Patrick (Sioux Falls)
Sorry, Willy. I'm still having the same troubles after the changes.

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, April 03, 2019 3:10 PM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




Hi Patrick,

On Wed, Apr 03, 2019 at 03:32:23PM +, Overbey, Patrick (Sioux Falls) wrote:
> Hi Willy,
> I brought down haproxy-1.9-1483198 through git, but am getting 
> expansion of macro errors during the compile using the same compile 
> script that works with 2.0. Any ideas what's wrong?
(...)

Oh I know, it's because I'm stupid, but that's fixed now (the bug, not my 
stupidity unfortunately). In 2.0 all the USE_* macros are automatically passed 
to compiler options. In 1.9 we have to explicitly append them in the makefile. 
And guess what I forgot to add ? :-)

It's OK for me with commit 01a2c4 now.

Thanks for reporting this, and sorry for the confusion!
Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Willy Tarreau
Hi Patrick,

On Wed, Apr 03, 2019 at 03:32:23PM +, Overbey, Patrick (Sioux Falls) wrote:
> Hi Willy,
> I brought down haproxy-1.9-1483198 through git, but am getting expansion of
> macro errors during the compile using the same compile script that works with
> 2.0. Any ideas what's wrong?
(...)

Oh I know, it's because I'm stupid, but that's fixed now (the bug, not
my stupidity unfortunately). In 2.0 all the USE_* macros are automatically
passed to compiler options. In 1.9 we have to explicitly append them in
the makefile. And guess what I forgot to add ? :-)

It's OK for me with commit 01a2c4 now.

Thanks for reporting this, and sorry for the confusion!
Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Overbey, Patrick (Sioux Falls)
Hi Willy,
I brought down haproxy-1.9-1483198 through git, but am getting expansion of 
macro errors during the compile using the same compile script that works with 
2.0. Any ideas what's wrong?

For example, I ran "gmake -B CFLAGS="-maix64" LDFLAGS="-maix64" TARGET=aix52 
USE_OPENSSL=1 USE_ZLIB=1 2>&1 | tee haproxy-make.log" :

In file included from src/connection.c:17:
include/common/initcall.h:105:10: warning: cast between incompatible function ty
pes from 'void (*)(struct sample_fetch_kw_list *)' to 'void (*)(void *, void *,
void *)' [-Wcast-function-type]
   .fct = (void (*)(void *,void *,void *))function,   \
  ^
include/common/initcall.h:146:2: note: in expansion of macro '__DECLARE_INITCALL
'
  __DECLARE_INITCALL(__VA_ARGS__)
  ^~
include/common/initcall.h:158:2: note: in expansion of macro '_DECLARE_INITCALL'

  _DECLARE_INITCALL(stage, __LINE__, function, arg1, 0, 0)
  ^
src/connection.c:1302:1: note: in expansion of macro 'INITCALL1'
 INITCALL1(STG_REGISTER, sample_register_fetches, _fetch_keywords);
 ^
gmake: *** [Makefile:991: src/connection.o] Error 1


Thanks.

Patrick Overbey
Fiserv


-Original Message-
From: Overbey, Patrick (Sioux Falls) 
Sent: Wednesday, April 03, 2019 7:53 AM
To: Willy Tarreau 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: RE: Upcoming haproxy build fixes for Cygwin & AIX

Great. Thank you Willy.

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, April 03, 2019 1:18 AM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




Hi Patrick,

On Mon, Apr 01, 2019 at 09:27:46PM +, Overbey, Patrick (Sioux Falls) wrote:
> Thanks. Can you let me know when the change is ported back to 1.9?

OK so this is now in the 1.9-maint branch (commit 3349375). You can retrieve it 
with git, or if you wait another day you'll get a nightly snapshot in the 
download directory. In absence of pending bugs, I don't think there will be 
another 1.9 release before week.

Regards,
Willy


RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Overbey, Patrick (Sioux Falls)
Great. Thank you Willy.

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, April 03, 2019 1:18 AM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




Hi Patrick,

On Mon, Apr 01, 2019 at 09:27:46PM +, Overbey, Patrick (Sioux Falls) wrote:
> Thanks. Can you let me know when the change is ported back to 1.9?

OK so this is now in the 1.9-maint branch (commit 3349375). You can retrieve it 
with git, or if you wait another day you'll get a nightly snapshot in the 
download directory. In absence of pending bugs, I don't think there will be 
another 1.9 release before week.

Regards,
Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-03 Thread Willy Tarreau
Hi Patrick,

On Mon, Apr 01, 2019 at 09:27:46PM +, Overbey, Patrick (Sioux Falls) wrote:
> Thanks. Can you let me know when the change is ported back to 1.9?

OK so this is now in the 1.9-maint branch (commit 3349375). You can
retrieve it with git, or if you wait another day you'll get a nightly
snapshot in the download directory. In absence of pending bugs, I don't
think there will be another 1.9 release before week.

Regards,
Willy



Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-02 Thread Willy Tarreau
Hi Jeffrey,

On Tue, Apr 02, 2019 at 02:52:01PM +0800, Jeffrey Chen wrote:
> Hi Willy,
> I have test in cygwin, there haven't problem now.

Many thanks for your feedback, much appreciated. Then given that this
patch series fix the issue for both of you guys I'll backport it.

Thanks!
Willy



Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-02 Thread Jeffrey Chen
Hi Willy,
I have test in cygwin, there haven't problem now.
Thanks.

Jeffrey

Willy Tarreau  於 2019年4月1日 週一 下午3:06寫道:

> On Mon, Apr 01, 2019 at 09:04:06AM +0800, ??? wrote:
> > Many thanks Willy, I will wait and to try and study your patch.
>
> You're welcome.
>
> So I've just pushed the latest fixes to the master branch.
> What I've done is the following :
>
>   - enabled the new USE_OBSOLETE_LINKER option on both flavors of AIX
> and on cygwin by default since we know the linker doesn't provide
> our section start/end pointers there ;
>
>   - enabled USE_PRIVATE_CACHE on aix51 because it complained about
> missing symbols like __sync_sub_and_fetch_4. If on more recent
> AIX or on Cygwin you experience this, you'll have to add
> USE_PRIVATE_CACHE=1 as well (then let me know so that I can update
> the default build options)
>
>   - added a few defines on the CFLAGS to build on aix51 :
>   -Dss_family=__ss_family -Dip6_hdr=ip6hdr -DSTEVENS_API \
>   -D_LINUX_SOURCE_COMPAT -Dunsetenv=my_unsetenv
> => you may or may not need some of them on a more recent AIX version.
>On cygwin, maybe unsetenv will be needed, I don't know.
>
> You need to have at least commit 13d9b023 in your repository for this to
> be available. Once we figure all the required options for you to get this
> version to build, I'll backport them to 1.9.
>
> I managed to build this version with openssl 1.0.2 support on a very
> old Power3/333 MHz running AIX 5.1 and to run an H2 test. This sounds
> a bit like an anachronism though :-)
>
> Cheers,
> Willy
>


RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Overbey, Patrick (Sioux Falls)
Thanks. Can you let me know when the change is ported back to 1.9?

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Monday, April 01, 2019 3:23 PM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




On Mon, Apr 01, 2019 at 07:50:20PM +, Overbey, Patrick (Sioux Falls) wrote:
> Not really necessary since "aix52" works. Production servers should really be 
> AIX 7.1+ anyway.

OK, thanks for the info.

Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Willy Tarreau
On Mon, Apr 01, 2019 at 07:50:20PM +, Overbey, Patrick (Sioux Falls) wrote:
> Not really necessary since "aix52" works. Production servers should really be 
> AIX 7.1+ anyway.

OK, thanks for the info.

Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Overbey, Patrick (Sioux Falls)
Not really necessary since "aix52" works. Production servers should really be 
AIX 7.1+ anyway.

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Monday, April 01, 2019 2:48 PM
To: Overbey, Patrick (Sioux Falls) 
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




On Mon, Apr 01, 2019 at 07:05:04PM +, Overbey, Patrick (Sioux Falls) wrote:
> I was able to compile HA-Proxy version 2.0-dev2-ce4ec50 2019/04/01 with these 
> options using an AIX 6.1.9 system and openssl 1.0.2q. Thank you!
>
> gmake CFLAGS="-maix64" LDFLAGS="-maix64" TARGET=aix52 USE_OPENSSL=1 
> USE_PCRE=1 USE_ZLIB=1

Excellent! Do you want me to add an "aix61" target with these flags, as I guess 
all AIX 6 will require -maix64 anyway ?

Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Willy Tarreau
On Mon, Apr 01, 2019 at 07:05:04PM +, Overbey, Patrick (Sioux Falls) wrote:
> I was able to compile HA-Proxy version 2.0-dev2-ce4ec50 2019/04/01 with these 
> options using an AIX 6.1.9 system and openssl 1.0.2q. Thank you!
> 
> gmake CFLAGS="-maix64" LDFLAGS="-maix64" TARGET=aix52 USE_OPENSSL=1 
> USE_PCRE=1 USE_ZLIB=1

Excellent! Do you want me to add an "aix61" target with these flags,
as I guess all AIX 6 will require -maix64 anyway ?

Willy



RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Overbey, Patrick (Sioux Falls)
I was able to compile HA-Proxy version 2.0-dev2-ce4ec50 2019/04/01 with these 
options using an AIX 6.1.9 system and openssl 1.0.2q. Thank you!

gmake CFLAGS="-maix64" LDFLAGS="-maix64" TARGET=aix52 USE_OPENSSL=1 USE_PCRE=1 
USE_ZLIB=1

Patrick Overbey
Fiserv


-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Monday, April 01, 2019 2:06 AM
To: maio...@gmail.com; Overbey, Patrick (Sioux Falls) 

Cc: haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




On Mon, Apr 01, 2019 at 09:04:06AM +0800, ??? wrote:
> Many thanks Willy, I will wait and to try and study your patch.

You're welcome.

So I've just pushed the latest fixes to the master branch.
What I've done is the following :

  - enabled the new USE_OBSOLETE_LINKER option on both flavors of AIX
and on cygwin by default since we know the linker doesn't provide
our section start/end pointers there ;

  - enabled USE_PRIVATE_CACHE on aix51 because it complained about
missing symbols like __sync_sub_and_fetch_4. If on more recent
AIX or on Cygwin you experience this, you'll have to add
USE_PRIVATE_CACHE=1 as well (then let me know so that I can update
the default build options)

  - added a few defines on the CFLAGS to build on aix51 :
  -Dss_family=__ss_family -Dip6_hdr=ip6hdr -DSTEVENS_API \
  -D_LINUX_SOURCE_COMPAT -Dunsetenv=my_unsetenv
=> you may or may not need some of them on a more recent AIX version.
   On cygwin, maybe unsetenv will be needed, I don't know.

You need to have at least commit 13d9b023 in your repository for this to be 
available. Once we figure all the required options for you to get this version 
to build, I'll backport them to 1.9.

I managed to build this version with openssl 1.0.2 support on a very old 
Power3/333 MHz running AIX 5.1 and to run an H2 test. This sounds a bit like an 
anachronism though :-)

Cheers,
Willy


Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Aleksandar Lazic
Am 01.04.2019 um 15:15 schrieb Willy Tarreau:
> On Mon, Apr 01, 2019 at 03:04:24PM +0200, Aleksandar Lazic wrote:
>>> I managed to build this version with openssl 1.0.2 support on a very
>>> old Power3/333 MHz running AIX 5.1 and to run an H2 test. This sounds
>>> a bit like an anachronism though :-)
>>
>> 8-O
>>
>> https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=D700454U98638U83
>>
>> EOS: 01-Apr-2006
>>
>> As for today the Support ends *exactly* 12 Years ago.
>> At this time H2 wasn't on any Roadmap and now with HAProxy this platform gets
>> the shiny new H2 technology ;-)))
>>
>> Maybe OS/2 is the next platform.
>>
>> https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=F827166B21756H28
>> EOS 31-Dec-2006
> 
> I have been wondering if it was worth emitting an april's fool around
> all this support for dead platforms but I feared it would revive some
> feature requests, and with users complaining that haproxy ate all their
> PDP-11's memory :-)

and expected 1000 r/s ;-)

> Willy
> 




Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Willy Tarreau
On Mon, Apr 01, 2019 at 03:04:24PM +0200, Aleksandar Lazic wrote:
> > I managed to build this version with openssl 1.0.2 support on a very
> > old Power3/333 MHz running AIX 5.1 and to run an H2 test. This sounds
> > a bit like an anachronism though :-)
> 
> 8-O
> 
> https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=D700454U98638U83
> 
> EOS: 01-Apr-2006
> 
> As for today the Support ends *exactly* 12 Years ago.
> At this time H2 wasn't on any Roadmap and now with HAProxy this platform gets
> the shiny new H2 technology ;-)))
> 
> Maybe OS/2 is the next platform.
> 
> https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=F827166B21756H28
> EOS 31-Dec-2006

I have been wondering if it was worth emitting an april's fool around
all this support for dead platforms but I feared it would revive some
feature requests, and with users complaining that haproxy ate all their
PDP-11's memory :-)

Willy



Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Aleksandar Lazic
Am 01.04.2019 um 09:06 schrieb Willy Tarreau:
> On Mon, Apr 01, 2019 at 09:04:06AM +0800, ??? wrote:
>> Many thanks Willy, I will wait and to try and study your patch.
> 
> You're welcome.

[good infos snipped]

> I managed to build this version with openssl 1.0.2 support on a very
> old Power3/333 MHz running AIX 5.1 and to run an H2 test. This sounds
> a bit like an anachronism though :-)

8-O

https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=D700454U98638U83

EOS: 01-Apr-2006

As for today the Support ends *exactly* 12 Years ago.
At this time H2 wasn't on any Roadmap and now with HAProxy this platform gets
the shiny new H2 technology ;-)))

Maybe OS/2 is the next platform.

https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=F827166B21756H28
EOS 31-Dec-2006

> Cheers,
> Willy

Cheers,
Aleks



Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-04-01 Thread Willy Tarreau
On Mon, Apr 01, 2019 at 09:04:06AM +0800, ??? wrote:
> Many thanks Willy, I will wait and to try and study your patch.

You're welcome.

So I've just pushed the latest fixes to the master branch.
What I've done is the following :

  - enabled the new USE_OBSOLETE_LINKER option on both flavors of AIX
and on cygwin by default since we know the linker doesn't provide
our section start/end pointers there ;

  - enabled USE_PRIVATE_CACHE on aix51 because it complained about
missing symbols like __sync_sub_and_fetch_4. If on more recent
AIX or on Cygwin you experience this, you'll have to add
USE_PRIVATE_CACHE=1 as well (then let me know so that I can update
the default build options)

  - added a few defines on the CFLAGS to build on aix51 :
  -Dss_family=__ss_family -Dip6_hdr=ip6hdr -DSTEVENS_API \
  -D_LINUX_SOURCE_COMPAT -Dunsetenv=my_unsetenv
=> you may or may not need some of them on a more recent AIX version.
   On cygwin, maybe unsetenv will be needed, I don't know.

You need to have at least commit 13d9b023 in your repository for this to
be available. Once we figure all the required options for you to get this
version to build, I'll backport them to 1.9.

I managed to build this version with openssl 1.0.2 support on a very
old Power3/333 MHz running AIX 5.1 and to run an H2 test. This sounds
a bit like an anachronism though :-)

Cheers,
Willy



Re: Upcoming haproxy build fixes for Cygwin & AIX

2019-03-31 Thread 陳喵喵
Many thanks Willy, I will wait and to try and study your patch.

Jeffrey

Willy Tarreau  於 2019年3月30日 週六 上午5:01寫道:

> Hi,
>
> I finally could figure how to work around the issues with very old
> linkers. I could work on this using a very old AIX machine we have
> here running AIX 5.1, so now that my test code works on it, I'm
> fairly confident more recent versions will as well, and given that
> Jeffrey's errors on Cygwin where the same, I think it's all that's
> missing there as well.
>
> I'll clean up my patches this week-end or on Monday and will ask you
> to give them a try. I'll merge them into 2.0 to make it easier for you
> to test, and will backport them to 1.9 once you confirm the issue is
> gone for you as well.
>
> I suspect Solaris versions older than 10 will need the same workaround
> as well, but it will only be a matter of adding a build option, which
> will be easy. I can't test there, my old Ultra5 is really sick...
>
> So stay tuned!
> Willy
>


RE: Upcoming haproxy build fixes for Cygwin & AIX

2019-03-29 Thread Overbey, Patrick (Sioux Falls)
Wow. Really appreciate you following up. Thanks Willy!

Patrick Overbey
Fiserv

-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Friday, March 29, 2019 4:01 PM
To: maio...@gmail.com; Overbey, Patrick (Sioux Falls) 

Cc: haproxy@formilux.org
Subject: Upcoming haproxy build fixes for Cygwin & AIX

  ⚠ EXTERNAL MESSAGE – Think Before You Click




Hi,

I finally could figure how to work around the issues with very old linkers. I 
could work on this using a very old AIX machine we have here running AIX 5.1, 
so now that my test code works on it, I'm fairly confident more recent versions 
will as well, and given that Jeffrey's errors on Cygwin where the same, I think 
it's all that's missing there as well.

I'll clean up my patches this week-end or on Monday and will ask you to give 
them a try. I'll merge them into 2.0 to make it easier for you to test, and 
will backport them to 1.9 once you confirm the issue is gone for you as well.

I suspect Solaris versions older than 10 will need the same workaround as well, 
but it will only be a matter of adding a build option, which will be easy. I 
can't test there, my old Ultra5 is really sick...

So stay tuned!
Willy


Upcoming haproxy build fixes for Cygwin & AIX

2019-03-29 Thread Willy Tarreau
Hi,

I finally could figure how to work around the issues with very old
linkers. I could work on this using a very old AIX machine we have
here running AIX 5.1, so now that my test code works on it, I'm
fairly confident more recent versions will as well, and given that
Jeffrey's errors on Cygwin where the same, I think it's all that's
missing there as well.

I'll clean up my patches this week-end or on Monday and will ask you
to give them a try. I'll merge them into 2.0 to make it easier for you
to test, and will backport them to 1.9 once you confirm the issue is
gone for you as well.

I suspect Solaris versions older than 10 will need the same workaround
as well, but it will only be a matter of adding a build option, which
will be easy. I can't test there, my old Ultra5 is really sick...

So stay tuned!
Willy