From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: Gcc-mingw - check directory structure after updated my Cygwin from 1.5 to 1.7 (finally) before I read gcc-mingw announcement
Date: Thu, 30 Jun 2011 17:33:00 -0000 [thread overview]
Message-ID: <4E0CB343.9080805@cwilson.fastmail.fm> (raw)
In-Reply-To: <VA.00001ce4.0054e8a2@thesoftwaresource.com>
On 6/30/2011 10:40 AM, Brian Keener wrote:
> The /usr/i686-pc-mingw32 directory structure on my machine is different
> than documented above. Within /usr/i686-pc-mingw32 I have:
> bin
> lib
> sys-root
>
> and within sys-root I have
> mingw
> within mingw I find
> bin
> include
> lib
> share
This is correct. The mailing list post was incorrect (I was, after all,
writing that from memory). You should be safe to go ahead with the next
steps.
--
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
prev parent reply other threads:[~2011-06-30 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 14:41 Brian Keener
2011-06-30 17:33 ` Charles Wilson [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=4E0CB343.9080805@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).