search for: intrinsics_bitcode_boehm

...ersions 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 following message: Linking app-resources:lib;release;intrinsics_bitcode_boehm.o warning: ignoring debug info with an invalid version (602053001) in /Users/meister/Development/clasp/build/clasp/Contents/Resources/lib/release/intrinsics_bitcode_boehm.o warning: Linking two modules of different target triples: /Users/meister/Development/clasp/build/clasp/Contents/Resources/lib/...

...those headers at any given point in time. Do you know what you would set “-isysroot” to on OS X to get clang3.6.1 to run on OS X? > >> I always thought that this was just a warning but now that I look at the resulting bitcode file after linking I see that no inlining of the functions in intrinsics_bitcode_boehm.o (this is a bitcode file and not a .o file as the extension suggests) is taking place. > > They look like reasonably harmless warnings to me too. The true test > of whether it's worked is going to be whether the output file runs > correctly though, rather than whether LLVM decided...