From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: magic failure
Date: Wed, 19 Jun 2013 13:23:00 -0000 [thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A7021D89AB3@USA7109MB022.na.xerox.net> (raw)
Surprised that this didn't work:
$ ls -ld /usr/bin/gcc-?
ls: cannot access /usr/bin/gcc-?: No such file or directory
$
while the following did:
$ ls -ld /usr/bin/gcc-?.exe
-rwxr-xr-x 2 knellis Domain Users 94741 Feb 25 2009 /usr/bin/gcc-3.exe
-rwxr-xr-x 3 knellis Domain Users 231438 Oct 26 2011 /usr/bin/gcc-4.exe
$
Not a biggie. I can cope.
--Ken Nellis
--
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:[~2013-06-19 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 13:23 Nellis, Kenneth [this message]
2013-06-19 13:31 ` Matt D.
2013-06-19 16:53 ` Nellis, Kenneth
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=0D835E9B9CD07F40A48423F80D3B5A7021D89AB3@USA7109MB022.na.xerox.net \
--to=kenneth.nellis@xerox.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).