From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 000/003] ccs cleanup
Date: Tue, 01 May 2007 18:04:15 +0200 [thread overview]
Message-ID: <463764FF.1070904@ubuntu.com> (raw)
In-Reply-To: <463764B3.1030408@ubuntu.com>
001_ccs_clean_build_linking
both libccs and daemon were building and linking common/log.c.
Make libccs sucks in log.o and make ccsd link against libccs.
Also fix ccs top level makefile to build in proper order.
--
I'm going to make him an offer he can't refuse.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 001_ccs_clean_build_linking.dpatch
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070501/980103e0/attachment.ksh>
next prev parent reply other threads:[~2007-05-01 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 16:02 [Cluster-devel] [PATCH 000/003] ccs cleanup Fabio Massimo Di Nitto
2007-05-01 16:04 ` Fabio Massimo Di Nitto [this message]
2007-05-01 16:05 ` [Cluster-devel] [PATCH 002/003] ccs daemon cluster base on ipv6 Fabio Massimo Di Nitto
2007-05-01 16:07 ` [Cluster-devel] [PATCH 003/003] ccs daemon remove dead code Fabio Massimo Di Nitto
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=463764FF.1070904@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).