From: Michael Stefaniuc <mstefani@redhat.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: 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 15:28:29 +0200 [thread overview]
Message-ID: <53D7A17D.5010206@redhat.com> (raw)
In-Reply-To: <CACsJy8Att+O7fF-2mMjqkfm75yXihfJNWutGDAqUkZs34pKLGw@mail.gmail.com>
On 07/29/2014 03:05 PM, Duy Nguyen wrote:
> On Tue, Jul 29, 2014 at 7:20 PM, Michael Stefaniuc <mstefani@redhat.com> wrote:
>> On 07/29/2014 08:30 AM, Torsten Bögershausen wrote:
>>> 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.
>> Why is fixing Wine not an option? The guy working on MSVCRT in Wine is
>> very responsive; all that is needed is just a bug in
>> https://bugs.winehq.org/ and he'll look at it. Or give me more details
>> and I'll create the bug entry.
>
> Not an option as in "_I_ will be working on it". I don't suppose lots
> of people use git on wine to be worth the trouble, but then again
> making wine msvcrt more compatible is probably a good thing so I'll
> open a bug for wine.
Thanks! This is actually a very important use case for Wine:
Making it easy for OSS developers to test the Windows builds of their
software without having to use Windows.
bye
michael
next prev parent reply other threads:[~2014-07-29 13:27 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
2014-07-29 12:20 ` Michael Stefaniuc
2014-07-29 13:05 ` Duy Nguyen
2014-07-29 13:28 ` Michael Stefaniuc [this message]
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=53D7A17D.5010206@redhat.com \
--to=mstefani@redhat.com \
--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).