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? Thanks. Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111212/6665c3b2/attachment.html>
On Dec 12, 2011, at 2:12 PM, Tony Linthicum wrote:> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111212/aa3c3794/attachment.html>
On 12/12/2011 4:28 PM, Jakob Stoklund Olesen wrote:> > On Dec 12, 2011, at 2:12 PM, Tony Linthicum wrote: > >> 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?With configure. I was beginning to suspect it had something to do with that. Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111212/ac17d5bc/attachment.html>
On 12/12/2011 4:28 PM, Jakob Stoklund Olesen wrote:> > On Dec 12, 2011, at 2:12 PM, Tony Linthicum wrote: > >> 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? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111212/f60a8d80/attachment.html>