On Jan 5, 2012, at 11:35 PM, cr...@mailhaven.com wrote:
> hi,
>
> i'm taking a 1st shot at building CalendarServer on my linux/64 box.
>
> i've co'd from trunk,
>
> cd /usr/local/src/CalendarServer/CalendarServer
> svn info | egrep "UUID|Revision"
> Repository UUID: e27351fd-9f3e-4f54-a53b-843176b1656c
> Revision: 8488
>
> then, per README,
>
> ./run -s
> ...
> Checking MD5 sum for libevent...
> Unpacking libevent from cache...
> libevent-1.4.13-stable/
> ...
> Building libevent...
> ...
> Libraries have been installed in:
>
> /usr/local/src/CalendarServer/libevent-1.4.13-stable/_root/lib64
> ...
> Building memcached...
> ...
> checking for libevent directory... configure: error:
> libevent is required. You can get it from
> http://www.monkey.org/~provos/libevent/
>
> If it's already installed, specify its path using
> --with-libevent=/dir/
>
> iiuc, "./run" is supposed to gather prereqs.
>
> do i need to install libevent prior to 1st exec of "./run" to satisfy
> the bundled-memcached build? or pass some additional flags to ./run
> itself?
The idea is that ./run -s sets everything up.
What kind of Linux is this? I have been able to personally get calendar server
working on the last 3 versions of Ubuntu or so, as well as Red Hat derivatives,
by just doing ./run.
My guess is that this is a problem with build.sh's c_dependency function; it
currently hard-codes ${dstroot}/lib, and it looks like your configuration is
producing ${dstroot}/lib64 instead. If you try patching that file, does your
build succeed?
Thanks, and good luck,
-glyph
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
