search for: xctoolchain

...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: CMAKE_CXX_COMPILER=${LLVM_INSTALL_PATH}/_install/Toolchains/LLVM12.0.0git.xctoolchain/usr/bin/clang++ CMAKE_CXX_STANDARD_LIBRARIES=${LLVM_INSTALL_PATH}/_install/Toolchains/LLVM12.0.0git.xctoolchain/usr/lib CMAKE_CXX_STANDARD_INCLUDE_DIRECTORIES=${LLVM_INSTALL_PATH}/_install/Toolchains/LLVM12.0.0git.xctoolchain/usr/include/c++/v1 Though the compilation works, the link stage fails, a...

...M3.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 "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/6.1.0" \ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk \ … I say partial answer because when I try to compile all of my C++ source files some headers are still not found. But the one source file that I need to...

...rguments using /usr/bin/ld instead of ld64.lld works fine. Here are the details: Here is the call using /usr/bin/ld: /usr/bin/ld HelloObjC.o -o HelloObjC -v -sdk_version 10.14.0 -macosx_version_min 10.14.0 -demangle -lto_library /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libLTO.dylib -dynamic -arch x86_64 -framework Foundation -framework Cocoa -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -lSystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/10....

...e has suggestions on how to do one of the following - I would greatly appreciate it. 1) Running clang built using LLVM3.6.1 (or higher) on OS X doesn’t work because it doesn’t find system header files. I’ve added "-resource-dir /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/6.1.0” to the command line and while versions of this path have worked in the past - it doesn’t work anymore. 2) Using the version of clang provided by Xcode6.4 generates a bitcode file but it cannot be loaded into my language that was compiled using LLVM3.6.1. It complains with the...

...td::__1::default_delete<llvm::orc::MaterializationUnit> >), llvm::orc::JITDylib&, std::__1::unique_ptr<llvm::orc::MaterializationUnit, std::__1::default_delete<llvm::orc::MaterializationUnit> >&&) at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/type_traits:4425 #23 0x00000001062eaef8 in void std::__1::__invoke_void_return_wrapper<void>::__call<void (*&)(llvm::orc::JITDylib&, std::__1::unique_ptr<llvm::orc::MaterializationUnit, std::__1::default_delete<llvm::orc::MaterializationUnit> >), llv...

...arwin18.6.0 checking host system type... x86_64-apple-darwin18.6.0 checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for ld used by gcc... /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld checking if the linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) is GNU ld... no checking for shared library run path origin... done checking 32-bit host C ABI... no checking for the common suffixes of directories in the library search pa...

...gt;), >>>>> llvm::orc::JITDylib&, std::__1::unique_ptr<llvm::orc::MaterializationUnit, >>>>> std::__1::default_delete<llvm::orc::MaterializationUnit> >&&) at >>>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/type_traits:4425 >>>>> >>>>> #23 0x00000001062eaef8 in void >>>>> std::__1::__invoke_void_return_wrapper<void>::__call<void >>>>> (*&)(llvm::orc::JITDylib&, >>>>> std::__1::unique_ptr<l...

...rely on setting a policy to OLD.     -- The C compiler identification isAppleClang 6.0.0.6000057 -- The CXX compiler identificationis AppleClang 6.0.0.6000057 -- The ASM compiler identificationis AppleClang -- Found assembler:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- Check for working C compiler:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- Check for working C compiler:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc-- works -- Detecting C compiler ABI info...

...t_delete<llvm::orc::MaterializationUnit> >), > llvm::orc::JITDylib&, std::__1::unique_ptr<llvm::orc::MaterializationUnit, > std::__1::default_delete<llvm::orc::MaterializationUnit> >&&) at > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/type_traits:4425 > >>>>>>> > >>>>>>> #23 0x00000001062eaef8 in void > std::__1::__invoke_void_return_wrapper<void>::__call<void > (*&)(llvm::orc::JITDylib&, > std::__1::unique_ptr<llvm::orc::Materializat...

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:

...tead of ld64.lld works fine. > > Here are the details: > > Here is the call using /usr/bin/ld: > > /usr/bin/ld HelloObjC.o -o HelloObjC -v -sdk_version 10.14.0 -macosx_version_min 10.14.0 -demangle -lto_library /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libLTO.dylib -dynamic -arch x86_64 -framework Foundation -framework Cocoa -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -lSystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/10...

...s is confusing. In the orig_command_line you can see that src/.libs/libogg.a is passed to the command line and even when running verbose clang I can see that clang invokes the linker with libogg.a on the line: > > "/Applications/Xcode-11.3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld" -demangle -object_path_lto /var/folders/5c/85r7gp0909j5jbytzds1j7b40000gn/T/thinlto-74963a -lto_library /Applications/Xcode-11.3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libLTO.dylib -no_deduplicate -dynamic -arch x86_64 -macosx_version_min 10.15.0 -syslib...

...ow 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.: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++). Is there a way to do that? Thx

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 /var/folders/5c/85r7gp0909j5jbytzds1j7b40000gn/T/thinlto-bf51d2 -lto_library data_files/libLTO.dylib -no_deduplicate -dynamic -arch x86_64 -macosx_version_min 10.15.0 -debug_snapshot -filelist objects/filelist dylibs/libSystem.tbd dylibs/libc++.tbd Steven...

...-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 (52) (Producer: 'LLVM3.9.0' Reader: 'LLVM APPLE_1_800.0.42.1_0') /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar: internal ranlib command failed Using MacPorts, I've been able to confirm that archiving LTO object files now requires a cctools release that has been built against llvm 3.9.0 rather than 3.8.1 to avoid this failure. Was this change intentional and is there any possibility of r...

...EmptyProject17" -objc_abi_version 2 -no_implicit_dylibs -lcrt1.o -syslibroot "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.0.sdk" -force_load "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_iphonesimulator.a" -demangle -ios_simulator_version_min 5.0 I get this error: Undefined symbols for architecture i386: "EH_frame0", referenced from: _main in EmptyProject17 what am i missing here? The asm for this http://pastebin.com/KCSWSDBm doesn't...

...ing > > libc++ along with llvm and clang. > > When I'm not building with libcxx in-tree I find it easiest to just > symlink Xcode's libc++ headers into the build directory. Something > like "ln -s > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++ > build/include". > Thanks Tim, symlink to build include does not help because clang++ looks headers into build/lib/clang/3.9.0/include ( as per output of clang++ -v) but I symlink to /usr/local/include , that worked I hope there is nothing wrong in doing so. -Vivek &g...

How is the LLVM toolchain built for Windows? I'm working on VS integration. Like, in Xcode, the actual *.xctoolchain bundle is built using the regular cmake files, plus using the cmake build script in tools/xcode-toolchain, what is the windows equivalent? is it literally just the stuff in tools/msbuild, or is there more to it than that? -------------- next part -------------- An HTML attachment was scrubbed... U...

...; $ ar cr libtar.a paxerror.o paxexit-status.o paxnames.o rtapelib.o > stdopen.o wordsplit.o xattr-at.o > error: Unknown attribute kind (52) (Producer: 'LLVM3.9.0' Reader: > 'LLVM APPLE_1_800.0.42.1_0') > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar: > internal ranlib command failed > > Using MacPorts, I've been able to confirm that archiving LTO object > files now requires a cctools release that has been built against llvm > 3.9.0 rather than 3.8.1 to avoid this failure. > Was this change intentional and...

....indirect_symbol _data_table .long 0 .subsections_via_symbols /* ==end use_table_m2.s== */ /* ==begin test.c ==*/ extern int data_table[]; int main(void) { int a = data_table[0]; return 0; } /* ==end test.c ==*/ /* ==Makefile== */ CC = /Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang AR = /Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar CFLAG = -fPIC -Wall -arch armv7 -mcpu=cortex-a9 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk all:dynamic static dynamic:test_d_m1_1 test_d_m1_2 test_d_m...