From: Qian Hong <fracting@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
Date: Fri, 19 Feb 2016 09:39:00 -0000 [thread overview]
Message-ID: <CALd+sZS=U_0hYRTQCs1gq2r22E9mWbFL1j=Bdhc+Gn5bJgr1Qg@mail.gmail.com> (raw)
In-Reply-To: <CALd+sZR=HSUoyh6VYCqDebPiA7fXQkQspycT=Hqaf8-7hTbRog@mail.gmail.com>
Wine use xattr to store Windows ACL information as extended
attribution, (well, it's an emulation for compatibility reason...)
fracting@fracting-ThinkPad-Edge-E431: ~/.wine/drive_c/cygwin$
$ getfattr tmp
# file: tmp
user.DOSATTRIB
user.wine.sd
fracting@fracting-ThinkPad-Edge-E431: ~/.wine/drive_c/cygwin$ getfattr
-n user.wine.sd tmp
# file: tmp
user.wine.sd=0sAQAUEAAAHAAAABwAAAAAAAAA7AAAAAEFAAAAAAAFFQAAAAAAAAAAAAAAAAAAAOgDAAABBQAAAAAABRUAAAAAAAAAAAAAAAAAAAABAgAAAgDsAAkAAAABABQAAQACAAEBAAAAAAAAAAAAAAAAJAD/AR8AAQUAAAAAAAUVAAAAAAAAAAAAAAAAAAAA6AMAAAAAJACAABIAAQUAAAAAAAUVAAAAAAAAAAAAAAAAAAAAAQIAAAEAJAB/AQAAAQUAAAAAAAUVAAAAAAAAAAAAAAAAAAAAAQIAAAAAFAC/ARIAAQEAAAAAAAEAAAAAAQsUAAAAAgABAQAAAAAAAAAAAAAACxQA/wEfAAEBAAAAAAADAAAAAAALFACpABIAAQEAAAAAAAMBAAAAAAsUAKkAEgABAQAAAAAAAQAAAAA=
As a temporary hack, you can remove ~/.wine/drive_c/cygwin/tmp from
Linux and re-create using Linux mkdir (rather than Cygwin mkdir). Or
use Linux's `fgetxattr` to clear user.wine.sd attribution of
~/.wine/drive_c/cygwin/tmp, this should make `mktemp` and gcc work.
I'm still investigating what is the root cause.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-02-19 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 20:35 John Hood
2016-02-13 20:46 ` John Hood
2016-02-13 21:11 ` Qian Hong
2016-02-13 21:39 ` Qian Hong
2016-02-14 16:35 ` Andrey Repin
2016-02-15 11:46 ` Corinna Vinschen
2016-02-16 9:36 ` Qian Hong
2016-02-19 2:48 ` Qian Hong
2016-02-19 9:39 ` Qian Hong [this message]
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='CALd+sZS=U_0hYRTQCs1gq2r22E9mWbFL1j=Bdhc+Gn5bJgr1Qg@mail.gmail.com' \
--to=fracting@gmail.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).