On Fri, Nov 22, 2013 at 7:00 PM, FX <fxcoud...@gmail.com> wrote: >> /users/charlet/fsf/trunk/libsanitizer/sanitizer_common/sanitizer_linux.cc: >> Assembler messages: >> /users/charlet/fsf/trunk/libsanitizer/sanitizer_common/sanitizer_linux.cc:821: >> Error: .cfi_endproc without corresponding .cfi_startproc >> :21485: Error: open CFI at the end of file; missing .cfi_endproc directive >> make[4]: *** [sanitizer_linux.lo] Error 1 > > I’ve posted this to the list before, and turns out you need “recent” linux > kernel and “recent” binutils to bootstrap GCC these days. But to keep the > fun, “recent” is neither document, nor tested at configure time, so you end > up with useless error messages. > > I’ve filed bug reports about it > (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59067 and > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59068), which have been dutifuly > ignored. My opinion is that unless the level of support of libsanitizer is > increased, it should not be built by default (or build it only if it’s > supported). Causing such bootstrap issues would not be tolerated in other > parts of the compiler.
I am all for disabling libsanitizer if something in the tool chain is old (binutils, kernel, compiler, etc). > > FX
