From: "Torsten Bögershausen" <tboegi@web.de>
To: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: "error: Tweaking file descriptors doesn't work with this MSVCRT.dll" on wine
Date: Tue, 29 Jul 2014 08:30:21 +0200 [thread overview]
Message-ID: <53D73F7D.1010902@web.de> (raw)
In-Reply-To: <CACsJy8DFvTHieQc-nZL2h7JbQYc4Qkbx+Ouc297VpNeU=kNaoQ@mail.gmail.com>
On 07/28/2014 12:39 PM, Duy Nguyen wrote:
> I know wine is kind of second citizen but is there a cheap trick to
> make it work on wine? Reverting fcd428f (Win32: fix broken pipe
> detection - 2012-03-01) could result in conflicts in compat that I'm
> not comfortable resolving. I don't have Windows at home. Wine is the
> only option for me (or if somebody has a modern.ie image for KVM, or a
> simple recipe to make one, that'd be great). "Fix wine" is not really
> an option.
Is it only that patch that needs to be reverted to make things work got
wine?
For me It seems as if the patch is not that huge, and manually do a
copy-paste
with the help of a diff tool can be done.
It seems as if even both implemenations can live side-by-side in the code.
And if there is a run-time detection for wine, we could switch between the
old one and the new one which is dependent on how MSVCRT.dll has layed out
internal data structures:
"ioinfo structure (exposed by MSVCRT.dll via __pioinfo"
Sorry being not more helpful
next prev parent reply other threads:[~2014-07-29 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 10:39 "error: Tweaking file descriptors doesn't work with this MSVCRT.dll" on wine Duy Nguyen
2014-07-29 6:30 ` Torsten Bögershausen [this message]
2014-07-29 12:20 ` Michael Stefaniuc
2014-07-29 13:05 ` Duy Nguyen
2014-07-29 13:28 ` Michael Stefaniuc
2014-07-29 19:55 ` Karsten Blees
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=53D73F7D.1010902@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).