From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster: RHEL56 - fence-agents: Work around bad nss/nspr prototypes
Date: Thu, 22 Apr 2010 13:31:14 +0100 [thread overview]
Message-ID: <4BD04192.4070404@redhat.com> (raw)
In-Reply-To: <20100421155116.0877F1207FB@lists.fedorahosted.org>
On 21/04/10 16:51, Lon Hohberger wrote:
> Gitweb: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=d4ae5b0f197288fafe884046ba9d9cd1c9c556b0
> Commit: d4ae5b0f197288fafe884046ba9d9cd1c9c556b0
> Parent: c57d8c5a6b3ba804a0d3242fdbd9daeb9476b58d
> Author: Lon Hohberger<lhh@redhat.com>
> AuthorDate: Wed Apr 21 11:35:28 2010 -0400
> Committer: Lon Hohberger<lhh@redhat.com>
> CommitterDate: Wed Apr 21 11:35:28 2010 -0400
>
> fence-agents: Work around bad nss/nspr prototypes
>
> This patch allows fence_xvm[d] to compile with
> nss/nspr installations which have bad prototypes.
>
> Resolves: bz#575157
>
> Signed-off-by: Lon Hohberger<lhh@redhat.com>
> ---
> fence/agents/xvm/Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fence/agents/xvm/Makefile b/fence/agents/xvm/Makefile
> index 4118e34..a8c8b56 100644
> --- a/fence/agents/xvm/Makefile
> +++ b/fence/agents/xvm/Makefile
> @@ -28,7 +28,7 @@ INCLUDE=-I${top_srcdir}/include -I${top_srcdir}/config \
> -I../../../cman/lib -I../../../ccs/lib -I/usr/include/libxml2
>
> CFLAGS+=-DFENCE_RELEASE_NAME=\"${RELEASE}\" \
> - -Wall -Werror -Wstrict-prototypes -Wshadow -ggdb -D_GNU_SOURCE
> + -Wall -Wstrict-prototypes -Wshadow -ggdb -D_GNU_SOURCE
>
> LIBS+=-L../../../cman/lib -L../../../ccs/lib -L${libdir}/openais \
> -L../../../dlm/lib -lnss3 -lxml2
Lon, that's fine as far as it goes ... but now you also need to backport
that to the Zstreams too. OR we get the real problem fixed :S
Chrissie
parent reply other threads:[~2010-04-22 12:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100421155116.0877F1207FB@lists.fedorahosted.org>]
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=4BD04192.4070404@redhat.com \
--to=ccaulfie@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).