From: david m. richter <richterd@gmail.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster3 build: libdlm.h and PATH_MAX
Date: Wed, 1 Oct 2008 15:15:34 -0400 [thread overview]
Message-ID: <1d07ca700810011215p10d441bge4495cd10a74d754@mail.gmail.com> (raw)
hello,
I should've asked on IRC before you folks all left for your
conference, but these are two things I'd forgotten about until now
(because I'm setting up a new cluster from scratch).
[libdlm.h]
First, I'm building cluster3 and run into difficulties with finding
libdlm.h. In order to coax the build along, I had to modify:
- cluster/dlm/tool/Makefile
- cluster/dlm/libdlmcontrol/Makefile
- cluster/group/dlm_controld
.. by adding cluster/dlm/libdlm/ as an include directory.
I believe I'd had this trouble in the past with cluster2, as well, and
just punted and yum installed cman-devel -- but that's an ugly kludge.
My question is: has anyone else noticed anything w/r/t missing
libdlm.h, and if not have you verified that it's actually getting
picked up from the cluster source tree and not a pre-existing one in
/usr/include somewhere?
[PATH_MAX]
I'd had a similar problem before with
cluster/group/libgfscontrol/libgfscontrol.h, which uses PATH_MAX.
Builds on my systems blow up because it doesn't #include
<linux/limits.h>. I've had the one-liner patch in my tree for months
and forgot about it until I rebased and excised it, expecting it to be
vestigial.
Has anyone noticed anything similar? This one seems pretty clear-cut,
but something must be screwy somewhere or everyone would've noticed it
a long time ago.
thanks -- and enjoy Austria (or wherever you folks are having your conference),
d
.
next reply other threads:[~2008-10-01 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 19:15 david m. richter [this message]
2008-10-01 19:39 ` [Cluster-devel] Re: cluster3 build: libdlm.h and PATH_MAX david m. richter
2008-10-02 5:58 ` [Cluster-devel] " Fabio M. Di Nitto
2008-10-02 13:01 ` david m. richter
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=1d07ca700810011215p10d441bge4495cd10a74d754@mail.gmail.com \
--to=richterd@gmail.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).