Re: clang++ broken by recent GCC update

2013-12-10 Thread RJVB
jojelino gmail.com> writes: > Clang does use hard-coded include path for using gcc header files. > Please build your own or you can file bug report to clang. > Hardcoding header file locations isn't very clever, esp. if that means things break even after applying a point update to gcc (4.7.3 t

Re: clang++ broken by recent GCC update

2013-07-05 Thread jojelino
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 fi

Re: clang++ broken by recent GCC update

2013-07-04 Thread Ryan Johnson
On 04/07/2013 8:47 AM, 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: ignoring nonexistent directory "/usr/lib/gcc/i686-pc-cygwin/4.5.3/include/c++" ignoring nonexistent director

clang++ broken by recent GCC update

2013-07-04 Thread Václav Zeman
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 version 3.1 (branches/release_31) Target: i386-pc-cygwin Thread model: posix "/usr/bin/clang" -cc1 -triple i386-pc-cygwin -S -disable-free -disable-