buildbot failure

Hi folks,

I just committed a new backend for the Hexagon processor. After committing, I was able to successfully check out, build and test with the new changes. The x86_64 build on the buildbot is failing, however. Here’s the build error:

FWIW, I am getting the same linker errors on OS X:

Undefined symbols for architecture x86_64:
“_LLVMInitializeHexagonAsmPrinter”, referenced from:
LTOCodeGenerator::LTOCodeGenerator() in LTOCodeGenerator.o
“_LLVMInitializeHexagonTargetMC”, referenced from:
LTOCodeGenerator::LTOCodeGenerator() in LTOCodeGenerator.o
LTOModule::makeLTOModule(llvm::MemoryBuffer*, std::string&) in LTOModule.o
“_LLVMInitializeHexagonTarget”, referenced from:
llvm::InitializeAllTargets() in LTOCodeGenerator.o
“_LLVMInitializeHexagonTargetInfo”, referenced from:
llvm::InitializeAllTargets() in LTOCodeGenerator.o
ld: symbol(s) not found for architecture x86_64

Are you building with CMake or configure?

/jakob

With configure. I was beginning to suspect it had something to do with that.

Tony

I should have asked, but is the buildbot using CMake? Assuming that’s the issue, I need to get CMake installed on my build machine to find and fix the problem. Is there anything I can do in the interim to keep others from being blocked by this?

Thanks.

Tony

Hi folks,

I just committed a new backend for the Hexagon processor. After committing, I was able to successfully check out, build and test with the new changes. The x86_64 build on the buildbot is failing, however. Here’s the build error:

llvm[2]: Linking Debug+Asserts executable llvm-mc
/home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()':
llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo'
/home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetMCs()':
llvm-mc.cpp:(.text._ZN4llvm22InitializeAllTargetMCsEv[llvm::InitializeAllTargetMCs()]+0x5): undefined reference to `LLVMInitializeHexagonTargetMC'

It certainly looks like something wasn't checked in, but I don't find anything and
my fresh checkout should have failed as well.  Any suggestions as to what I could 
have done wrong?

FWIW, I am getting the same linker errors on OS X:

Undefined symbols for architecture x86_64:
“_LLVMInitializeHexagonAsmPrinter”, referenced from:
LTOCodeGenerator::LTOCodeGenerator() in LTOCodeGenerator.o
“_LLVMInitializeHexagonTargetMC”, referenced from:
LTOCodeGenerator::LTOCodeGenerator() in LTOCodeGenerator.o
LTOModule::makeLTOModule(llvm::MemoryBuffer*, std::string&) in LTOModule.o
“_LLVMInitializeHexagonTarget”, referenced from:
llvm::InitializeAllTargets() in LTOCodeGenerator.o
“_LLVMInitializeHexagonTargetInfo”, referenced from:
llvm::InitializeAllTargets() in LTOCodeGenerator.o
ld: symbol(s) not found for architecture x86_64

Are you building with CMake or configure?

/jakob

I should have asked, but is the buildbot using CMake?

No, most of us internally can’t build it either using autoconf at the moment.

Assuming that’s the issue, I need to get CMake installed on my build machine to find and fix the problem. Is there anything I can do in the interim to keep others from being blocked by this?

Revert unfortunately, but I’m looking at it.

-eric

Daniel is fixing it :slight_smile:

-eric

Excellent! Daniel, I owe you a beer … or three. :slight_smile:

Tony

Hi folks,

I just committed a new backend for the Hexagon processor. After committing, I was able to successfully check out, build and test with the new changes. The x86_64 build on the buildbot is failing, however. Here’s the build error:

llvm[2]: Linking Debug+Asserts executable llvm-mc
/home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()':
llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo'
/home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetMCs()':
llvm-mc.cpp:(.text._ZN4llvm22InitializeAllTargetMCsEv[llvm::InitializeAllTargetMCs()]+0x5): undefined reference to `LLVMInitializeHexagonTargetMC'

It certainly looks like something wasn't checked in, but I don't find anything and
my fresh checkout should have failed as well.  Any suggestions as to what I could 
have done wrong?

FWIW, I am getting the same linker errors on OS X:

Undefined symbols for architecture x86_64:
“_LLVMInitializeHexagonAsmPrinter”, referenced from:
LTOCodeGenerator::LTOCodeGenerator() in LTOCodeGenerator.o
“_LLVMInitializeHexagonTargetMC”, referenced from:
LTOCodeGenerator::LTOCodeGenerator() in LTOCodeGenerator.o
LTOModule::makeLTOModule(llvm::MemoryBuffer*, std::string&) in LTOModule.o
“_LLVMInitializeHexagonTarget”, referenced from:
llvm::InitializeAllTargets() in LTOCodeGenerator.o
“_LLVMInitializeHexagonTargetInfo”, referenced from:
llvm::InitializeAllTargets() in LTOCodeGenerator.o
ld: symbol(s) not found for architecture x86_64

Are you building with CMake or configure?

/jakob

I should have asked, but is the buildbot using CMake?

No, most of us internally can’t build it either using autoconf at the moment.

Assuming that’s the issue, I need to get CMake installed on my build machine to find and fix the problem. Is there anything I can do in the interim to keep others from being blocked by this?

Revert unfortunately, but I’m looking at it.

Daniel is fixing it :slight_smile:

-eric

Excellent! Daniel, I owe you a beer … or three. :slight_smile:

Well, not really, it was just an llvm-build bug that I was already in the process of fixing. So it was my fault all along – shame I didn’t comment a tad faster and then maybe no one would have known! :slight_smile:

  • Daniel

I’m hitting this. Is there ETA for the fix?

Evan

I thought it was already fixed, so no.

I hate to say this, but can you try first:
touch $LLVM_SRC_ROOT/LLVMBuild.txt
and a make? If that doesn’t work, try a make clean? I’ll try and find a real fix tomorrow.

  • Daniel

I had the same problem on one machine. Running "make clean" doesn't work, but touching LLVMBuild.txt fixed the problem.

/jakob

I thought it was already fixed, so no.

I hate to say this, but can you try first:
touch $LLVM_SRC_ROOT/LLVMBuild.txt
and a make? If that doesn't work, try a make clean? I'll try and find a real fix tomorrow.

I had the same problem on one machine. Running "make clean" doesn't work, but touching LLVMBuild.txt fixed the problem.

Ok, I'll try this. Thanks guys.

Evan