FreeBSD Port: cfengine-2.2.1

2007-07-04 Thread Atmasamarpan
Hi, I am not able to compile cfengine both under 6.0 and 6.2. Am I doing anything wrong? Thanks a lot, Atmasamarpan if cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/include/db4 -I/usr/include -D_THREAD_SAFE -g -O2 -Wreturn-type -Wmissing-prototypes -Wuninitialized -D_THREAD_SAFE -O -pipe

FreeBSD Port: cfengine-2.2.1

2007-12-13 Thread Dewayne Geraghty
Sergie, I really appreciate your efforts with cfengine. I've discovered its use in maintaining 8 different sites with fairly complex configuration requirements. Is there any chance that you could update the kit to 2.2.3, as there won't be another upgrade to cfengine until June 2008, and the cha

Re: FreeBSD Port: cfengine-2.2.1

2007-07-04 Thread Lowell Gilbert
Atmasamarpan <[EMAIL PROTECTED]> writes: > I am not able to compile cfengine both under 6.0 and 6.2. Am I doing > anything wrong? Probably. It builds fine for me with the latest ports under a fairly recent -STABLE. Can you give more information about you installation, ports tree, etc.?

Re: FreeBSD Port: cfengine-2.2.1

2007-07-05 Thread Atmasamarpan
Hi, Everything is fine after I removed db4-4.0.14_1,1. The port requires db44, but during configure it finds db4 and compilation fails. See bellow. Thanks, Atmasamarpan ===> Patching for cfengine-2.2.1 ===> Applying FreeBSD patches for cfengine-2.2.1 ===> cfengine-2.2.1 depends on shared

Re: FreeBSD Port: cfengine-2.2.1

2007-07-05 Thread Scot Hetzel
On 7/5/07, Atmasamarpan <[EMAIL PROTECTED]> wrote: Hi, Everything is fine after I removed db4-4.0.14_1,1. The port requires db44, but during configure it finds db4 and compilation fails. See bellow. I had a look at the ports Makefile, and found a couple of problems:. USE_BDB?= 44 It should

Re: FreeBSD Port: cfengine-2.2.1

2007-12-13 Thread LI Xin
Dewayne Geraghty wrote: > Sergie, > > I really appreciate your efforts with cfengine. I've discovered its use in > maintaining 8 different sites with fairly complex configuration > requirements. Is there any chance that you could update the kit to 2.2.3, > as there won't be another upgrade to c