From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 001/008] configure makefile cleanup
Date: Wed, 28 Jun 2006 17:03:32 +0200 [thread overview]
Message-ID: <44A29A44.2000207@ubuntu.com> (raw)
In-Reply-To: <44A2996B.1010001@redhat.com>
Robert Peterson wrote:
> Fabio M. Di Nitto wrote:
>> gfs and gfs-kernel do not build anylonger from HEAD. gfs-kernel requires
>> dlm that's not built and gfs requires iddev that's not part of this branch
>> anymore.
>>
>> dlm needs to build before group. The latter requires to link with dlm.
>>
>> enter group in distclean and add a distclean target for group/Makefile.
>>
>> don't configure cmirror since we do not build it (Or perhaps fix the Makefile?).
>>
>> gfs2 is on the way to be merged upstream. gnbd should probably do the same and
>> already part of the ubuntu kernel tree. So stop building it from here.
>>
>> fix clean/make target in gfs-kernel since gulm is long way gone.
> Hi Fabio,
>
> NACK. Actually, I've been working to get gfs and gfs-kernel to build
> properly
> with the upstream kernel and new infrastructure changes.
> I've got a gfs-kernel that compiles now (but needs other things, regarding
> the locking infrastructure), and I'm working on getting the gfs tools to
> use
> udev's libvolume_id rather than iddev, as we did for the gfs2 userspace
> tools.
Ok perfect! I wasn't aware of general plan and directions (or I might have just
missed them) so i did prefer to raise the issue.
> So hopefully in the next few business days, I'll have these compiling
> properly
> and committed to CVS. Until then, I apologize for the compile problems.
It's not a problem. In Ubuntu we are dropping gfs for the next release to focus
on gfs2.
My main concern was for CVS users that builds from the top level dir.
> You're right that the gfs2-kernel stuff should not be compiled out of CVS,
> because that's all in a public git tree now, and that's where people
> should get it.
> I'm not sure about the plans for gnbd at the moment, so I'll defer to
> someone else.
Agreed 100%.
Thanks!
Fabio
--
I'm going to make him an offer he can't refuse.
prev parent reply other threads:[~2006-06-28 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 11:34 [Cluster-devel] [PATCH 001/008] configure makefile cleanup Fabio M. Di Nitto
2006-06-28 14:59 ` Robert Peterson
2006-06-28 15:03 ` Fabio Massimo Di Nitto [this message]
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=44A29A44.2000207@ubuntu.com \
--to=fabbione@ubuntu.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).