I think this is the relavent part of the config.log :
configure:5551: gcc -std=gnu99 -o conftest -g -O2 -pthread
-I/usr/local/include -I/usr/local/include -L/usr/local/lib conftest.c
-levent >&5
In file included from /usr/include/inttypes.h:688,
from /usr/include/stdint.h:18,
from /usr/local/include/event.h:170,
from conftest.c:20:
/usr/local/lib/gcc/ia64-hp-hpux11.23/3.4.3/include/wchar.h:134: error: parse
error before "va_list"
/usr/local/lib/gcc/ia64-hp-hpux11.23/3.4.3/include/wchar.h:135: error: parse
error before "va_list"
/usr/local/lib/gcc/ia64-hp-hpux11.23/3.4.3/include/wchar.h:136: error: parse
error before "va_list"
configure:5558: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "memcached"
| #define PACKAGE_TARNAME "memcached"
| #define PACKAGE_VERSION "1.4.5"
| #define PACKAGE_STRING "memcached 1.4.5"
| #define PACKAGE_BUGREPORT "[email protected]"
| #define PACKAGE "memcached"
| #define VERSION "1.4.5"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_UNISTD_H 1
| /* end confdefs.h. */
| #include <sys/time.h>
| #include <sys/types.h>
| #include <event.h>
| int
| main ()
| {
| event_init();
| ;
| return 0;
| }
configure:5591: 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/
On Tue, Oct 5, 2010 at 10:51 AM, Dustin <[email protected]> wrote:
>
> On Oct 5, 12:44 am, mca <[email protected]> wrote:
> > Hello I am having problem installing memcached on my hp-ux box.
> > I have installed libevent-1.4.11-stable with configure make make-
> > install
> > But running ./configure on memcached-1.4.5 fails stating that it can't
> > find libevent.
> > Exact error message is "checking for libevent directory... configure:
> > error: libevent is required."
> >
> > I have previously installed memcached on an Linux box but can't figure
> > out whats the problem on this one.
> > Any pointers appreciated
>
> Read config.log -- it'll tell you what it means by that.
--
Murat Can ALPAY
http://mcatr.blogspot.com
