All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools: Check presence of ncurses
Date: Tue, 4 Mar 2008 11:42:52 +0000	[thread overview]
Message-ID: <20080304114252.GB5038@implementation.uk.xensource.com> (raw)
In-Reply-To: <C3F2E1FE.1D6FE%keir.fraser@eu.citrix.com>

Keir Fraser, le Tue 04 Mar 2008 11:24:46 +0000, a écrit :
> Will this break cross-compile environments? Xentop is not built in that case
> (hence no dependency on curses.h), yet your new check will still be
> enforced. If it is the xentop usage that you are wanting to protect with a
> check, perhaps the compile-or-not decision in xenstat/Makefile should be
> made dynamically based on presence of curses.h?

Something like this then:


tools: Compile xentop only if curses are available.

Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>

diff -r c89f6ed56351 tools/xenstat/Makefile
--- a/tools/xenstat/Makefile	Mon Mar 03 11:47:40 2008 +0000
+++ b/tools/xenstat/Makefile	Tue Mar 04 11:41:24 2008 +0000
@@ -6,7 +6,9 @@ SUBDIRS += libxenstat
 
 # This doesn't cross-compile (cross-compile environments rarely have curses)
 ifeq ($(XEN_COMPILE_ARCH),$(XEN_TARGET_ARCH))
+ifeq ($(wildcard /usr/include/curses.h),/usr/include/curses.h)
 SUBDIRS += xentop
+endif
 endif
 
 .PHONY: all install clean

      reply	other threads:[~2008-03-04 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 11:07 [PATCH] tools: Check presence of ncurses Samuel Thibault
2008-03-04 11:24 ` Keir Fraser
2008-03-04 11:42   ` Samuel Thibault [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=20080304114252.GB5038@implementation.uk.xensource.com \
    --to=samuel.thibault@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 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.