search for: 092150

Jeremy, At this point the belief is that there are no issues left blocking removing autoconf. The plan is to remove it after the 3.8 branch. In case you missed the thread where that was decided it is here (http://lists.llvm.org/pipermail/llvm-dev/2015-November/092150.html <http://lists.llvm.org/pipermail/llvm-dev/2015-November/092150.html>). This discussion has been going on for over a year, so it shouldn’t be a surprise. I see the issues you reported, I don’t consider any of them to be blocking because they can all be worked around. That doesn’t mean I...

...the autoconf build system is removed? > > eg: https://llvm.org/bugs/show_bug.cgi?id=19465 Chris Bieneman has been posting regular updates to the list on the current status, listing issues viewed as 'blocking'. e.g. the recent RFC http://lists.llvm.org/pipermail/llvm-dev/2015-November/092150.html or late October update http://lists.llvm.org/pipermail/llvm-dev/2015-October/091798.html. I don't think this information has all been entered in to bugzilla, but a tracking bug could make sense if it doesn't already exist. Responding to the RFC on removing autoconf thread with any out...

Hi! If I'm not mistaken old makefiles are not supported in 3.8. If this is a case, i think till be good idea to remove them before 3.8 branching. Eugene.

The purpose of this thread was to propose removing configure on January 26th. There have been no objections, so I’m assuming that timeline is acceptable. -Chris > On Jan 15, 2016, at 5:54 AM, Krzysztof Parzyszek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 1/15/2016 5:05 AM, Daniel Sanders via llvm-dev wrote: >>> One issue that I believe has not yet been

LLVM Weekly - #98, Nov 16th 2015 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/98>. Welcome to the ninety-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex Bradbury](http://asbradbury.org).