Displaying 6 results from an estimated 6 matches for "libcxx_has_wx_flag".
2016 Dec 12
1
failing bootstrap: C++11 or greater is required but the compiler does not support c++11
FTR, I've disabled libcxx checkout on that particular bot
<http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer> to make
it green.
The problem remains, of course. :(
On Sun, Dec 11, 2016 at 7:23 AM, James Knight <jyknight at google.com> wrote:
> On Dec 11, 2016, at 3:33 AM, Eric Fiselier via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> > So it
2016 Dec 11
2
failing bootstrap: C++11 or greater is required but the compiler does not support c++11
On Dec 11, 2016, at 3:33 AM, Eric Fiselier via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> So it seems that libatomic went missing between build #1379 and #1380, so I don't think this is related to the -std=c++11 failure. Instead it seems likely that the compile test for -std=c++11 is failing due to mis-configuring -latomic.
>
> Can you confirm the bot has libatomic
2014 Oct 07
2
[LLVMdev] Can libc++ build for arm cross compiler?
...orming Test LIBCXX_HAS_WNO_ERROR_FLAG - Success
> -- Performing Test LIBCXX_HAS_FNO_EXCEPTIONS_FLAG
> -- Performing Test LIBCXX_HAS_FNO_EXCEPTIONS_FLAG - Success
> -- Performing Test LIBCXX_HAS_FNO_RTTI_FLAG
> -- Performing Test LIBCXX_HAS_FNO_RTTI_FLAG - Success
> -- Performing Test LIBCXX_HAS_WX_FLAG
> -- Performing Test LIBCXX_HAS_WX_FLAG - Failed
> -- Performing Test LIBCXX_HAS_NO_WX_FLAG
> -- Performing Test LIBCXX_HAS_NO_WX_FLAG - Failed
> -- Performing Test LIBCXX_HAS_EHSC_FLAG
> -- Performing Test LIBCXX_HAS_EHSC_FLAG - Failed
> -- Performing Test LIBCXX_HAS_NO_EHS_FLAG...
2014 Oct 03
3
[LLVMdev] Can libc++ build for arm cross compiler?
On 10/3/14 10:16 AM, Dan Albert wrote:
>>
>> I try to build libc++ and libc++abi for host x86_64(linux) and target
>> arm(linux) but fail.
>>
>
> Failing in what way? If this isn't working out of the box, we've done
> something wrong.
Yeah, it would help to know more specifics about where you're getting stuck.
>
> jroelofs might know more...
For
2017 Feb 11
2
Asan self host problems: Failed to deallocate
Trying to run a self host "ninja check-clang" with ASan enabled I hit a
/lot/ of errors like this (strangely I hit none of these in check-llvm,
only in check-clang):
Any ideas?
==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes
at address 0x631000014800
==10525==AddressSanitizer CHECK failed:
2017 Feb 15
2
Asan self host problems: Failed to deallocate
..._FLAG
LIBCXX_HAS_WNO_ERROR_FLAG:INTERNAL=1
//Test LIBCXX_HAS_WNO_LONG_LONG_FLAG
LIBCXX_HAS_WNO_LONG_LONG_FLAG:INTERNAL=1
//Test LIBCXX_HAS_WNO_UNUSED_PARAMETER_FLAG
LIBCXX_HAS_WNO_UNUSED_PARAMETER_FLAG:INTERNAL=1
//Test LIBCXX_HAS_WWRITE_STRINGS_FLAG
LIBCXX_HAS_WWRITE_STRINGS_FLAG:INTERNAL=1
//Test LIBCXX_HAS_WX_FLAG
LIBCXX_HAS_WX_FLAG:INTERNAL=
//Test LIBCXX_HAS_W_FLAG
LIBCXX_HAS_W_FLAG:INTERNAL=1
//ADVANCED property for variable: LIBXML2_INCLUDE_DIR
LIBXML2_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: LIBXML2_LIBRARIES
LIBXML2_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable...