From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Xen Devel <xen-devel@lists.xensource.com>
Cc: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
Subject: [PATCH] Add a check script to check for the existence of an ocaml native compiler
Date: Tue, 13 Jul 2010 11:11:40 +0100 [thread overview]
Message-ID: <1279015900-20587-1-git-send-email-vincent.hanquez@eu.citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
The script doesn't check anything if the $OS is not linux, and just print a
warning if the compiler is missing.
Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
---
tools/check/check_ocaml | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
create mode 100755 tools/check/check_ocaml
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Add-a-check-script-to-check-for-the-existence-of-an-.patch --]
[-- Type: text/x-patch; name="0001-Add-a-check-script-to-check-for-the-existence-of-an-.patch", Size: 344 bytes --]
diff --git a/tools/check/check_ocaml b/tools/check/check_ocaml
new file mode 100755
index 0000000..a29a345
--- /dev/null
+++ b/tools/check/check_ocaml
@@ -0,0 +1,13 @@
+#!/bin/sh
+# CHECK-BUILD
+
+. ./funcs.sh
+
+case $OS in
+Linux)
+ has ocamlopt >/dev/null || warning "missing ocaml native compiler"
+ ;;
+*)
+
+ ;;
+esac
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-07-13 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 10:11 Vincent Hanquez [this message]
2010-07-13 18:12 ` [PATCH] Add a check script to check for the existence of an ocaml native compiler Ian Jackson
2010-07-14 10:33 ` Vincent Hanquez
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=1279015900-20587-1-git-send-email-vincent.hanquez@eu.citrix.com \
--to=vincent.hanquez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).