[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autconf, configure & purify...

From: Ralf Wildenhues
Subject: Re: autconf, configure & purify...
Date: Fri, 24 Oct 2008 08:39:32 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hello Antony,

* Boggis, Antony wrote on Fri, Oct 24, 2008 at 01:47:43AM CEST:
> After much googling and no answers (and least, none I can understand)
> I am resorting to querying the wisdom of this list (and excuse me if
> cc'ing is frowned upon).

Yeah, it's usually nicer to choose one list only; or set a followup to
one and mention that in the message.

> Now, I wish to introduce the usage of Purify into the equation.

Most syntax issues of your code have already been addressed.  Remains
the semantics: it substitutes PURIFY and USE_PURIFY (why this one BTW?),
adds to CPPFLAGS, and defines USE_PURIFY.

Remains the question: does anything in your files use

One hack I'd try would be to, after your snippet, and after AC_PROG_CC,
but before AC_PROG_LIBTOOL, set

so that purify is invoked along with the compiler.  FWIW, I haven't used
this beast in years, but that's how it used to work back then (with the
arrival of valgrind, we've never looked back though).

As a much cheaper alternative (that may or may not clash with libtool a
bit) than any code changes for purify, one can try to
  make clean
  env CC="purify gcc" make -e all

which usually worked, too.

> So, I have the following section in

> if test "$enable_purify" = "true"; then

FWIW the 'true' does not need quoting.

>   AC_CHECK_PROGS(PURIFY,purify purify2002)
>   if test -z $PURIFY; then

This however does need quoting: if $PURIFY can ever be empty, then the
shell will complain about a missing argument to 'test -z'.  So use
  if test -z "$PURIFY"; ...

>      AC_MSG_ERROR([purify requested, but unable to find purify])
>   fi

Hope that helps.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]