From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: MSYS mode (continue)
Date: Thu, 04 Jul 2013 14:47:00 -0000 [thread overview]
Message-ID: <51D58AE1.1080001@cwilson.fastmail.fm> (raw)
In-Reply-To: <20130704121617.GC12995@calimero.vinschen.de>
On 7/4/2013 8:16 AM, Corinna Vinschen wrote:
> I'm ok with that, but I think we should drop the "32" from MINGW in
> the first place.
>
> Does anybody rely on the "WOW64" in uname -s output? I just checked
> the scripts in /bin in my installation and none of it seems to check
> for that info.
>
> And then again, it *is* redundant, given the uname -m output...
cygwin64$ uname -s
CYGWIN_NT-6.1
cygwin64$ uname -m
x86_64
cygwin32$ uname -s
CYGWIN_NT-6.1-WOW64
cygwin32$ uname -m
i686
Yep, seems redundant.
--
Chuck
--
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 prev parent reply other threads:[~2013-07-04 14:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 16:03 Alexey Pavlov
2013-07-03 18:15 ` Christopher Faylor
2013-07-03 18:25 ` Alexey Pavlov
2013-07-03 19:50 ` Corinna Vinschen
2013-07-03 21:03 ` Charles Wilson
2013-07-03 21:57 ` Christopher Faylor
2013-07-03 22:39 ` Charles Wilson
2013-07-04 2:33 ` Alexey Pavlov
2013-07-04 8:58 ` Corinna Vinschen
2013-07-04 9:07 ` Alexey Pavlov
2013-07-04 9:09 ` Alexey Pavlov
2013-07-04 9:17 ` Corinna Vinschen
2013-07-04 9:37 ` Alexey Pavlov
2013-07-04 10:11 ` Corinna Vinschen
2013-07-04 10:23 ` Alexey Pavlov
2013-07-04 10:34 ` Kai Tietz
2013-07-04 10:47 ` Corinna Vinschen
2013-07-04 10:54 ` Alexey Pavlov
2013-07-04 14:43 ` Charles Wilson
2013-07-04 10:37 ` Corinna Vinschen
2013-07-04 10:45 ` Alexey Pavlov
2013-07-04 12:16 ` Corinna Vinschen
2013-07-04 14:47 ` Charles Wilson [this message]
2013-07-04 16:36 ` Christopher Faylor
2013-07-09 10:57 ` BGINFO4X
2013-07-09 18:15 ` Buchbinder, Barry (NIH/NIAID) [E]
2013-07-04 9:13 ` Corinna Vinschen
2013-07-04 8:39 ` Corinna Vinschen
2013-07-04 14:49 ` Charles Wilson
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=51D58AE1.1080001@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--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).