similar to: RFC: Default path for cross-compiled runtimes

Displaying 20 results from an estimated 20000 matches similar to: "RFC: Default path for cross-compiled runtimes"

2017 Dec 19
2
RFC: Default path for cross-compiled runtimes
On Tue, Dec 19, 2017 at 8:33 AM Jonathan Roelofs <jonathan at codesourcery.com> wrote: > On 12/19/17 9:15 AM, Petr Hosek via llvm-dev wrote: > > Today, there're two different locations for runtimes files within > > Clang's installation: > > > > compiler-rt: > > headers: $prefix/lib/clang/$version/include(/sanitizer) > > libraries: >
2017 Dec 30
1
RFC: Default path for cross-compiled runtimes
On Tue, Dec 19, 2017 at 12:33 PM Jonathan Roelofs <jonathan at codesourcery.com> wrote: > On 12/19/17 12:53 PM, Petr Hosek wrote: > > On Tue, Dec 19, 2017 at 8:33 AM Jonathan Roelofs < > jonathan at codesourcery.com> wrote: > >> On 12/19/17 9:15 AM, Petr Hosek via llvm-dev wrote: >> > Today, there're two different locations for runtimes files within
2020 Apr 08
2
Clarifying the supported ways to build libc++, libc++abi and libunwind
Thanks Shoaib for a great summary. To summarize this as an answer to Louis' questions: 1. What is a "Standalone build"? What does it enable that a normal monorepo build can't? This means building any of the runtimes separately, where the runtime's CMakeLists.txt (e.g. path/to/my/llvm-project/libcxx/CMakeLists.txt) is the top-level one. The reason for using this variant is
2020 Apr 08
4
Clarifying the supported ways to build libc++, libc++abi and libunwind
[Cross-post to llvm-dev to make sure everybody relevant sees this] Hi, I'm currently trying to simplify the libc++/libc++abi/libunwind build systems and testing setup. In doing so, I am encountering issues related to "unusual" ways of building them. By unusual, I just mean "not the usual monorepo build with LLVM_ENABLE_PROJECTS". I would like to pin down what the set of
2016 Dec 19
0
libcompiler_rt.so and libcompiler_rt.a are not being built
> On Dec 18, 2016, at 3:48 AM, Dmitry Golovin <dima at golovin.in> wrote: > > > > 16.12.2016, 18:23, "Vedant Kumar" <vsk at apple.com>: >>> On Dec 16, 2016, at 7:06 AM, Dmitry Golovin via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and
2016 Dec 18
3
libcompiler_rt.so and libcompiler_rt.a are not being built
16.12.2016, 18:23, "Vedant Kumar" <vsk at apple.com>: >>  On Dec 16, 2016, at 7:06 AM, Dmitry Golovin via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >>  I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are
2018 Dec 27
2
[CMake] CMAKE_TOOLCHAIN_FILE and projects
Hi, I'm working on cross-compiling llvm and sub-projects to dynamically build Clang toolchain and associated libraries for an embedded project. I'm starting with this mailing list, as I see the pattern using "config-ix.cmake" a common one; it's found in all the sub-projects. For those that are not aware, in CMake the standard approach for dealing with unique toolchains,
2018 Feb 09
2
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 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. >> >>
2015 Sep 07
4
LibC++ tests in tree
Folks, I'm running the libc++ tests in tree [1] and I'm seeing two class of errors: 1. -lrt is used, but there is no such "librt.a" in the path. Results are that some symbols are not found, or that the DSO object wasn't. Adding a symlink in build/lib/librt.a to build/clang/3.8.0/lib/linux/libclang_rt.builtins-aarch64.a worked. 2. "collate_byname failed to construct
2018 Oct 01
2
How to build LLVM linked to libc++abi?
Thanks a lot, but tried it and I get this: CMake Error at projects/libcxx/CMakeLists.txt:361 (message): LIBCXX_ENABLE_STATIC_ABI_LIBRARY is not supported on OS X Why is it not supported? If I manually embed libc++abi.a inside libc++.a it seems to work. Thanks! ardi On Mon, Oct 1, 2018 at 4:20 AM Petr Hosek <phosek at chromium.org> wrote: > > You can use
2018 Mar 05
2
[Release-testers] [6.0.0 Release] The final tag is in
Isn't libc++.so dependent on libc++abi.so? On Mon, Mar 5, 2018 at 10:30 AM, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: > From what I can see all of the libraries without RPATH are runtime > libraries that are used by binaries compiled with Clang. I think they don't > have a dependency on other libraries in that directory, so what would be > the advantage of having
2018 Mar 05
0
[Release-testers] [6.0.0 Release] The final tag is in
libc++.so should be a linker script that automatically pulls in libc++abi (see "Failed to read file header" in your output). And IIRC libc++abi is only one possible implementation that may be used by libc++, but I'm no expert here... Am 2018-03-05 17:33, schrieb Brian Cain: > Isn't libc++.so dependent on libc++abi.so? > > On Mon, Mar 5, 2018 at 10:30 AM, Jonas
2018 Mar 05
2
[Release-testers] [6.0.0 Release] The final tag is in
It was just brought to my attention that the RPATH configuration isn't uniform among the libraries produced by the release. Some use $ORIGIN../lib/ and others have none. Is this by design? It seems like it might be ideal for all of them to be configured the same way. If that makes sense I'll create a corresponding feature request. $ for f in
2018 Mar 05
0
[Release-testers] [6.0.0 Release] The final tag is in
From what I can see all of the libraries without RPATH are runtime libraries that are used by binaries compiled with Clang. I think they don't have a dependency on other libraries in that directory, so what would be the advantage of having RPATH set on them? Regards, Jonas Am 2018-03-05 17:23, schrieb Brian Cain via llvm-dev: > It was just brought to my attention that the RPATH
2019 Mar 25
3
Trying to create a pure LLVM toolchain on musl based distribution
Hello, I'm trying to create a pure LLVM toolchain (that will not depend on GNU and produce GNU-free code too) on a musl based distribution. For now, I use gcc to bootstrap and build all LLVM components. I do it individually because I was running out of space and memory trying to build all using LLVM_ENABLE_PROJECTS. Also, I don't want to create a all-in-one package. Then, once
2020 Nov 06
1
Building an LLVM cross-compiler
On Fri, 6 Nov 2020, Cág via llvm-dev wrote: > The process, in my opinion, should go like this: > 1. Get the sources (llvm, lld, compiler-rt, libunwind, libcxx...). > 2. Build an LLVM cross-compiler toolchain using native distribution's > compiler (i.e. build an x86_64 clang executable that targets aarch64). > 3. Cross-compile libc and other libraries/dependencies to run the
2020 Jun 18
4
RFC: A top level monorepo CMake file
On 06/18/2020 11:27 AM, Steven Wu via llvm-dev wrote: > I like the proposal but I would like to go even further. If we are going to create a top level CMake file, we should just go ahead and eliminate all the standalone build configuration. The standalone build should just be `cmake <monorepo-root> -DLLVM_ENABLE_PROJECTS=standalone-project ...`. That means less build configuration to
2016 Dec 16
0
libcompiler_rt.so and libcompiler_rt.a are not being built
> On Dec 16, 2016, at 7:06 AM, Dmitry Golovin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. > > I'm
2018 Aug 30
4
crash problem when using IndirectBrInst to replace BranchInst
Hello all, I have written a pass, which replaces condition branchinst using indirectBr to obfuscate program. The origin IR is as the following: br i1 %1, label %2, label %3 And the transformed IR is as the follwoing: %4 = select i1 %1, i8* blockaddress(@func, %2), i8* blockaddress(@func, %3) indirectbr i8* %4, [label %2, label %3] The pass's core function is as the
2018 Sep 30
2
How to build LLVM linked to libc++abi?
Hi! I sometimes build LLVM with a static libc++.a in MacOS, so that I use the LLVM libc++ instead of the system-wide one. However, when doing so, I always get link errors when building LLVM, because the build system links with libc++.a, but not with libc++abi.a and so there are quite a few missing symbols that the linker cannot find. My workaround (which always seems to work) is to embed