search for: ac_cv_header_valgrind_valgrind_h

...uild host and not the host. >>> >>> -eric >> Right. >> >> There are two issues. >> >> 1 ) THere should be a way to disable valgrind as you can for zlib. > FWIW, because of inline asm in valgrind.h that LLVM can't yet handle, I use: > > ac_cv_header_valgrind_valgrind_h=no .../configure ... when i do that i get: llvm[1]: Compiling regfree.c for Release+Asserts build llvm[1]: Compiling regstrlcpy.c for Release+Asserts build llvm[1]: Compiling system_error.cpp for Release+Asserts build llvm[1]: Building Release+Asserts Archive Library libLLVMSupport.a make[1]: ***...

...ight. >>>> >>>> There are two issues. >>>> >>>> 1 ) THere should be a way to disable valgrind as you can for zlib. >>> FWIW, because of inline asm in valgrind.h that LLVM can't yet handle, I >>> use: >>> >>> ac_cv_header_valgrind_valgrind_h=no .../configure ... >> when i do that i get: >> >> llvm[1]: Compiling regfree.c for Release+Asserts build >> llvm[1]: Compiling regstrlcpy.c for Release+Asserts build >> llvm[1]: Compiling system_error.cpp for Release+Asserts build >> llvm[1]: Building Release+A...

...two issues. >>>>>> >>>>>> 1 ) THere should be a way to disable valgrind as you can for zlib. >>>>> FWIW, because of inline asm in valgrind.h that LLVM can't yet handle, I >>>>> use: >>>>> >>>>> ac_cv_header_valgrind_valgrind_h=no .../configure ... >>>> when i do that i get: >>>> >>>> llvm[1]: Compiling regfree.c for Release+Asserts build >>>> llvm[1]: Compiling regstrlcpy.c for Release+Asserts build >>>> llvm[1]: Compiling system_error.cpp for Release+Asserts bu...

On 02/24/2014 04:42 PM, Eric Christopher wrote: > On Mon, Feb 24, 2014 at 4:40 PM, reed kotler <rkotler at mips.com> wrote: >> I need to leave soon and will take a look in the morning. >> >> I did look at the autoconf input files configure.ac >> >> There is a disable-zlib but not a disable-valgrind, even though it seems >> like there used to be.