public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: clang++ broken by recent GCC update
Date: Fri, 05 Jul 2013 15:29:00 -0000	[thread overview]
Message-ID: <51D6E666.20102@gmail.com> (raw)
In-Reply-To: <CAKw7uViT4P23=i1tV0qp8C6biy+sr59-=YAHrUkD2AnKsZU=HQ@mail.gmail.com>

On 2013-07-04 PM 9:47, Václav Zeman wrote:> Hi.
 >
 > The C++ part of Clang package (I have not tested the C part) is broken
 > after update of GCC to 4.7.3. It cannot find standard C++ headers:
 >
 >
Clang does use hard-coded include path for using gcc header files.
Please build your own or you can file bug report to clang.

--
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

WARNING: multiple messages have this Message-ID

From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: clang++ broken by recent GCC update
Date: Fri, 05 Jul 2013 17:36:00 -0000	[thread overview]
Message-ID: <51D6E666.20102@gmail.com> (raw)
Message-ID: <20130705173600.1nZyqk38keCcPw2ylwcek9Ii-ZrrdxWfSnnLg20fuiU@z> (raw)
In-Reply-To: <CAKw7uViT4P23=i1tV0qp8C6biy+sr59-=YAHrUkD2AnKsZU=HQ@mail.gmail.com>

On 2013-07-04 PM 9:47, Václav Zeman wrote:> Hi.
 >
 > The C++ part of Clang package (I have not tested the C part) is broken
 > after update of GCC to 4.7.3. It cannot find standard C++ headers:
 >
 >
Clang does use hard-coded include path for using gcc header files.
Please build your own or you can file bug report to clang.


--
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

  parent reply	other threads:[~2013-07-05 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 12:47 Václav Zeman
2013-07-04 17:34 ` Ryan Johnson
2013-07-05 15:29 ` jojelino [this message]
2013-07-05 17:36   ` jojelino
2013-12-10 14:05   ` RJVB

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=51D6E666.20102@gmail.com \
    --to=jojelino@gmail.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).