public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/16024] Document use of relative path to ${srcdir}/configure when using MSYS
Date: Fri, 24 Aug 2007 10:21:00 -0000	[thread overview]
Message-ID: <20070824102054.17104.qmail@sourceware.org> (raw)
In-Reply-To: <bug-16024-8754@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from fxcoudert at gcc dot gnu dot org  2007-08-24 10:20 -------
Since this one seems to be a documentation issue, I'll take it. I intend to
write a *-*-mingw32 entry to the target-specific installation notes.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |fxcoudert at gcc dot gnu dot
                   |dot org                     |org
             Status|SUSPENDED                   |ASSIGNED
          Component|bootstrap                   |web
 GCC target triplet|i386-pc-elf                 |
           Keywords|                            |documentation
   Last reconfirmed|2005-07-15 22:33:02         |2007-08-24 10:20:53
               date|                            |
            Summary|gengtype crashes with mingw |Document use of relative
                   |and c++ extension           |path to ${srcdir}/configure
                   |                            |when using MSYS


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16024


       reply	other threads:[~2007-08-24 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16024-8754@http.gcc.gnu.org/bugzilla/>
2007-08-24 10:21 ` fxcoudert at gcc dot gnu dot org [this message]
2008-06-15 15:12 ` fxcoudert at gcc dot gnu dot org

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=20070824102054.17104.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).