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

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?

 -- Keir

On 4/3/08 11:07, "Samuel Thibault" <samuel.thibault@eu.citrix.com> wrote:

> Add a check for the presence of ncurses development files
> 
> Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
> 
> diff -r b28ae5f00553 tools/check/check_curses_devel
> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
> +++ b/tools/check/check_curses_devel Tue Mar 04 11:06:06 2008 +0000
> @@ -0,0 +1,14 @@
> +#!/bin/sh
> +# CHECK-BUILD
> +
> +RC=0
> +
> +set -e
> +test -r /usr/include/curses.h || RC=1
> +
> +if test ${RC} -ne 0; then
> + echo
> + echo " *** Check for curses headers FAILED"
> +fi 
> +
> +exit ${RC}
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2008-03-04 11:24 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 [this message]
2008-03-04 11:42   ` Samuel Thibault

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=C3F2E1FE.1D6FE%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=samuel.thibault@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.