No, none of my commits have this problem. The change that broke the
build had nothing to do with me. I believe it was r220894 - Start
adopting the StringPrinter API.
On 10/30/2014 12:55 PM, Eric Christopher wrote:
So "I've committed a similar change with the same problem"? :)
It looks like it's being fixed. Do try to be more careful, there is an
lldb buildbot that's been broken since this change went in:
http://lab.llvm.org:8011/builders/lldb-x86_64-debian-clang
Thanks.
-eric
On Thu Oct 30 2014 at 12:53:15 PM Shawn Best <sb...@blueshiftinc.com
<mailto:sb...@blueshiftinc.com>> wrote:
This change has not been checked in. The current broken build on
linux is due to a different checkin which included the same header
file.
On 10/30/2014 12:51 PM, Eric Christopher wrote:
On Tue Oct 28 2014 at 1:46:20 PM Vince Harron <vhar...@google.com
<mailto:vhar...@google.com>> wrote:
> codecvt> : the patch uses a c++ 11 class std::codecvt_utf8,
this is a facet implementation that will do utf8 to wchar
convervsion. It is part of c++ 11 standard, but not yet
supported in gcc.
Should we drop support for building with gcc on Linux?
We shouldn't. And this appears to have broken building on LInux.
We need to revert this immediately.
Thanks.
-eric
_______________________________________________
lldb-dev mailing list
lldb-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
