> Why not just write a patch to fix this and send it to the cygwin-patches
> mailing list?
I had first to make sure that the feature is indeed unsupported (and I wasn't
100% certain because it was included in the header).
Actually, nobody confirmed to me that I am not "seeing things", only taugh
On 7/31/2019 5:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>> Linux and BSD options are not available, whatever the .h #defines.
>
> Unsupported options should not be shown as features in the headers.
Why not just write a patch to fix this and send it to the cygwin-patches
mail
> Linux and BSD options are not available, whatever the .h #defines.
Unsupported options should not be shown as features in the headers.
> Many header and library files are shared with newlib, which is used by Cygwin
If you checked before responding with a large digress into unrelated details,
y
On 2019-07-30 22:48, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>> Regular SO options on Windows:
>
> I did not ask about Windows options. I asked about a feature that is
> defined in Cygwin yet appears not functional.
You are running Windows sockets under Cygwin emulation.
Linux and
> Regular SO options on Windows:
I did not ask about Windows options. I asked about a feature that is defined
in Cygwin yet appears not functional.
> You can abuse Nagle to get similar behaviour cross-platform:
This is not the same thing!
> ENOPROTOOPT (109)... "The option is not supported by
On 2019-07-30 15:30, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> Consider the following code:
> $ cat cork.c
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #if defined(TCP_NOPUSH) && !defined(TCP_CORK)
> # define TCP_COR
6 matches
Mail list logo
