problems with building the CVS checkout of roadrunner

I'm having some trouble getting started with building the CVS version of 
roadrunner, the profiles, and the Python wrapper. I have found instructions 
for extracting the files from CVS, but no instructions on how to build from 
CVS.

To generate the ./configure file from the CVS tree I ran autoconf on the 
confgure.ac file. Next I ran ./configure and then finally I ran make and then 
"make install".  The following libraries were installed in /usr/local/lib by 
"make install"

-rwxr-xr-x    1 root     root       392189 Sep  4 11:28 librr.so.0.0.0
lrwxrwxrwx    1 root     root           14 Sep  4 11:28 librr.so.0 -> 
librr.so.0.0.0
lrwxrwxrwx    1 root     root           14 Sep  4 11:28 librr.so -> 
librr.so.0.0.0
-rwxr-xr-x    1 root     root          770 Sep  4 11:28 librr.la
-rw-r--r--    1 root     root      2084324 Sep  4 11:28 librr.a
-rwxr-xr-x    1 root     root        77185 Sep  4 11:29 libnullecho.so.0.0.0
lrwxrwxrwx    1 root     root           20 Sep  4 11:29 libnullecho.so.0 -> 
libnullecho.so.0.0.0
lrwxrwxrwx    1 root     root           20 Sep  4 11:29 libnullecho.so -> 
libnullecho.so.0.0.0
-rwxr-xr-x    1 root     root          836 Sep  4 11:29 libnullecho.la
-rw-r--r--    1 root     root        78028 Sep  4 11:29 libnullecho.a
drwxr-xr-x    2 root     root         4096 Sep  4 11:29 pkgconfig
-rwxr-xr-x    1 root     root        83805 Sep  4 11:29 librrrot13.so.0.0.0
lrwxrwxrwx    1 root     root           19 Sep  4 11:29 librrrot13.so.0 -> 
librrrot13.so.0.0.0
lrwxrwxrwx    1 root     root           19 Sep  4 11:29 librrrot13.so -> 
librrrot13.so.0.0.0
-rwxr-xr-x    1 root     root          829 Sep  4 11:29 librrrot13.la
-rw-r--r--    1 root     root       144102 Sep  4 11:29 librrrot13.a

The compile step failed when running make in the doc/resources directory. (I'm 
compiling on Rehat 7.3).  The following errors occured:

gcc -I../.. -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
-I/usr/include/libxml2 -DRR_DEBUG_NET_ENABLE -c roadrunner-scan.c  -fPIC 
-DPIC -o .libs/roadrunner-scan.lo
roadrunner-scan.c: In function `output_widget_args':
roadrunner-scan.c:673: structure has no member named `n_property_specs'
roadrunner-scan.c:675: structure has no member named `property_specs'
Compilation of scanner failed
make[3]: *** [scan-build.stamp] Error 1
make[3]: Leaving directory `/home/mclay/roadrunner/roadrunner/doc/reference'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/mclay/roadrunner/roadrunner/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mclay/roadrunner/roadrunner'
make: *** [all-recursive-am] Error 2

When trying to build the pyrr module it failed with autoconf problems.

[me@farad pyrr] autoconf configure.ac > configure
autoconf: Undefined macros:
configure.ac:14:AC_DISABLE_STATIC

I looked in the roadrunner and Python configure.in and configure files and did 
not find AC_DISABLE_STATIC defined. I tried it with the two versions of 
autoconfig that are supplied with the Readhat distribution. (version 2.13 and 
2.53) The 2.53 version claimed additional possibly undefined macros.

I tried running the generated configure file in spite of the errors from 
autoconf.  Here's the result:

[me@farad pyrr] ./configure
loading cache ./config.cache
./configure: line 528: syntax error near unexpected token 
`AM_INIT_AUTOMAKE(pyrr,'
./configure: line 528: `AM_INIT_AUTOMAKE(pyrr, $PYRR_VERSION)'
[me@farad pyrr]

No Makefile was generated.

When building the tls module the following errors occured:
[me@farad tls] ./configure
loading cache ./config.cache
./configure: line 532: syntax error near unexpected token 
`AM_INIT_AUTOMAKE(rrtls,'
./configure: line 532: `AM_INIT_AUTOMAKE(rrtls, $RRTLS_VERSION)'

BTW, do the profiles need to be placed in the roadrunner/profiles directory or 
can the be outside the roadrunner directory tree? I am currently trying to 
build them outside of the roadrunner tree.

Thanks for all the great work on RoadRunner. The OpenCal project looks like an 
exciting addition to the mix. Do you have plans for integrating the Mr. 
Project scheduling into an OpenCal database?