From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] avoid build failure: css.h: no such file
Date: Fri, 19 Jun 2009 19:53:49 +0200 [thread overview]
Message-ID: <87my84w1n6.fsf@meyering.net> (raw)
Building fence, as just described, I get this:
agent.c:15:17: fatal error: ccs.h: No such file or directory
compilation terminated.
make[2]: *** [libfence_la-agent.lo] Error 1
make[2]: Leaving directory `/h/meyering/w/co/fence/fence/libfence'
The fix is to arrange to compile with the corosync CFLAGS from pkg-config:
From 9f44500477465e04654e42363e627c9845dc2596 Mon Sep 17 00:00:00 2001
From: Jim Meyering <meyering@redhat.com>
Date: Fri, 19 Jun 2009 19:52:44 +0200
Subject: [PATCH] avoid build failure: css.h: no such file
* configure.ac: Use PKG_CHECK_MODULES([corosync],[corosync]).
* fence/libfence/Makefile.am (libfence_la_CFLAGS):
Append $(corosync_CFLAGS).
---
configure.ac | 1 +
fence/libfence/Makefile.am | 2 +-
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index e569176..b0a014b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -77,6 +77,7 @@ check_lib_no_libs() {
}
# corosync libs
+PKG_CHECK_MODULES([corosync],[corosync])
PKG_CHECK_MODULES([cfg],[libcfg])
PKG_CHECK_MODULES([cpg],[libcpg])
PKG_CHECK_MODULES([quorum],[libquorum])
diff --git a/fence/libfence/Makefile.am b/fence/libfence/Makefile.am
index dff9098..13b48cb 100644
--- a/fence/libfence/Makefile.am
+++ b/fence/libfence/Makefile.am
@@ -12,7 +12,7 @@ lib_LTLIBRARIES = libfence.la
libfence_la_SOURCES = agent.c
-libfence_la_CFLAGS = $(css_CFLAGS)
+libfence_la_CFLAGS = $(css_CFLAGS) $(corosync_CFLAGS)
libfence_la_LDFLAGS = $(ccs_LIBS) \
-version-info $(libversion)
--
1.6.3.2.416.g04d0
next reply other threads:[~2009-06-19 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 17:53 Jim Meyering [this message]
2009-06-19 21:42 ` [Cluster-devel] [PATCH] avoid build failure: css.h: no such file Jim Meyering
2009-06-20 12:33 ` Fabio M. Di Nitto
2009-06-21 8:02 ` Jim Meyering
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=87my84w1n6.fsf@meyering.net \
--to=jim@meyering.net \
/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.