From 8bb436dad16d1157121c29b35fa95f40b0c08250 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Wed, 28 Jul 2010 23:55:10 +0200 Subject: cc/gcc: add option to enable/disable libmudflap For some scenarii, libmudflap is not very usefull or can break the build. Make in an optioon that defaults to 'N' to be on the safe side. For the core gcc-s, there is absolutely no need to build libmidflap. Idea from: Bernhard Pfund --- config/cc/gcc.in.2 | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'config') diff --git a/config/cc/gcc.in.2 b/config/cc/gcc.in.2 index 33cbbc54..d6827697 100644 --- a/config/cc/gcc.in.2 +++ b/config/cc/gcc.in.2 @@ -51,3 +51,17 @@ config CC_GCC_SJLJ_EXCEPTIONS It can happen that ./configure is wrong in some cases. Known case is for ARM big endian, where you should say 'N'. + +config CC_GCC_LIBMUDFLAP + bool + prompt "Compile libmudflap" + default n + help + libmudflap is a pointer-use checking tool, which can detect + various mis-usages of pointers in C and (to some extents) C++. + + You should say 'N' here, as libmduflap generates instrumented + code (thus it is a bit bigger and a bit slower) and requires + re-compilation and re-link, while it exists better run-time + alternatives (eg. DUMA, dmalloc...) that need neither re- + compilation nor re-link. -- cgit v1.2.3