Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fabbione@sourceware.org <fabbione@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence fence_node/Makefile fence_tool/M ...
Date: 22 Dec 2007 13:45:31 -0000	[thread overview]
Message-ID: <20071222134531.6543.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	fabbione at sourceware.org	2007-12-22 13:45:30

Modified files:
	fence/fence_node: Makefile 
	fence/fence_tool: Makefile 

Log message:
	Fix fence build dependencies. For too long we did rely on fence/Makefile
	to build in the right order but fence_tool and fence_node were just broken.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/fence_node/Makefile.diff?cvsroot=cluster&r1=1.15&r2=1.16
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/fence_tool/Makefile.diff?cvsroot=cluster&r1=1.22&r2=1.23

--- cluster/fence/fence_node/Makefile	2007/12/22 13:36:52	1.15
+++ cluster/fence/fence_node/Makefile	2007/12/22 13:45:30	1.16
@@ -15,7 +15,7 @@
 
 SBINDIRT=$(TARGET)
 
-all: ${TARGET}
+all: depends ${TARGET}
 
 include ../../make/defines.mk
 include $(OBJDIR)/make/cobj.mk
@@ -34,8 +34,10 @@
 
 LDFLAGS += -L${ccslibdir} -L${cmanlibdir} -lccs -lcman
 
-
 ${TARGET}: ${OBJS}
 	$(CC) -o $@ $^ $(LDFLAGS)
 
+depends:
+	$(MAKE) -C ../fenced agent.o
+
 clean: generalclean
--- cluster/fence/fence_tool/Makefile	2007/12/22 13:36:52	1.22
+++ cluster/fence/fence_tool/Makefile	2007/12/22 13:45:30	1.23
@@ -15,7 +15,7 @@
 
 SBINDIRT=$(TARGET)
 
-all: ${TARGET}
+all: depends ${TARGET}
 
 include ../../make/defines.mk
 include $(OBJDIR)/make/cobj.mk
@@ -34,8 +34,10 @@
 LDFLAGS += -L${ccslibdir} -L${cmanlibdir} -lccs -lcman
 LDFLAGS += -L../../group/lib -lgroup
 
-
 ${TARGET}: ${OBJS}
 	$(CC) -o $@ $^ $(LDFLAGS)
 
+depends:
+	$(MAKE) -C ../fenced agent.o
+
 clean: generalclean



                 reply	other threads:[~2007-12-22 13:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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