The validator buildbot builds llvm-gcc and installs it in a non-standard
location. It then reconfigures llvm with
--with-llvmgccdir=<llvm-gcc_prefix>
I see this code in llvmc/Base/Base.td:
def llvm_gcc_c : llvm_gcc_based<"llvm-gcc -x c", "c",
"i">;
def llvm_gcc_cpp : llvm_gcc_based<"llvm-g++ -x c++",
"c++", "i">;
def llvm_gcc_m : llvm_gcc_based<"llvm-gcc -x objective-c",
"objective-c",
"mi">;
def llvm_gcc_mxx : llvm_gcc_based<"llvm-gcc -x objective-c++",
"objective-c++", "mi">;
LLVMGCCDIR appears nowerhe. Shouldn't this be a .td.in file and processed
by
configure? As it is now, llvmc doesn't work because it can't find
llvm-gcc
and llvm-g++.
-Dave
Hi, David Greene <dag <at> cray.com> writes:> > The validator buildbot builds llvm-gcc and installs it in a non-standard > location. > [...] > LLVMGCCDIR appears nowerhe. Shouldn't this be a .td.in file and processed by > configure? As it is now, llvmc doesn't work because it can't find llvm-gcc > and llvm-g++.Fixed. Thanks for the bug report!
Apparently Analagous Threads
- [LLVMdev] Problem with stock llvmc configuration for C
- [LLVMdev] Problem with stock llvmc configuration for C
- [LLVMdev] Problem with stock llvmc configuration for C
- [LLVMdev] Problem with stock llvmc configuration for C
- [LLVMdev] inconsistent use of LLVMGCCDIR?