On Sat, Mar 28, 2015, at 12:52 PM, Amit Kulkarni wrote: > On Thu, Mar 19, 2015 at 6:07 PM, Aaron Bieber <[email protected]> > wrote: > > > Should have mentioned what the current hurdles are. So far the build > > dies because of a few lacking items: > > > > 1) libunwind (needed for the GC, also I am told this is not a hard > > requirement) > > 2) lldb > > > > For lldb to be ported, the llvm/clang versions should be kept in sync. I > tried this a few years ago with matthew@, but we gave up since tehre were > too many ifdef with the POSIX string functions. I do believe that the > situation has improved a lot since then, since a ton of stuff has been > ported from FreeBSD/NetBSD. IMHO, a pre-requisite for porting lldb is to > sync the llvm port to the latest upstream release. I understand from > reading the commits that Brad has joined long term clang porting effort > and > we have effectively forked llvm/clang to do our own stable long term > compiler as referenced by Miod a few years ago. IMHO a different port of > llvm/clang which follows latest upstream needs to be imported into the > tree. Is it time for the current llvm/clang port to be imported into base > but unlinked to the tree and make way for the latest llvm/clang port? > > Thanks
I am not too familiar with other things that require llvm/clang - but for sure CoreCLR is currently targeting llvm/clang 3.5.
