[LLVMdev] buildbot failure

Daniel Dunbar daniel_dunbar at apple.com
Mon Dec 12 18:06:28 PST 2011


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

On Dec 12, 2011, at 5:44 PM, Evan Cheng wrote:

> I'm hitting this. Is there ETA for the fix? 
> 
> Evan
> 
> On Dec 12, 2011, at 2:58 PM, Daniel Dunbar wrote:
> 
>> 
>> On Dec 12, 2011, at 2:51 PM, Tony Linthicum wrote:
>> 
>>> On 12/12/2011 4:49 PM, Eric Christopher wrote:
>>>> 
>>>> 
>>>> On Dec 12, 2011, at 2:41 PM, Eric Christopher wrote:
>>>> 
>>>>> 
>>>>> On Dec 12, 2011, at 2:36 PM, Tony Linthicum wrote:
>>>>> 
>>>>>> 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? 
>>>>> 
>>>>> 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 :)
>>>> 
>>>> -eric
>>>> 
>>> 
>>> Excellent!  Daniel, I owe you a beer ... or three. :)
>> 
>> 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! :)
>> 
>>  - Daniel
>> 
>>> 
>>> Tony
>>> 
>> 
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111212/5d127fff/attachment.html>


More information about the llvm-dev mailing list