From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Fix cman build issue on current head
Date: Mon, 26 Jun 2006 15:20:12 -0400 [thread overview]
Message-ID: <1151349612.20766.495.camel@ayanami.boston.redhat.com> (raw)
Fixes this build error:
gcc -Wall -fPIC -g -I//root/head/cman/../ccs/lib -I//usr/include
-I../config -DCMAN_RELEASE_NAME=\"DEVEL.1151348944\" -I../lib -DDEBUG -I
openais20060622/trunk/exec -L openais20060622/trunk/exec -c -o ais.o
ais.c
ais.c:40:18: error: swab.h: No such file or directory
In file included from ais.c:43:
daemon.h:23: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__?
before ?quit_threads?
ais.c: In function ?cman_deliver_fn?:
ais.c:356: warning: implicit declar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cman-build1.patch
Type: text/x-patch
Size: 675 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20060626/fea36e25/attachment.bin>
reply other threads:[~2006-06-26 19:20 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=1151349612.20766.495.camel@ayanami.boston.redhat.com \
--to=lhh@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).