public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "millibit at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59623] Segmentation fault, cc1plus, relative path Date: Mon, 30 Dec 2013 18:32:00 -0000 [thread overview] Message-ID: <bug-59623-4-9bY4tu4LLE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59623-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59623 --- Comment #1 from Morten Kristiansen <millibit at gmail dot com> --- Not a bug in GCC, after all. Caused by some mixup of cygwin dll's. Closing bug.
next prev parent reply other threads:[~2013-12-30 18:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-29 17:12 [Bug c++/59623] New: " millibit at gmail dot com 2013-12-30 18:32 ` millibit at gmail dot com [this message] 2013-12-30 18:34 ` [Bug c++/59623] " millibit at gmail dot com
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=bug-59623-4-9bY4tu4LLE@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).