From: "H. Peter Anvin" <hpa@zytor•com>
To: Johannes Sixt <J.Sixt@eudaptics•com>
Cc: git@vger•kernel.org
Subject: Re: MinGW port usable
Date: Thu, 01 Feb 2007 13:05:18 -0800 [thread overview]
Message-ID: <45C2560E.6090504@zytor.com> (raw)
In-Reply-To: <45C1C24A.471F40AD@eudaptics.com>
Johannes Sixt wrote:
> "H. Peter Anvin" wrote:
>> Johannes Sixt wrote:
>>> (*) The reason is that on Windows read() and write() cannot operate on
>>> descriptors created by socket(). A work-around is to implement a (threaded)
>>> proxy, but that's almost the same as if netcat were used as
>>> GIT_PROXY_COMMAND.
>>>
>> Actually, I believe it can for the NT series kernels (at least 2000 or
>> later, not sure about the earlier ones), but not for the DOS-based ones.
>>
>> The trick is to use _open_osfhandle() to convert the file handle (a
>> WinAPI construct) to a file descriptor (which in Windows is a construct
>> of the C library.)
>
> I tried this, but it doesn't seem to work. I get an EINVAL at the first
> write() to the socket. I conclude that the things returned by socket()
> are not WinAPI file handles that are valid for WriteFile(). :(
>
Except they are (for NT-based Windows), so you're doing something goofy.
This is a widely used construct, so it can't be that broken.
-hpa
next prev parent reply other threads:[~2007-02-01 21:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 22:20 MinGW port usable Johannes Sixt
2007-01-29 22:35 ` Shawn O. Pearce
2007-01-29 23:11 ` Christian MICHON
2007-01-29 23:24 ` Shawn O. Pearce
2007-01-29 23:48 ` Christian MICHON
2007-01-30 7:59 ` Christian MICHON
2007-01-30 8:07 ` Christian MICHON
2007-01-30 10:16 ` Johannes Schindelin
2007-01-30 15:27 ` Shawn O. Pearce
2007-01-30 16:31 ` Johannes Sixt
2007-01-30 8:47 ` Johannes Sixt
2007-01-29 22:46 ` Linus Torvalds
2007-01-29 23:08 ` Christian MICHON
2007-01-30 10:08 ` Johannes Schindelin
2007-01-30 10:14 ` Christian MICHON
2007-01-30 8:45 ` Johannes Sixt
2007-01-30 14:35 ` Johannes Schindelin
2007-01-30 15:18 ` Shawn O. Pearce
2007-01-30 15:38 ` Johannes Schindelin
2007-01-30 15:56 ` Shawn O. Pearce
2007-01-30 16:12 ` Johannes Schindelin
2007-01-30 16:28 ` Shawn O. Pearce
2007-01-30 16:49 ` Johannes Schindelin
2007-01-30 0:50 ` Daniel Barkalow
2007-01-30 8:23 ` Johannes Sixt
2007-01-30 8:41 ` Andreas Ericsson
2007-01-30 10:07 ` Johannes Schindelin
2007-01-30 17:09 ` Daniel Barkalow
2007-01-30 17:36 ` Johannes Schindelin
2007-01-30 18:09 ` Daniel Barkalow
2007-01-30 20:20 ` Johannes Sixt
2007-01-30 5:53 ` Junio C Hamano
2007-02-01 6:35 ` H. Peter Anvin
2007-02-01 10:34 ` Johannes Sixt
2007-02-01 21:05 ` H. Peter Anvin [this message]
2007-02-02 8:28 ` H. Peter Anvin
2007-02-02 8:49 ` Davide Libenzi
2007-02-02 8:55 ` Johannes Sixt
2007-02-02 8:55 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C2560E.6090504@zytor.com \
--to=hpa@zytor$(echo .)com \
--cc=J.Sixt@eudaptics$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox