similar to: [LLVMdev] LLVM 3.7 release plans

> > - Using CMake for the release binaries. I think I promised we'd do > > this for 3.7. I haven't actually started looking at this yet, but I'm > > still optimistic. > > I'm absolutely in agreement with this. Most of us already use CMake > for development, a lot of the buildbots are based on it and I think we > all agree that autoconf is deprecated.

Hello build bot owners! The staging master is ready. Please feel free to use it to make sure your bots would work well with the monorepo and github. The following builders could be configured to build monorepo: * clang-atom-d525-fedora-rel * clang-native-arm-lnt-perf * clang-cmake-armv7-lnt * clang-cmake-armv7-selfhost-neon * clang-cmake-armv7-quick * clang-cmake-armv7-global-isel *

Hi Galina, It seems that our libcxx bots are now triggering builds for any changes to llvm: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux/builds/2434 Should I file a bug report for this? Thanks, Diana On Sat, 19 Oct 2019 at 11:36, Galina Kistanova via cfe-commits <cfe-commits at lists.llvm.org> wrote: > > Hello everyone, > > The staging master is

Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original

Hi Tanya, The www-scripts builder that updates the Sphinx documentation has been broken for about a week now, despite the buildbot builders passing. The error from the last sphinx update attempt says: > /opt/tools/sphinx_update.sh: warning: removing stale lock file from PID 8798. > UPDATING lld SOURCES > Updating '.': > At revision 302593. > make: *** No rule to make

I think what she is referring to was that the build seemed to be triggered by a commit to a project that shouldn't trigger builds on a libcxx bot (i.e. the change was in llvm). I have a somewhat orthogonal but related question. In the past, commits to compiler-rt did not trigger builds on llvm/clang/sanitizer bots. Has this behaviour been rectified with the move to github? I am really sorry

I don't know if that would make a difference. Whenever a CMake file is changed and a build rule is executed CMake is automatically re-run, but the variables in the cache remain. Since certain configuration doesn't re-run once a variable is in the cache, a bad cache variable can break the build until it's manually removed. I believe that's what's happening here. I should

Hello everyone, Below are some buildbot numbers for the last week of 9/25/2016 - 10/1/2016. Please see the same data in attached csv files: The longest time each builder was red during the last week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed

Hello everyone, Below are some buildbot numbers for the last week of 6/05/2016 - 6/11/2016. Thanks Galina buildername | was_red -----------------------------------------------------------+----------- sanitizer-x86_64-linux-bootstrap | 134:12:25 perf-x86_64-penryn-O3-polly-parallel-fast | 46:29:26

Ping. It's been another week. When are we going to get the docs building and updating again? On Tue, May 16, 2017 at 9:01 PM, Eric Fiselier <eric at efcs.ca> wrote: > Ping. Everything is still broken. > > On Wed, May 10, 2017 at 2:39 PM, Eric Fiselier <eric at efcs.ca> wrote: > >> I don't know if that would make a difference. Whenever a CMake file is

@Tobias The poly docs build step is still failing, but due to a bug in the particular version of Sphinx used by the www-scripts builder. This seems like something best worked around inside poly. The builds take place hourly and their output is reported on the www-scripts at lists.llvm.org mailing list. On Thu, May 25, 2017 at 12:58 AM, Tobias Grosser <tobias.grosser at inf.ethz.ch > wrote:

Hi All, I'm working on rewriting libc++'s documentation using Sphinx. Hopefully it will be easier to write and maintain documentation using restructured text and not HTML. What steps do I need to take to get libc++ a Sphinx builder and get the required changes made for libcxx.llvm.org? /Eric

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

Hello everyone, Below are some buildbot numbers for the week of 7/10/2016 - 7/16/2016. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

> On 3 Apr 2017, at 22:47, Alex Denisov <1101.debian at gmail.com> wrote: > > The HTML generated using sphinx[1]. > At the bottom of each page you can see actual version of sphinx used to generate this page. > Thanks -- interesting that the docs haven't been updated since March 15th: © Copyright 2003-2017, LLVM Project. Last updated on 2017-03-16. Created using Sphinx

Moving the LLVM Documentation to Sphinx ======================================= As a few of you that are on IRC already know, I have experimented with moving the LLVM documentation over to `Sphinx <http://sphinx.pocoo.org/index.html>`__ from the current html form. I have moved almost all of the content over and have begun "Sphinxifying" the documentation to correct links and make

On 3 April 2017 at 13:59, Daniel Berlin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On Mon, Apr 3, 2017 at 5:51 AM, Dean Michael Berris via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> >> On 3 Apr 2017, at 22:47, Alex Denisov <1101.debian at gmail.com> wrote: >> >> The HTML generated using sphinx[1]. >> At the

Hi Eric, On 20 July 2015 at 10:41, Eric Fiselier <eric at efcs.ca> wrote: > Hi All, > > I'm working on rewriting libc++'s documentation using Sphinx. > Hopefully it will be easier to write and maintain documentation using > restructured text and not HTML. > > What steps do I need to take to get libc++ a Sphinx builder and get > the required changes made for

Here's the first part of my Windows set up documentation. This one only covers the process of setting up a normal box for building LLVM and Clang. A later document, which will follow in a few days, will cover how to set up a buildbot slave. As usual: I'm not a psychic, so if you have opinions regarding or suggestions on this document, please feel free to share them with me (on this

You are correct, sir. Everything works much better if I run CMake and Ninja from a "developer command prompt." I displayed the path and almost fell off my chair laughing. The road to hell is paved with environment variable entries. Two questions. 1. Building with Visual Studio created build/release/bin. Building with Ninja created build/bin (no release directory). Does that make sense?