All of lore.kernel.org
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster Makefile
Date: 5 Oct 2006 16:28:08 -0000	[thread overview]
Message-ID: <20061005162808.27495.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at sourceware.org	2006-10-05 16:28:08

Modified files:
	.              : Makefile 

Log message:
	gfs-kernel (gfs1) and gnbd-kernel are going to track the RHEL5 kernel
	in cvs head.  We want the default top-level build of cvs head to work
	on upstream kernels, though, e.g. 2.6.19, for people who are trying out
	upstream gfs2/dlm.
	
	So, comment gfs-kernel and gnbd-kernel out of the top level makefile.
	Once we create a RHEL5 branch, we can uncomment them there (and
	perhaps remove gfs-kernel and gnbd-kernel from cvs head.)

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/Makefile.diff?cvsroot=cluster&r1=1.23&r2=1.24

--- cluster/Makefile	2006/08/11 15:18:03	1.23
+++ cluster/Makefile	2006/10/05 16:28:07	1.24
@@ -16,14 +16,14 @@
 
 
 all:
-	${MAKE} -C gnbd-kernel all
+#	${MAKE} -C gnbd-kernel all
 	${MAKE} -C cman/lib all
 	${MAKE} -C ccs all
 	${MAKE} -C cman all
 	${MAKE} -C group all
 	${MAKE} -C dlm all
 	${MAKE} -C fence all
-	${MAKE} -C gfs-kernel all
+#	${MAKE} -C gfs-kernel all
 	${MAKE} -C gfs all
 	${MAKE} -C gfs2 all
 	${MAKE} -C gnbd all
@@ -33,8 +33,8 @@
 clean:
 	rm -f *tar.gz
 	rm -rf build
-	${MAKE} -C gfs-kernel clean
-	${MAKE} -C gnbd-kernel clean
+#	${MAKE} -C gfs-kernel clean
+#	${MAKE} -C gnbd-kernel clean
 	${MAKE} -C ccs clean
 	${MAKE} -C cman clean
 	${MAKE} -C group clean
@@ -47,8 +47,8 @@
 #	${MAKE} -C cmirror clean
 
 distclean:
-	${MAKE} -C gfs-kernel distclean
-	${MAKE} -C gnbd-kernel distclean
+#	${MAKE} -C gfs-kernel distclean
+#	${MAKE} -C gnbd-kernel distclean
 	${MAKE} -C ccs distclean
 	${MAKE} -C cman distclean
 	${MAKE} -C group distclean
@@ -61,8 +61,8 @@
 #	${MAKE} -C cmirror distclean
 
 install: all
-	${MAKE} -C gfs-kernel install
-	${MAKE} -C gnbd-kernel install
+#	${MAKE} -C gfs-kernel install
+#	${MAKE} -C gnbd-kernel install
 	${MAKE} -C ccs install
 	${MAKE} -C cman install
 	${MAKE} -C group install
@@ -75,8 +75,8 @@
 #	${MAKE} -C cmirror install
 
 uninstall:
-	${MAKE} -C gfs-kernel uninstall
-	${MAKE} -C gnbd-kernel uninstall
+#	${MAKE} -C gfs-kernel uninstall
+#	${MAKE} -C gnbd-kernel uninstall
 	${MAKE} -C ccs uninstall
 	${MAKE} -C cman uninstall
 	${MAKE} -C group uninstall
@@ -89,8 +89,8 @@
 #	${MAKE} -C cmirror uninstall
 
 latest_tags:
-	${LATEST_TAG} gfs-kernel
-	${LATEST_TAG} gnbd-kernel
+#	${LATEST_TAG} gfs-kernel
+#	${LATEST_TAG} gnbd-kernel
 	${LATEST_TAG} ccs
 	${LATEST_TAG} cman
 	${LATEST_TAG} dlm
@@ -111,8 +111,8 @@
 	$(BUILD_SRPMS)
 
 tarballs: TAG
-	make -s COMPONENT=gfs-kernel RELEASE_FILE=gfs-kernel/make/release.mk.input tarball
-	make -s COMPONENT=gnbd-kernel RELEASE_FILE=gnbd-kernel/make/release.mk.input tarball
+#	make -s COMPONENT=gfs-kernel RELEASE_FILE=gfs-kernel/make/release.mk.input tarball
+#	make -s COMPONENT=gnbd-kernel RELEASE_FILE=gnbd-kernel/make/release.mk.input tarball
 	make -s COMPONENT=ccs RELEASE_FILE=ccs/make/release.mk.input tarball
 	make -s COMPONENT=cman RELEASE_FILE=cman/make/release.mk.input tarball
 	make -s COMPONENT=dlm RELEASE_FILE=dlm/make/release.mk.input tarball



             reply	other threads:[~2006-10-05 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 16:28 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-01  3:29 [Cluster-devel] cluster Makefile fabbione
2007-09-19 19:47 fabbione
2007-08-10  5:05 fabbione
2007-06-06  8:56 fabbione
2007-05-18 16:40 teigland
2006-07-19 14:45 teigland

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=20061005162808.27495.qmail@sourceware.org \
    --to=teigland@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 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.