> From: Michael Wojcik
> Sent: Friday, 1 April, 2022 15:41
> >
> > View results: https://github.com/openssl/openssl/actions/runs/2073285321
>
> I'll take a look when I get a chance to see if anything jumps out. I
> haven't had to deal with IPv6 raw or UDP programming in Windows yet, but I
> do a
> From: openssl-users On Behalf Of
> Michael Richardson
> Sent: Friday, 1 April, 2022 07:34
>
> Attempts to make bss_dgram.c compile with the right IPv6 include for
> Windows
> are not going well.
>
> Some of the jobs actually die before my test case even runs, but at least,
> I
> guess they
> From: Michael Richardson
> Sent: Friday, 1 April, 2022 07:40
>
> Michael Wojcik wrote:
> > Actually, in the context of #if expressions, unrecognized tokens
> expand to 0 anyway:
>
> > After all replacements due to macro expansion and the defined unary
> > operator have been
Hello,
Connection between a Openssl 3.0.2 server and a 1.1.1g client is proving to be
unsuccessful.
According to the logs collected we seem to be having an issue with the loading
of the legacy providers.
We are loading both the default and legacy providers programmatically as per
the steps
Michael Wojcik wrote:
> Actually, in the context of #if expressions, unrecognized tokens expand
to 0 anyway:
> After all replacements due to macro expansion and the defined unary
> operator have been performed, all remaining identifiers are replaced
> with the pp-number 0...
Attempts to make bss_dgram.c compile with the right IPv6 include for Windows
are not going well.
Some of the jobs actually die before my test case even runs, but at least, I
guess they compile bss_dgram.c
Others (the shared ones) seem to fail completely to compile bss_dgram.c
I haven't run a
