[LLVMdev] [cfe-dev] RFC: Dropping support for building sanitizers with autotools (original) (raw)

Nico Weber thakis at chromium.org
Fri Feb 13 13:16:00 PST 2015

Sounds fine to me, but be aware that some of the libraries in compiler-rt other than the sanitizers currently are only built correctly in the autotools build (for example, I think libprofile_rt for iOS isn't built correctly in the cmake build).

On Thu, Feb 12, 2015 at 6:31 PM, Alexey Samsonov <vonosmas at gmail.com> wrote:

Hi everyone,

TL;DR I plan to do subj unless anyone objects. Autotools support for building sanitizers was never complete, is a proper subset of CMake capabilities, and the gap between the features of CMake build and autotools is quickly increasing: 1) OS: autotools support Linux, Mac OS X and Android; CMake also supports FreeBSD and Windows. 2) Architectures: autotools support i386 and x8664, CMake also supports MIPS, ARM/AArch64, PowerPC). 3) Library variants: autotools don't support building shared ASan runtime on Linux. 4 [!!!]) Autotools build doesn't have any support for building and running tests. 5) The sets of compiler flags we use to build runtimes are different in two builds, and are hard to kept in sync. Because of (4), sanitizer runtimes built with autotools are severely undertested, and maintaining two different build systems is a burden I would like to get rid of. Now seems to be a good time for that: we've cut off 3.6 release branch, and Hans assures me that 3.7 release process will use CMake. Are there existing users of configure/make that want sanitizers to be available in their build? Are there other arguments for keeping the autotools build "working" I'm missing? -- Alexey Samsonov vonosmas at gmail.com

cfe-dev mailing list cfe-dev at cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150213/f1e8401c/attachment.html>

More information about the llvm-dev mailing list