From: fabbione@sourceware.org <fabbione@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster gfs2/mount/Makefile gfs/include/gfs_on ...
Date: 20 Aug 2007 14:36:18 -0000 [thread overview]
Message-ID: <20070820143618.8675.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: fabbione at sourceware.org 2007-08-20 14:36:16
Modified files:
gfs2/mount : Makefile
Removed files:
gfs/include : gfs_ondisk.h
gfs2/include : gfs_ondisk.h
Log message:
Remove redundant gfs_ondisk.h from gfs/include/ and gfs2/include/
both files are outdated compared to the one shipped in
gfs-kernel/src/gfs/gfs_ondisk.h and there should be no need of
duplicates around the tree.
gfs and gfs2 both use to include gfskincdir that is enough to guarantee
that gfs_ondisk.h will be available at build time.
gfs2/mount/Makefile requires this one liner. I spotted that we try to include
gfs2kincdir that we never set and therefor it was failing to build without
a local copy of gfs_ondisk.h
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/include/gfs_ondisk.h.diff?cvsroot=cluster&r1=1.1&r2=NONE
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/include/gfs_ondisk.h.diff?cvsroot=cluster&r1=1.1&r2=NONE
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/mount/Makefile.diff?cvsroot=cluster&r1=1.14&r2=1.15
--- cluster/gfs2/mount/Makefile 2007/06/01 09:45:34 1.14
+++ cluster/gfs2/mount/Makefile 2007/08/20 14:36:16 1.15
@@ -26,7 +26,7 @@
CFLAGS += -DHELPER_PROGRAM -D_FILE_OFFSET_BITS=64
CFLAGS += -DGFS2_RELEASE_NAME=\"${RELEASE}\" -D_GNU_SOURCE
CFLAGS += -O2
-CFLAGS += -I${gfs2kincdir} -I${gfskincdir}
+CFLAGS += -I${gfskincdir}
CFLAGS += -I../include
CFLAGS += -I${incdir}
reply other threads:[~2007-08-20 14:36 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=20070820143618.8675.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 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.