similar to: [SERVER UPDATE] Moving clang, clang-analyzer, libcxxabi, libcxx ... websites to new server

> On Jan 13, 2017, at 12:35 PM, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Thu, Jan 5, 2017 at 5:26 PM, Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Are you fixing the SSL problem? > Yes. The new server will have SSL support for all websites and have an updated certificate. >

On Fri, Jan 13, 2017 at 04:07:48PM -0500, James Y Knight via llvm-dev wrote: > But beyond that: there's no downside. Why should *anyone* continue to serve > http traffic? It's just all around better and safer to require https, for > everything, always. I take you haven't tried to use WiFi at UK airports or coaches recently? There are a lot of other places with completely

On Sun, Jan 15, 2017 at 04:25:16PM -0500, James Knight wrote: > On Jan 15, 2017, at 9:19 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Fri, Jan 13, 2017 at 04:07:48PM -0500, James Y Knight via llvm-dev wrote: > >> But beyond that: there's no downside. Why should *anyone* continue to serve > >> http traffic? It's just all

In prepping our next release, we noticed that the LICENSE.TXT files were still all copyrighted 2015. I've done a bit of archaeology and it looks like the files to update are: cfe/trunk/LICENSE.TXT clang-tools-extra/trunk/LICENSE.TXT compiler-rt/trunk/LICENSE.TXT libclc/trunk/LICENSE.TXT libcxx/trunk/LICENSE.TXT libcxxabi/trunk/LICENSE.TXT lld/trunk/LICENSE.TXT llvm/trunk/LICENSE.TXT

Hi, I am observing the libcxx project can not be built without libcxxabi, but I thought libcxx should not depend upon other projects. Observed on x86. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200102/023ca21b/attachment.html>

> On Mar 30, 2016, at 1:57 PM, Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > In prepping our next release, we noticed that the LICENSE.TXT files > were still all copyrighted 2015. I've done a bit of archaeology and > it looks like the files to update are: > > cfe/trunk/LICENSE.TXT > clang-tools-extra/trunk/LICENSE.TXT >

On 03/20/2017 03:33 PM, Jonathan Roelofs wrote: > On 3/20/17 1:47 PM, Evandro Menezes via llvm-dev wrote: >> Folks, >> >> I'm at a loss trying to add Compiler-RT to an LLVM build, even after >> checking out the instructions at http://compiler-rt.llvm.org, so I'd >> appreciate your help. >> >> I've tried adding the CMake options

Hi, I'm under Ubuntu 13.10 amd64 I just compiled both my libcxx and my libcxxabi. I noticed this really weird behaviour, while trying to compile some C++11-compliant piece of code I get this error at runtime exception_ptr not yet implemented Aborted (core dumped) Now my experience tells me that this is something that can easily be related to the ABI, so I go to the official libcxxabi

Since the original buildit script doesn't cover my needs I switched to a custom but really similar script, in the meantime I also got the habit to dig for new flags and support and the __GLIBCXX__ define was hiding some of this errors. I see that other linux-based operating system offer this kind of support and they even use the same core components of my GNU/Linux distribution. You are

All, The following llvm.org certificates will be renewed tomorrow, Friday Sept 22nd at ~7:30AM PDT. bugs.llvm.org <http://bugs.llvm.org/> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/> clang.llvm.org <http://clang.llvm.org/> compiler-rt.llvm.org <http://compiler-rt.llvm.org/> dragonegg.llvm.org <http://dragonegg.llvm.org/> git.llvm.org

Hi Nelson, Thanks for your reply. The “build/Debug/lib” and "build/Release/lib” directories is where all the libraries go. Similarly, the executables go to “build/Debug/bin” and “build/Release/bin” before they are moved to the install directory. This is expected and normal. However, the problem is that a small number of libraries (exactly 20 in total) are not created at all for the LLVM

CC Tanya and ping. On Mon, Jul 20, 2015 at 1:41 PM, 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

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

I understand that a difference between ninja and xcode is they use a different way to determine code dependencies. So to my understanding xcode needs dependencies to be properly created whereas ninja just doesn’t care. Maybe this is why ninja is able to find what it needs for the compilation to succeed, but not xcode. So I have now looked at the CMakeLists.txt files and found that all the missing

On 10/11/2018 03:27 PM, James Y Knight via llvm-dev wrote: > TLDR: https://github.com/llvm-git-prototype/ exists as a read-only mirror of SVN, and is being updated continuously with a script running on an llvm-project AWS VM. > Hi James, What is the current status of the monorepo, have you resolved all the known issues with the history? Are there any other changes that need to be made

Try using ninja generator, most people do not use Xcode for building, so since it lesser-used, it also lesser tested. Note that it’s perfectly possible to use Xcode for code browsing, debugging, editing while using ninja for building, which is what I think most people do On Sun, Jul 7, 2019 at 4:20 AM Joan Lluch via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I also filled a bug

On Fri, Jul 31, 2015 at 12:01 AM, Dan Liew <dan at su-root.co.uk> wrote: > 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.

Hi Tom, I saw the tags go in and tried to start the builds but it seems that you forgot one: $ LANG=C CFLAGS=-mips32r2 CXXFLAGS=-mips32r2 ./test-release.sh -triple mips-linux-gnu -build-triple mips-linux-gnu -no-64bit -j4 -release 3.5.1 -rc 1 # Validating llvm SVN URL # Validating cfe SVN URL # Validating dragonegg SVN URL # Validating compiler-rt SVN URL # Validating libcxx SVN URL # Validating

I’m not saying you can’t use Xcode, I’m just saying that instead of *building* in Xcode, just type “ninja” on the command line to do your build and then use Xcode as you normally would. I don’t think it’s the case that LLVM does not intend to support Xcode, just that its a community driven project, so unless someone is sufficiently motivated to fix whatever this problem is, it might stay this way

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