[lldb-dev] top-of-tree build failure when using configure on Linux?

Ted Woodward via lldb-dev lldb-dev at lists.llvm.org
Wed Sep 9 09:56:40 PDT 2015


I took a look at the buildbots; it looks like another buildbot is failing with the same issue – the debian bot, http://lab.llvm.org:8011/builders/lldb-x86_64-debian-clang . It fails the compile at the same place as the Hexagon Ubuntu bot, and it also uses configure.

 

Google has 2 Ubuntu 14.04 bots up that are building lldb using cmake, so ours will be redundant when we switch it to cmake. If there’s no objection, we’ll just take it down.

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 

From: lldb-dev [mailto:lldb-dev-bounces at lists.llvm.org] On Behalf Of Ted Woodward via lldb-dev
Sent: Thursday, September 03, 2015 1:34 PM
To: 'Zachary Turner'; 'Todd Fiala'
Cc: 'LLDB'
Subject: Re: [lldb-dev] top-of-tree build failure when using configure on Linux?

 

We forced a clean build because it wasn’t picking up an enum change that affected the swig python bindings, and the objective c problem popped up.

 

I’ve built with cmake on that machine, and it worked. I think the right answer is switch to cmake.

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 

From: Zachary Turner [mailto:zturner at google.com] 
Sent: Thursday, September 03, 2015 12:42 PM
To: Todd Fiala; Ted Woodward
Cc: LLDB
Subject: Re: [lldb-dev] top-of-tree build failure when using configure on Linux?

 

Can you change it to CMake instead of configure?  I know that's not what you want to hear, but the configure build is on its way out, so you're going to have to do this at some point anyway.

 

On Thu, Sep 3, 2015 at 10:25 AM Todd Fiala via lldb-dev <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org> > wrote:

I haven't seen that one myself.  Are you still seeing it?

 

Is it possible the buildbot's commands are possibly using older/stale object files?  Is distcc/ccache involved?  Does the build force a clean build?  If not, does the issue go away on a clean build?  Is it configure-based or cmake based?

 

Just some thoughts.  Good luck resolving!

 

-Todd

 

On Fri, Aug 28, 2015 at 10:56 AM, Ted Woodward via lldb-dev <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org> > wrote:

Our Ubuntu 14.10 buildbot at http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.10 is failing, and I’ve been tasked to fix it because I’m the LLDB guy.

 

It fails with things like:

/var/lib/buildbot/slaves/hexagon-build-03/lldb-x86_64-ubuntu-14.10/llvm.obj/Release+Asserts/lib/libclangCodeGen.a(BackendUtil.o): In function `addObjCARCOptPass(llvm::PassManagerBuilder const&, llvm::legacy::PassManagerBase&)':

BackendUtil.cpp:(.text._ZL17addObjCARCOptPassRKN4llvm18PassManagerBuilderERNS_6legacy15PassManagerBaseE+0x21): undefined reference to `llvm::createObjCARCOptPass()'

 

I get the same error when I manually build using the same steps as the bot, but when I use cmake it works.

 

Has anyone seen this behavior using configure?

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 


_______________________________________________
lldb-dev mailing list
lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org> 
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev





 

-- 

-Todd

_______________________________________________
lldb-dev mailing list
lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org> 
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150909/c5c4e3af/attachment-0001.html>


More information about the lldb-dev mailing list