All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:42:42 +0200	[thread overview]
Message-ID: <87y6rnvr1p.fsf@meyering.net> (raw)
In-Reply-To: <87my84w1n6.fsf@meyering.net> (Jim Meyering's message of "Fri, 19 Jun 2009 19:53:49 +0200")

Jim Meyering wrote:
> 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:

While my patch worked, it wasn't right ;-)
Fabio found the real cause: a typo: css_... instead of css_...

Here's the patch:

From b124cd70ce01d12eb0a11e89c7f8c740cf4dbf30 Mon Sep 17 00:00:00 2001
From: Fabio M. Di Nitto <fdinitto@redhat.com>
Date: Fri, 19 Jun 2009 19:52:44 +0200
Subject: [PATCH] avoid build failure: css.h: no such file

* fence/libfence/Makefile.am (libfence_la_CFLAGS): Fix typo:
s/css_CFLAGS/ccs_CFLAGS/
---
 fence/libfence/Makefile.am |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fence/libfence/Makefile.am b/fence/libfence/Makefile.am
index dff9098..ef99b57 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	= $(ccs_CFLAGS)

 libfence_la_LDFLAGS	= $(ccs_LIBS) \
 			  -version-info $(libversion)
--
1.6.3.2.416.g04d0



  reply	other threads:[~2009-06-19 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 17:53 [Cluster-devel] [PATCH] avoid build failure: css.h: no such file Jim Meyering
2009-06-19 21:42 ` Jim Meyering [this message]
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=87y6rnvr1p.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.