From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster configure
Date: 6 Dec 2007 10:38:00 -0000 [thread overview]
Message-ID: <20071206103800.27689.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: pcaulfield at sourceware.org 2007-12-06 10:38:00
Modified files:
. : configure
Log message:
Add option to disable kernel_check.
From Soren Hansen:
"It's handy to be able to
disable the new kernel version check if we don't actually have the
kernel headers around, but know that the proper stuff is around when
it's needed."
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/configure.diff?cvsroot=cluster&r1=1.38&r2=1.39
--- cluster/configure 2007/11/24 04:57:31 1.38
+++ cluster/configure 2007/12/06 10:38:00 1.39
@@ -84,6 +84,7 @@
without_gfs2 => \$without_gfs2,
without_gnbd => \$without_gnbd,
without_rgmanager => \$without_rgmanager,
+ disable_kernel_check => \$disable_kernel_check,
);
my $err = &GetOptions (\%options,
@@ -139,7 +140,8 @@
'without_gfs',
'without_gfs2',
'without_gnbd',
- 'without_rgmanager');
+ 'without_rgmanager',
+ 'disable_kernel_check');
if(!$err) {
$ret = 1;
@@ -205,6 +207,7 @@
print "--without_gfs2\tDisable gfs2 building (Default: enabled)\n";
print "--without_gnbd\tDisable gnbd building (Default: enabled)\n";
print "--without_rgmanager\tDisable rgmanager building (Default: enabled)\n";
+ print "--disable_kernel_check\tDisable kernel version check (default: enabled)\n";
exit $ret;
}
@@ -312,7 +315,7 @@
$kernel_src=$kernel_build;
}
}
-if (!kernel_version($kernel_build,$required_kernelversion)) {
+if (not $disable_kernel_check and !kernel_version($kernel_build,$required_kernelversion)) {
exit 1;
}
if (!$module_dir) {
@@ -444,6 +447,9 @@
if (!$without_rgmanager) {
$without_rgmanager="";
}
+if (!$disable_kernel_check) {
+ $disable_kernel_check=0;
+}
if (defined($release_major) && not length $release_major) {
$release_major="";
}
next reply other threads:[~2007-12-06 10:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 10:38 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-28 6:43 [Cluster-devel] cluster configure fabbione
2008-01-07 18:58 lhh
2007-12-21 7:28 fabbione
2007-12-21 5:58 fabbione
2007-12-19 5:48 fabbione
2007-11-24 4:57 fabbione
2007-10-26 19:18 rmccabe
2007-10-01 3:28 fabbione
2007-09-28 6:19 fabbione
2007-09-24 14:43 fabbione
2007-09-14 14:32 teigland
2007-09-06 16:26 teigland
2007-09-06 16:24 teigland
2007-06-06 8:42 fabbione
2007-05-21 10:16 pcaulfield
2006-10-05 16:50 teigland
2006-08-02 22:47 rpeterso
2006-07-19 17:13 teigland
2006-07-19 14:51 teigland
2006-07-19 14:04 rpeterso
2006-06-28 19:54 jbrassow
2006-06-14 20:44 cfeist
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=20071206103800.27689.qmail@sourceware.org \
--to=pcaulfield@sourceware.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 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).