Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] systemd: add option for valgrind header checking
Date: Thu, 13 Nov 2014 16:06:11 +0800	[thread overview]
Message-ID: <54646673.3020702@windriver.com> (raw)
In-Reply-To: <CAJTo0LbDXrc=RK5zbE2z24K86Ti5eEcS1LRYCOHC7jfFeUOpFA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]

On 11/12/2014 11:55 PM, Burton, Ross wrote:
> On 12 November 2014 10:45, Chen Qi <Qi.Chen@windriver.com 
> <mailto:Qi.Chen@windriver.com>> wrote:
>
>     +-AC_CHECK_HEADERS_ONCE([valgrind/memcheck.h valgrind/valgrind.h])
>     ++AC_ARG_ENABLE(valgrindheader,
>     AS_HELP_STRING([--disable-valgrindheader], [disable valgrind
>     header checking]))
>     ++if test "x$enable_valgrindheader" != "xno"; then
>     ++        AC_CHECK_HEADERS_ONCE([valgrind/memcheck.h
>     valgrind/valgrind.h])
>     ++fi
>
>
> If the user passes --enable-valgrindheader and valgrind isn't present, 
> it doesn't fail.  Combined with the lack of a valgrind build 
> dependency in the PACKAGECONFIG statement this isn't a very useful 
> PACKAGECONFIG option as it only works when not specified, and if it's 
> specified is non-deterministic.
>

Hi Ross,

I've sent to V2 with modification in PACKAGECONFIG. With this 
modification, the build result would not be non-deterministic.

Best Regards,
Chen Qi

> It appears that this valgrind support is for running the test suite 
> under valgrind for leak detection, which is something we're unlikely 
> to do.  A quick fix would be to comment out the check.
>
> A proper fix would be to use AC_ARG_WITH(valgrind), default to "auto", 
> use the pkg-config macros and respect yes/no/auto as appropriate.  The 
> mantra here being to spend ten minutes fixing it properly upstream 
> instead of having to rewrite the patch often as upstream changes their 
> configure script.
>
> Ross


[-- Attachment #2: Type: text/html, Size: 3242 bytes --]

      reply	other threads:[~2014-11-13  8:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 10:45 [PATCH 0/1] systemd: add option for valgrind header checking Chen Qi
2014-11-12 10:45 ` [PATCH 1/1] " Chen Qi
2014-11-12 15:55   ` Burton, Ross
2014-11-13  8:06     ` ChenQi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54646673.3020702@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox