Do you use a libtool release contemporary with 2.2.7? On Tue, Jul 9, 2013 at 7:37 AM, Mangesh Sawant <m.v.sawant@xxxxxxxxx> wrote: > Hi, > > getting following error: > /bin/sh: /home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/shlibtool: No such > file or directory > > Config: > > ./configure --with-ldap --with-included-apr=./srclib/apr/ > --with-included-apr=./srclib/apr-util/ --enable-mods-shared="all aaa ssl > ldap cache proxy authn_alias mem_cache file_cache authnz_ldap charset_lite > dav_lock disk_cache" > > > > > > > > RC/branches/HTTPDSRC2.2.7/srclib/pcre -I. > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/os/unix > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/server/mpm/prefork > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/http > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/filters > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/proxy > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/include > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/generators > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/mappers > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/database > -I/usr/include/apr-1 -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/server > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/proxy/../generators > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/ssl > -I/home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/modules/dav/main -c > mod_authn_file.c && touch mod_authn_file.slo > > /bin/sh /home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/shlibtool --silent > --mode=link gcc -pthread -o mod_authn_file.la -rpath > /usr/local/apache2/modules -module -avoid-version mod_authn_file.lo > > /bin/sh: /home/CODE/RBS_OPEN_SRC/branches/HTTPDSRC2.2.7/shlibtool: No such > file or directory > > > Thanks And Regards , > Mangesh Sawant . -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|