similar to: Ld64.lld cannot find Foundation framework

Thanks for your reply. Two questions: 1). Will ld64.lld be fixed in LLVM v11.0 and when is this likely to be? 2). You mention Apple’s linker, by which I assume you mean GNU’s ld. Is it possible to get a binary version of ld (preferably that does not use other things from /usr/bin)? Thanks > On 7 May 2020, at 12:26, James Y Knight <jyknight at google.com> wrote: > > The MachO

Looks like your static library is not even pulled into the link command so the static library is not even in the snapshot. From the link command in the snapshot, the static library is not on the command line from snapshot: /Applications/Xcode-11.3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld -Z -demangle -object_path_lto

Hi Tobias The problem is that your static archive has a SYMDEF that is empty, so linker thinks the static library provided doesn't contain any symbol. The reason for that is you are using the `ranlib` from Xcode, which is too old to understand the new bitcode object files produced by llvm 10. There are lots of ways to fix that: * The standard way to create static library on macOS is to use

Thank you. I found a partial answer to the problem (1), namely “how to run Clang compiled with LLVM3.6.1 on OS X Yosemite/Xcode6.4" It’s a combination of -isysroot and -resource-dir I’m using these compiler options: "/Users/meister/Development/externals-clasp/build/release/bin/clang" -v \ -resource-dir

I’m developing a Common Lisp compiler for OS X and Linux that uses LLVM as its backend and interoperates with C++. It’s at: github.com/drmeister/clang I need to compile one C++ source file containing small, intrinsic functions into an LLVM-IR bitcode file and link it with bitcode generated by my compiler running LLVM3.6.1. I have been unable to do this for more than a year and I was hoping

Hello, I am trying to run this basic C++ hello-world code in my iOS app that has LLVM libraries linked in (the app runs on the actual device - iPad Pro, iOS 13.4.1). #include <iostream> int main (int argh, char *argv[]) { std::cout << "Hello World!" << std::endl; return 0; } So below is the break down of the steps that I do: First I compile this code to an

linking this IR file: http://pastebin.com/HnUsSshB with triple i386-apple-ios to an .o file and linking it using: ld -arch i386 -ObjC "EmptyProject17.o" -lSystem -lobjc -framework CoreGraphics -framework Foundation -framework UIKit -dynamic -o "i386-EmptyProject17" -objc_abi_version 2 -no_implicit_dylibs -lcrt1.o -syslibroot

Hi Lang, Please see below is the trace. -- Thanks, Igor *2020-06-06 12:05:21.016705-0400 CppDevProCompiler[6613:3000073] Running...* *jitLink_MachO: magic = 0xfeedfacf, identifier = "llvm-link.submodule-jitted-objectbuffer"* *jitLink_MachO: cputype = 0x0100000c, cpusubtype = 0x00000000* *Creating normalized sections...* * __text: 0x0000000000000000 -- 0x0000000000000064, align:

The new cmake 3.7.0-rc1 release produces a stage2 bootstrap failure in openmp project build on OS X 10.11 under Xcode 8.... In file included from /sw/src/fink.build/llvm40-4.0.0-1/llvm-4.0.0.src/projects/openmp/runtime/src/kmp_alloc.c:16: In file included from /sw/src/fink.build/llvm40-4.0.0-1/llvm-4.0.0.src/projects/openmp/runtime/src/kmp.h:98:

Hi All, I am trying to build the 'lld' linker on Mac OS 10.9, but during the build, I am getting the errors. Following are the steps that I have followed: 1.     I have downloaded the ‘llvm-stable’ source code from the following location:   https://github.com/llvm-mirror/llvm/tree/stable   2.     Machine details(on which llvm source code isbeing built) are as follows: $ sw_vers

Hi Dave, Yep. This is JITLink specific, so we could only have observed it on MachO x86-64 or arm64 until recently. It takes a little bit of poking to get IR to produce a zero-lengh section on MachO, but not much. Jared Wyles recently contributed an initial JITLink ELF implementation, so the fix seems timely -- we might have been about to see more of it. -- Lang. On Fri, Jun 19, 2020 at 4:02 PM

Dear all, I am not sure whether this is a right place to ask basic questions about usage of CLang/LLVM, but also not sure if there is any other mailing list for such. Kindly point me to such a list in such case. I had built mainline CLang/LLVM on OSX and tried to use it with CMake. I had override following variables in CMake:

Hi, I’m trying to set the includes search path in clang, but I can’t figure out how to do it? I’m working on OSX and every time I compile a C/C++ code, I have to specify it with -isysroot (and I don’t want an alias, or a symlink to /usr/include) since the includes are not in a really standard path on OSX (e.g.:

The ability to archive object files generated with -flto under LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently shipping Xcode releases including the upcoming Xcode 8.1 GM. https://llvm.org/bugs/show_bug.cgi?id=30791 $ clang-3.9 -flto -O1 -c *.i $ ar cr libtar.a paxerror.o paxexit-status.o paxnames.o rtapelib.o stdopen.o wordsplit.o xattr-at.o error: Unknown attribute kind

Hello, I am running OS X, when I build clang++ from source and use it to compile .cpp files it fails as it is not able to find C++ header. I am not building libc++ along with llvm and clang. using -stdlib=libstdc++ solves problem partially but it fails when using C++11 threads, again it can't find <thread>, to get this work clang++ should work with -stdlib=libc++ but it fails with

Hi Ashi, > ld: illegal text-relocation to _data_table in table.o from foo in > use_table.o for architecture armv7 It looks like you're using iOS. I'm not familiar with the exact workings of that platform, but I think a similar message would occur in ELF-land. If iOS *is* comparable, your issue is that symbols in dynamically loaded objects can't (usually) be referenced directly

Yes, that’s right. Some LLVM terminology though: The blocks you mention, are called the “exiting blocks” of the loop, and the blocks outside the loop (that are the targets of these exiting blocks) are called the exit blocks. getExitingBlocks in LoopInfoImpl.h is the code you’re interested in. By definition: one of the successor’s of the exiting block is an exit block, and it should have another

Hello, May I ask anyone responsible to either fix or revert r326109 and r326110, which effectively broke LLVM compilation with clang? Str is const now (https://reviews.llvm.org/D43436#C985082NL45 <https://reviews.llvm.org/D43436#C985082NL45>), and later on a move constructor on const is performed (https://reviews.llvm.org/D43436#C985082NL64

On Thu, Jun 23, 2016 at 7:36 PM, Tim Northover <t.p.northover at gmail.com> wrote: > On 23 June 2016 at 06:31, vivek pandya via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > I am running OS X, when I build clang++ from source and use it to compile > > .cpp files it fails as it is not able to find C++ header. I am not > building > > libc++ along with llvm

Hi, I've got an assembly file which used to compile with previous clang versions. However with 4.2 I get the following error: admin$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch armv7 ./src/asm.s -o asm.o ./src/asm.s:30:5: error: instruction requires a CPU feature not currently enabled add r2, pc, r2 According to ARM