The error that Ted was seeing is now fixed on SVN HEAD. - Bruce
On Thu, Sep 10, 2015 at 12:51 AM, Zachary Turner via lldb-dev < lldb-dev@lists.llvm.org> wrote: > The community's current plan of record is still to kill the autoconf build > but there is no definitive timeline on when it will be complete. But to > answer your question, yes it is across all projects. > > From the LLDB side, I don't know if anyone depends on having a working > autoconf build for production reasons. The last time I heard, it was only > still around because some people were still running autoconf-based > buildbots. It's possible I'm forgetting about something or someone, but > that was my understanding. > > On Wed, Sep 9, 2015 at 10:39 AM Rick Foos via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> 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. >> >> Zachary, is the decision to drop autoconf across all projects or just >> LLDB? The last time I proposed a cmake change, I was asked to add the >> equivalent for autoconf. >> (if autoconf is deprecated, I have some other builders starting that I >> need to switch to cmake) >> >> Ted, I was going to remove the builder before I left but didn't have >> time. The tests were not going to be fixed for autoconf builds. BTW >> hexagon-build-03 is up to date Ubuntu 15.04 if you care about the newer gcc >> version. >> >> >> - Rick >> >> >> On 09/09/2015 11:56 AM, Ted Woodward via lldb-dev wrote: >> >> 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> >> 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-boun...@lists.llvm.org >> <lldb-dev-boun...@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:ztur...@google.com <ztur...@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@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@lists.llvm.org>lldb-dev@lists.llvm.org> wrote: >> >> Our Ubuntu 14.10 buildbot at >> <http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.10> >> 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@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> >> >> >> >> -- >> >> -Todd >> >> _______________________________________________ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> >> _______________________________________________ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
