From: "Zac G. Al Wakeel" <ghanimm4@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cannot Run Executable Files
Date: Sat, 09 Jan 2016 13:52:00 -0000 [thread overview]
Message-ID: <FEC34897-3E10-4FFA-ABA7-1FDF1B05BA3E@gmail.com> (raw)
> For the archives, would you say which software was causing the problem?
I was using Avast, free software.
--
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
next reply other threads:[~2016-01-09 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 13:52 Zac G. Al Wakeel [this message]
2016-01-09 14:36 ` Jim Reisert AD1C
2016-01-11 16:13 ` Warren Young
2016-01-11 16:44 ` Mark Hansen
-- strict thread matches above, loose matches on Subject: below --
2016-01-08 4:59 Zac G. Al Wakeel
2016-01-08 7:48 ` Yaakov Selkowitz
2016-01-08 19:49 ` Warren Young
2016-01-08 19:54 ` Warren Young
2016-01-07 17:54 Zac G. Al Wakeel
2016-01-07 20:19 ` Warren Young
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=FEC34897-3E10-4FFA-ABA7-1FDF1B05BA3E@gmail.com \
--to=ghanimm4@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).