public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: peflags warning and tsaware flags
Date: Thu, 26 Apr 2012 15:16:00 -0000	[thread overview]
Message-ID: <loom.20120426T170854-952@post.gmane.org> (raw)

What is peflags trying to tell me with this warning, which is only present when
the "-v" switch is in effect?


> ash -c "PATH=/bin peflags -t -d -v  /usr/lib/zsh/4.3.12/zsh/zutil.dll"
Warning: file is non-executable but has tsaware set
(/usr/lib/zsh/4.3.12/zsh/zutil.dll).
/usr/lib/zsh/4.3.12/zsh/zutil.dll:
coff(0x230e[+executable_image,+line_nums_stripped,
+local_syms_stripped,+32bit_machine,+sepdbg,+dll])
pe(0x8000[-dynamicbase,+tsaware])

> ash -c "PATH=/bin peflags -t -d  /usr/lib/zsh/4.3.12/zsh/zutil.dll"
/usr/lib/zsh/4.3.12/zsh/zutil.dll: coff(0x230e) pe(0x8000[-dynamicbase,+tsaware])


The file(s) in question are most certainly executable, POSIX file permissions
and cacls are no different than hundreds of other DLL.  Also, I seem to have a
wild mixture of "+tsaware" and "-tsaware".  Can I just set all of them to
"+tsaware" or is that a Bad Idea(TM)?  (I do want to install Cygwin onto a
Terminal Server.)


Achim.



--
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

             reply	other threads:[~2012-04-26 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:16 Achim Gratz [this message]
2012-04-26 19:58 ` Corinna Vinschen
2012-04-26 20:28   ` Achim Gratz
2012-04-27  3:09     ` Larry Hall (Cygwin)
2012-04-27  6:05       ` Achim Gratz
2012-04-27  7:37         ` Corinna Vinschen
2012-04-27  8:55           ` Achim Gratz

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=loom.20120426T170854-952@post.gmane.org \
    --to=stromeko@nexgo.de \
    --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).