The TestDataFormatterLibcc* tests require libc++-dev:
$ sudo apt-get install libc++-dev
On Mon, Aug 24, 2015 at 3:42 PM, Todd Fiala via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
> On Mon, Aug 24, 2015 at 3:39 PM, Zachary Turner
> wrote:
>
>> Can't comment on the failures for Linux, but I don
>
> Ah okay, so we are working with libc++ on Ubuntu, that's good to hear.
> Pre-14.04 I gave up on it.
We're still using libstdc++ for lldb itself. libc++ is used to compile
inferiors for the TestDataFormatterLibcc* tests. I don't actually know if
libc++ works with lldb. Sorry to get your hopes
You're using CC="/usr/bin/cc". It needs to be clang for USE_LIBCPP to do
anything. :/
On Tue, Aug 25, 2015 at 9:20 AM, Todd Fiala wrote:
> Here are a couple of the failures that came up (the log output from the
> full dosep.py run).
>
> Let me know if that is not sufficient!
>
> On Tue, Aug 25,
g the compiler symbolic links fully
>>> resolved:
>>> /usr/bin/cc -> /etc/alternatives/cc -> /usr/bin/gcc, which would have
>>> then caught that it doesn't support libc++.
>>>
>>> Couldn't we use gcc with libc++? (i.e. is it sufficient t
>>> -Todd
>>>
>>> On Tue, Aug 25, 2015 at 10:04 AM, Todd Fiala
>>> wrote:
>>>
>>>> Okay.
>>>>
>>>> So the culprit then is that I'm using:
>>>> cmake -GNinja ../llvm
>>>>
>>>&g
We gave each bot 8 slots due to some limitation with the build master.
Slots 1-6 will notify us of failures, and slots 7-8 are sort of reserved
for tests/builds that are expected to be broken. Ying can provide more
details.
On Mon, Sep 14, 2015 at 10:12 PM, Todd Fiala wrote:
> Hi Chaoren,
>
> Wh
