similar to: [LLVMdev] [ exception_ptr ] libcxx doesn't cope well with libcxxabi under linux

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

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 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

> 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. >

All, The following websites will be moving to a new web server in the next few days: clang.llvm.org <http://clang.llvm.org/> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/> compiler-rt.llvm.org <http://compiler-rt.llvm.org/> dragonegg.llvm.org <http://dragonegg.llvm.org/> klee.llvm.org <http://klee.llvm.org/> libclc.llvm.org <http://libclc.llvm.org/>

On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: > >> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org> wrote: ... >> What are all these test failures? Does it seems like they have a >> common root cause and do we have a bug for it? ... > The Clang Tools and Extra Tools Unit tests all appear to crash with: >

We had to roll a release candidate 4 for the 3.5 release. It’s up at the normal place: http://llvm.org/pre-releases/3.5 Please test it and report any major bugs you may find. Thanks! -bw

On 9 Feb 2018, at 22:30, Dimitry Andric <dimitry at andric.com> wrote: > > On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >> >> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>>> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org>

Hi, After a discussion with David, Id like to propose a rework of the Windows target triples. The current set of Windows triples are somewhat less uniform than their Linux counterparts. With multiple ABIs and environments on Windows, they are also slightly awkward. Obviously, certain ones might be nice to keep around for compatibility (e.g. the mingw triple). Just to ensure that everyone has

On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s implementation), so there is no dependency of anything on libc++. Similarly, we support building libc++

On Thu, Aug 03, 2017 at 08:22:24AM -0600, Jonathan Roelofs wrote: > IIUC, you don't want to cross compile llvm itself (which is what those > instructions are for), but instead you want to *use* llvm to cross compile > things. > > To build your sysroot, you'll need to cross-build: > > 1) A libc. Good choices for that for baremetal are: newlib or musl. > 2)

On Wed, Aug 02, 2017 at 05:48:20PM -0600, Jonathan Roelofs wrote: > I strongly recommend against using the host's headers when cross compiling. > You need to either find or build an arm-none-eabi sysroot, and use the > --sysroot= flag. > > > Jon OK, that's a start. I found https://www.llvm.org/docs/HowToCrossCompileLLVM.html. Is it enough for --sysroot? In case it is,

On 28 Jul 2016, at 08:59, Renato Golin <renato.golin at linaro.org> wrote: > > On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s

On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: > > On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> >>> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org> wrote: > ... >>> What are all these test failures? Does it seems like they have a >>>

On Fri, Feb 20, 2015 at 7:02 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > 2. We need to clarify how libstdc++ and libsupc++ can be used as > > libc++'s ABI library and explicitly define the level of support for > > these configurations. Are there any people using this functionality? > > These configurations have been broken for GCC >= 4.9.2 and I haven't

On Sun, Feb 11, 2018 at 3:31 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2018, at 22:30, Dimitry Andric <dimitry at andric.com> wrote: >> >> On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >>> >>> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org>

You may also take a look at the ELLCC project (www.ellcc.org <http://www.ellcc.org/>). As far as I understand it they produce and package cross toolchains for a number of popular targets. - Matthias > On Aug 4, 2017, at 12:54 PM, Jonathan Roelofs via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On 8/4/17 1:14 PM, Goran Mekić via llvm-dev wrote: >> On

I noticed a problem with llvm-config.exe on Windows: >"c:\Users\andy\llvm+clang-6.0.0rc2-win64-msvc-release\bin\llvm-config.exe" --system-libs psapi.lib shell32.lib ole32.lib uuid.lib But then when I link against LLVM and these libs, I get: lld: error: LLVMSupport.lib(Process.obj): undefined symbol: __imp_CryptAcquireContextW lld: error: LLVMSupport.lib(RandomNumberGenerator.obj):

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