All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Martin <furryfuttock@gmail.com>
To: xen-devel@lists.xen.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: stubdom/libxc-x86_64 compile error with valgrind installed
Date: Mon, 21 Jul 2014 11:00:14 +0100	[thread overview]
Message-ID: <1216211935.20140721110014@gmail.com> (raw)

Hello all,

I  am building on Debian Wheezy and I have valgrind installed. About a
month ago I started having compilation problems. I assume it must have
something to do with Andrew's valgrind patch of June 10th.

The problem seems to lie in the fact that valgrind is in /usr/include,
however -nostdinc is specified on the compilation so we don't get it.

I  removed  -nostdinc from stubdom/Makefile and it compiled correctly.
Reading  the  gcc documentation this *should* be safe, as it will only
search   the   default   directories   *after*  the  explicit  include
directories. That being said, there is probably a better fix for this.

Regards.

-- 
Best regards,
 Simon                          mailto:furryfuttock@gmail.com

             reply	other threads:[~2014-07-21 10:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 10:00 Simon Martin [this message]
2014-07-21 10:06 ` stubdom/libxc-x86_64 compile error with valgrind installed Ian Campbell
2014-07-21 11:17   ` Simon Martin
2014-07-21 10:19 ` Andrew Cooper
2014-07-21 10:33   ` Ian Campbell
2014-07-21 10:40     ` Andrew Cooper
2014-07-21 10:47       ` Ian Campbell
2014-07-21 10:56         ` Andrew Cooper
2014-07-21 11:06           ` Ian Campbell
2014-07-21 11:10             ` Ian Campbell
2014-07-21 11:14           ` Ian Jackson

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=1216211935.20140721110014@gmail.com \
    --to=furryfuttock@gmail.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.