search for: dsphinx_warnings_as_errors

...E_CXX_COMPILER=clang++-3.9 -DCMAKE_C_COMPILER=clang-3.9 -DCMAKE_ASM_COMPILER=clang-3.9 -DLLVM_USE_LINKER=gold -DLLVM_USE_SPLIT_DWARF=On -DBUILD_SHARED_LIBS=ON -DLLVM_OPTIMIZED_TABLEGEN=On -DCOMPILER_RT_BUILD_XRAY=On -DLLVM_ENABLE_ASSERTIONS=On -DCOMPILER_RT_INCLUDE_TESTS=On -DLLVM_ENABLE_SPHINX=On -DSPHINX_WARNINGS_AS_ERRORS=On -DCMAKE_CXX_FLAGS="-Wpedantic" -DCMAKE_CXX_COMPILER_LAUNCHER=ccache ../llvm I'm building in Linux, x86_64. Cheers > > Thanks, > -Chris > >> On Oct 3, 2017, at 4:58 AM, Dean Michael Berris <dean.berris at gmail.com> wrote: >> >> Hi llvm-dev,...

...irectory). Does that make sense? (I have -DCMAKE_BUILD_TYPE=Release on the cmake command.) 2. The first build attempt failed because the existing TableGen Language Reference has multiple instances of the production 'SimpleValue', which produces warnings from Sphinx. I fixed that by adding -DSPHINX_WARNINGS_AS_ERRORS:BOOL=OFF to the cmake command. Does the official build do that, too? I searched all the CMakeLists files but didn't find any use of that option. At 8/8/2020 09:48 PM, David Blaikie wrote: >On Sat, Aug 8, 2020 at 5:27 PM Paul C. Anagnostopoulos ><paul at windfall.com> wrote: >&g...

Am 2018-02-07 21:51, schrieb Hans Wennborg via llvm-dev: > Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. Hi Hans, I can't build the documentation:

Folks, Total newbie here. What is the simplest way to build a single .rst file so that I can look at the generated HTML? I have CMake, Python, and Sphinx installed. ~~ Paul

...VM_LINK_LLVM_DYLIB=ON \     -DLLVM_INSTALL_UTILS=ON \     -DLLVM_ENABLE_RTTI=ON \     -DLLVM_ENABLE_FFI=ON \     -DLLVM_ENABLE_EH=ON \     -DLLVM_BUILD_TESTS=ON \     -DLLVM_BUILD_DOCS=OFF \     -DLLVM_ENABLE_SPHINX=OFF \     -DLLVM_ENABLE_DOXYGEN=OFF \     -DLLDB_DISABLE_LIBEDIT=1 \     -DSPHINX_WARNINGS_AS_ERRORS=OFF \     -DFFI_INCLUDE_DIR=$(pkg-config --variable=includedir libffi) \     -DFFI_LIBRARY_DIR:PATH="$(pkg-config --variable=libdir libffi)" \     -DLLVM_BINUTILS_INCDIR=/usr/include \     -DLLVM_LIBDIR_SUFFIX=64 \     -DLIBCXX_ENABLE_ABI_LINKER_SCRIPT=ON \     -DLIBUNWIND_ENABLE_SH...

Hi llvm-dev, I have unit tests set up in the XRay implementation (compiler-rt/lib/xray/tests/unit) following the pattern that the TSAN and other sanitiser unit tests. However, I'm running into the following problem: When I make changes to the runtime (in this case, XRay) and do `ninja all check-xray`, it seems that the unit tests don't get re-liked to the new version of the runtime. It

Last night, I triggered a buildbot error after my most recent commit. That one was totally on me as the warning did pop up while generating the docs site locally using the sphinx-build command (confirmed this afternoon). I just checked in a commit to resolve the error but now it appears I've triggered a different buildbot error? This error did not come up when I built the site locally to test

...E_RTTI=ON \ >> -DLLVM_ENABLE_FFI=ON \ >> -DLLVM_ENABLE_EH=ON \ >> -DLLVM_BUILD_TESTS=ON \ >> -DLLVM_BUILD_DOCS=OFF \ >> -DLLVM_ENABLE_SPHINX=OFF \ >> -DLLVM_ENABLE_DOXYGEN=OFF \ >> -DLLDB_DISABLE_LIBEDIT=1 \ >> -DSPHINX_WARNINGS_AS_ERRORS=OFF \ >> -DFFI_INCLUDE_DIR=$(pkg-config --variable=includedir libffi) \ >> -DFFI_LIBRARY_DIR:PATH="$(pkg-config --variable=libdir libffi)" \ >> -DLLVM_BINUTILS_INCDIR=/usr/include \ >> -DLLVM_LIBDIR_SUFFIX=64 \ >> -DLIBCXX_ENABLE_ABI_...

...;>> -DLLVM_ENABLE_EH=ON \ >>>> -DLLVM_BUILD_TESTS=ON \ >>>> -DLLVM_BUILD_DOCS=OFF \ >>>> -DLLVM_ENABLE_SPHINX=OFF \ >>>> -DLLVM_ENABLE_DOXYGEN=OFF \ >>>> -DLLDB_DISABLE_LIBEDIT=1 \ >>>> -DSPHINX_WARNINGS_AS_ERRORS=OFF \ >>>> -DFFI_INCLUDE_DIR=$(pkg-config --variable=includedir libffi) \ >>>> -DFFI_LIBRARY_DIR:PATH="$(pkg-config --variable=libdir libffi)" \ >>>> -DLLVM_BINUTILS_INCDIR=/usr/include \ >>>> -DLLVM_LIBDIR_SUFFIX=64 \ &g...

Hi Tanya, Last time I noticed a problem with clang-tools-extra docs you could help solving them. If someone else is taking care of this part of the infrastructure now, please redirect appropriately. It looks like docs generated from rst (for LLVM, Clang and clang-tools-extra) don't get updated at the moment. They stopped updating somewhere between r353327

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans

Sigh. I ask for your indulgence yet again. I installed Ninja and deleted my old build tree. When I run CMake now, I'm told that it can't find the compilers and assembler. So, of course, I need to put a compiler toolset on my path. I tried MinGW but was instantly reminded that it doesn't have localtime_s. So I tried to find the Visual Studio binaries and located four different

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on