[LLVMdev] Building bitcode modules (original) (raw)

Eric Christopher echristo at apple.com
Thu Sep 29 09:23:57 PDT 2011

On Sep 29, 2011, at 12:53 AM, Speziale Ettore wrote:

Hi,

What compiler are you using to build with? I've made it default to clang with less looking around for llvm-gcc, so there may be an issue there. What is your configure line? What host are you trying to build on? First I have compiled llvm/clang compiled with "gcc (Gentoo 4.5.2 p1.1, pie-0.4.5) 4.5.2". Then I have installed llvm/clang. They are in the path: $ clang --version clang version 3.0 (http://llvm.org/git/clang.git 53ce37ff4b44c59e5ac682d4558df980a8a3fa33) Target: x8664-unknown-linux-gnu Thread model: posix My llvm configure line is: ../src/configure --prefix=/home/ettore/work/llvm/root Host: Linux ironman 2.6.35-gentoo-r10 #1 SMP Fri Oct 15 11:35:09 CEST 2010 x8664 Intel(R) Xeon(R) CPU E5335 @ 2.00GHz GenuineIntel GNU/Linux I have added a bitcode library to the sample project I have modified the sample project to show my problem -- patch attached. The warning comes from Makefile.rules:1192. The check is performed over LLVMCC, set at Makefile.rules:428-443. Setting depends on LLVMCCOPTIONS, CLANGPATH, and ENABLEBUILTCLANG. Previously -- I have tried with 3699261d3f49d65cee6a645c849c41cdca51a01f -- these vars was set throught the configure script, now they are not set.

Aha. I see.

I'd forgotten to remove that code when I moved the rest of the compiler support out of the top level configure for llvm. I hadn't realized anyone was using that functionality to build modules.

Out of curiosity what are you using this for? I.e. is it absolutely important to build bitcode modules within the llvm build system?

-eric

More information about the llvm-dev mailing list