similar to: cmake 3.7.0-rc1 breaks stage2 bootstrap in openmp on 10.11 with Xcode 8

Displaying 20 results from an estimated 4000 matches similar to: "cmake 3.7.0-rc1 breaks stage2 bootstrap in openmp on 10.11 with Xcode 8"

2015 Jul 05
2
[LLVMdev] How to run LLVM3.6.1 on OS X (Yosemite, Xcode6.4) OR how to link bitcode generated by OS X clang with LLVM3.6.1
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
2015 Jul 08
2
[LLVMdev] How to run LLVM3.6.1 on OS X (Yosemite, Xcode6.4) OR how to link bitcode generated by OS X clang with LLVM3.6.1
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
2016 Jun 23
4
[cfe-dev] clang++ build from source is not able to find C++ headers
Hi Vivek, you can also include these lines below to your ~/.bash_profile: LLVM_BUILD="/Developer/llvm/build" # Path to your build directory alias new-clang="$LLVM_BUILD/bin/clang -Wno-expansion-to-defined -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include" alias new-clang++="$LLVM_BUILD/bin/clang++
2020 May 07
2
Ld64.lld cannot find Foundation framework
Dear LLVM community I need some help please. I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang. The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework". However similar arguments using /usr/bin/ld instead of ld64.lld works fine. Here are the
2013 Mar 07
2
[LLVMdev] ARM assembler's syntax in clang
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
2020 Nov 05
1
How to use mainline clang/llvm with CMake
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:
2013 Mar 06
3
[LLVMdev] ARM assembler's syntax in clang
Hi Ashi, Your first LDR is a pseudoinstruction that is supported by some tools (gas and armasm, at least), but not by LLVM. Roughly speaking, it turns into a PC-relative load from a literal pool. To do what you're trying to achieve you can write your own literal pool in your assembly. You can see some examples of this sort of thing at
2012 Dec 19
2
[LLVMdev] LLVM 3.2 on Xcode
Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM 3.2 (with clang, extras, and compiler-rt) building - but not testing - on Xcode. I used CMake 2.8.10 GUI to create the Xcode project file. Below are my notes. First, I believe CMake ends up setting things up so that Xcode has 1 warning after scanning the project having to do with hires images or some such… it takes
2015 Oct 12
2
Clang includes search path
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.:
2020 Jul 22
2
How to debug a missing symbol with ThinLTO?
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
2020 Jul 23
2
How to debug a missing symbol with ThinLTO?
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
2013 Nov 10
3
[LLVMdev] [Reminder] LLVM 3.4 Release Branching
Good day! This is just a reminder that branching for the 3.4 release will occur at this time: Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC What this means for you! ------------------------ * Please keep the release notes up to date -- There has been very few commits to them. Please be proactive and update them with any significant feature that was
2013 Mar 07
0
[LLVMdev] ARM assembler's syntax in clang
Hi, Bernie, Thanks for your reply! However, I still have problem by following edk2's code, my test code is attached, what I want to do is build it as a dynamic lib. But I get error from ld: ld: illegal text-relocation to _data_table in table.o from foo in use_table.o for architecture armv7 Do you have any suggestion to solve this? Thanks! //==begin table.c== int data_table[] = {0xff, 0xff};
2013 Mar 08
0
[LLVMdev] ARM assembler's syntax in clang
> And be warned that the PC doesn't point at the next instruction when you use it like this - I believe you don't need to modify it at all if you swap the pop and the .long. Bernie, is it related to ARM pipeline? I'm interesting in this, is there any other additional information? On Fri, Mar 8, 2013 at 4:59 AM, Tim Northover <t.p.northover at gmail.com>wrote: > Hi Ashi,
2013 Nov 11
2
[LLVMdev] [cfe-dev] [Reminder] LLVM 3.4 Release Branching
Jack, Where do the "-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -mmacosx-version-min=10.8" flags come from? I don't see them in your CMake invocation - perhaps they're added via $CC or $CFLAGS? Is this being done on purpose? I can add a CMake step checking whether the current CFLAGS/LDFLAGS allow to build an
2013 Nov 10
0
[LLVMdev] [Reminder] LLVM 3.4 Release Branching
On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > Good day! > > This is just a reminder that branching for the 3.4 release will occur at this time: > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC > > What this means for you! > ------------------------ > > * Please keep the release notes up to date --
2012 Dec 21
2
[LLVMdev] LLVM 3.2 on Xcode
Hi Richard! On Thu, Dec 20, 2012 at 12:48 AM, Nick Kledzik <kledzik at apple.com> wrote: > Those look like the linker is being passed the same .o file built twice, > ex: > ../Objects-normal/x86_64/asan_globals_test.o > ../lib/asan/tests/asan_globals_test.cc.asan.o > > So, the symbols are colliding. Something is set up wrong in the xcode > project. > > -Nick
2013 Nov 11
2
[LLVMdev] [cfe-dev] [Reminder] LLVM 3.4 Release Branching
This file is for configure+make build, not CMake, so I'm not sure why it's being included into your build (these failures aren't reproducible for me). Can you please list the exact steps you're doing to build LLVM with CMake and make sure you don't have additional CFLAGS (LDFLAGS etc) defined? On Mon, Nov 11, 2013 at 6:16 PM, Jack Howarth <howarth at bromo.med.uc.edu>
2013 Nov 11
0
[LLVMdev] [cfe-dev] [Reminder] LLVM 3.4 Release Branching
On Mon, Nov 11, 2013 at 01:59:25PM +0400, Alexander Potapenko wrote: > Jack, > > Where do the "-isysroot > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk > -mmacosx-version-min=10.8" flags come from? I don't see them in your > CMake invocation - perhaps they're added via $CC or $CFLAGS? Is this > being done
2013 Nov 11
2
[LLVMdev] [cfe-dev] [Reminder] LLVM 3.4 Release Branching
On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > This file is for configure+make build, not CMake, so I'm not sure why > > it's being included into your build (these failures aren't > > reproducible for me). > > Can you please list the exact steps you're doing to build