"recent libcxx regression" reason discovered. clang version info/folder changed. possibly accidental?

[Tom Stellard]

On Tue, Mar 11, 2014 at 10:10:22AM +1300, G M wrote:
> Hi Tom
> 
> On Tue, Mar 11, 2014 at 3:27 AM, Tom Stellard <tom at stellard.net> wrote:
> 
> >
> > Is autoconf supported on windows?  If not, then this shouldn't be a
> > problem, because
> > in CMake I'm only creating the symlink on non-WIN32 platforms (I'm not a
> > CMake expert,
> > though, so it would be nice if someone could test this).
> >
> 
> 
> >
> > -Tom
> >
> >
> I don't know too much about autoconf. I'm not sure when you ask about
> "supported" whether you mean does it run or does lllvm/clang support
> running it on Windows
>

By supported, I mean do we need to make sure that the autoconf build is
working on windows.

-Tom



> From distant memory, I thought I used it on Windows when I first got
> interested in clang/llvm before they supported cmake.
> 
> So I think it runs on Windows and was useful at one point, and here's a
> link I found to it for windows:
> http://gnuwin32.sourceforge.net/packages/autoconf.htm
> 
> As for supported, I don't know if autoconf use is kept up to date on
> Windows or not for llvm/clang. But I certainly don't use it anymore on
> Windows, I switched to cmake long long ago. I imagine most Windows centric
> people would be of the same mind-set, but that's a guess.