>> I suggest to resort for adding -DOPENSSL_USE_IPV6=0 at config time. I
>> couldn't reproduce the problem on two different systems, so it's some
>> problem with yours.
> 
> What system(s) are you testing on?

We have discussed it earlier, 5.1. And was under impression that you
target 5.1 too. You had older compiler, but system headers should have
been same.

> Mine is "Digital UNIX V4.0G (Rev. 1530)".

Even more reason to resort additional argument. I mean if something is
broken and/or is not up to contemporary standard, why is it source code
that is expected to be twisted to accommodate outdated system? When it's
possible to work around the problem without modifying code.

>> It's being discussed internally. BTW, defining inline with
>> defined(__DECC) is formally incorrect, because DEC C *would* accept
>> inline if you pass -c99.
> 
>     $ which cc
>     /usr/ccs/bin/cc
> 
>     $ cc -c hello.c
>     cc: Error: hello.c, line 1: Missing ";". (nosemi)
>     static inline int foofunc(void)
>     --------------^
> 
>     $ cc -c99 -c hello.c
>     cc: Error: hello.c, line 1: Missing ";". (nosemi)
>     static inline int foofunc(void)
>     --------------^

Works for me with C V6.5. inline is part of C99, so that if compiler
accepts -c99 and fails to compile recognize inline as keyword, it's
formally a bug. So that guarding with __DECC alone is still formally
inappropriate.

>> You mentioned "I am building with non-default arguments" but never
>> specified which ones.
> 
> That was previously. This time, I just used whatever ./config gave me,
> to make the bug-reporting easier.

And you still don't provide coherent problem description. I mean last
time it was "problem with non-specified argument on 5.1", now "it's on
4.0". There is no place for guessing and implying in bug reports.

Well, formally speaking defining _XOPEN_SOURCE in the middle is
inappropriate. Such macros should be defined first... But it wasn't me
who added it, so I don't know the rationale...


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to