You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by j d <do...@gmail.com> on 2010/03/07 18:51:08 UTC
./bootstrap and/or ./configure not working on Linux
from an svn checkout of rev 919949 I can run "./bootstrap" and then
"./configure --with-js-include=my/path --with-js-lib=my/lib/path".
However configure complains:
[
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 static flag -static works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether ln -s works... yes
checking for pthread_create in -lpthread... yes
checking for JS_NewContext in -lmozjs... no
checking for JS_NewContext in -ljs... yes
checking jsapi.h usability... no
checking jsapi.h presence... no
checking for jsapi.h... no
checking js/jsapi.h usability... no
checking js/jsapi.h presence... no
checking for js/jsapi.h... no
]
I am ~sure I've pointed the js paths to the right place. I haven't
been able to officially install spidermonkey, their build/install
directions aren't working (not sure what I've screwed up).
I've also tried couchdb rev 920001 from svn and HEAD from git but I
find the following:
Executing "./bootstrap" from the couchdb dir returns:
Usage: autoheader [-h] [--help] [-m dir] [--macrodir=dir]
[-l dir] [--localdir=dir] [--version] [template-file]
Executing "./configure" returns:
./configure: No such file or directory
Not sure what I'm doing wrong or what I need to do. Sorry for the
newbie question.
I really need the account/login/roles functionality or I have to
switch to another DB (but I'm really into couchdb).
Thanks!
Re: ./bootstrap and/or ./configure not working on Linux
Posted by Noah Slater <ns...@tumbolia.org>.
Please also run through:
http://wiki.apache.org/couchdb/Troubleshooting
On 7 Mar 2010, at 19:43, Paul Davis wrote:
> Are you looking for the command:
>
> $ JS_DIST=/usr/local/spidermonkey make -f Makefile.ref export
>
> There are docs on the wiki that should help:
>
> http://wiki.apache.org/couchdb/Installation
>
> You might also want to check out the "Avoiding DYLD_LIBRARY_PATH" in
> the OS X instructions.
>
> HTH,
> Paul Davis
>
> On Sun, Mar 7, 2010 at 2:34 PM, j d <do...@gmail.com> wrote:
>> Red Hat Enterprise Linux Server release 5.1 (Tikanga)
>>
>> Autoconf 2.13 (because Mozilla said only that's the only version that
>> works for them). It would be nice to know the proper Linux way of
>> keeping/referencing multiple versions of execs. This may be my issue
>> for the latest attempts at bootstraping couchdb, however i still need
>> to solve the js-lib issue.
>>
>> I am using absolute paths for the --with-js-* options but I didn't
>> have the LD_LIBRARY_PATH env var set. It is set now
>> (/tmp/js/src/Linux_All_OPT.OBJ) but I get the same results from the
>> "./configure ****" execute.
>>
>> In the interest of clarity:
>>
>> I have spidermonkey 1.8RC1 in the following folder: /tmp/js/src (i
>> know it shouldn't be in tmp, not sure what's the best place?)
>>
>> The contents of that directory are:
>>
>> [
>> build.mk jsdbgapi.h jslocko.asm jsscript.c
>> config jsdhash.c jslog2.c jsscript.h
>> config.mk jsdhash.h jslong.c jsshell.msg
>> CVS jsdtoa.c jslong.h jsstddef.h
>> editline jsdtoa.h jsmath.c jsstr.c
>> fdlibm jsdtracef.c jsmath.h jsstr.h
>> javascript-trace.d jsdtracef.h js.mdp jstypes.h
>> js jsemit.c js.msg jsutil.c
>> js3240.rc jsemit.h jsnum.c jsutil.h
>> jsapi.c jsexn.c jsnum.h jsxdrapi.c
>> jsapi.h jsexn.h jsobj.c jsxdrapi.h
>> jsarena.c jsfile.c jsobj.h jsxml.c
>> jsarena.h jsfile.h jsopcode.c jsxml.h
>> jsarray.c jsfile.msg jsopcode.h Linux_All_DBG.OBJ
>> jsarray.h jsfun.c jsopcode.tbl Linux_All_OPT.OBJ
>> jsatom.c jsfun.h jsOS240.def liveconnect
>> jsatom.h jsgc.c jsotypes.h lock_SunOS.s
>> jsbit.h jsgc.h jsparse.c Makefile.in
>> jsbool.c jshash.c jsparse.h Makefile.ref
>> jsbool.h jshash.h js.pkg perfect.js
>> js.c js_headers.txt jsprf.c plify_jsdhash.sed
>> jsclist.h jsify.pl jsprf.h prmjtime.c
>> jscntxt.c jsinterp.c jsproto.tbl prmjtime.h
>> jscntxt.h jsinterp.h jsprvtd.h README.html
>> jscompat.h jsinvoke.c jspubtd.h resource.h
>> jsconfig.h jsiter.c jsregexp.c rules.mk
>> jsconfig.mk jsiter.h jsregexp.h SpiderMonkey.rsp
>> jscpucfg.c jskeyword.tbl jsreops.tbl win32.order
>> jscpucfg.h jskwgen.c jsscan.c Y.js
>> jsdate.c jslibmath.h jsscan.h
>> jsdate.h jslock.c jsscope.c
>> jsdbgapi.c jslock.h jsscope.h
>> ]
>>
>> The contents of /Linux_All_OPT.OBJ are:
>> [
>> js jscntxt.o jsemit.o jskwgen jsobj.d jsscript.d
>> jsapi.d jscpucfg jsexn.d jskwgen.d jsobj.o jsscript.o
>> jsapi.o jscpucfg.d jsexn.o jskwgen.o jsopcode.d jsstr.d
>> jsarena.d jscpucfg.o jsfun.d jslock.d jsopcode.o jsstr.o
>> jsarena.o js.d jsfun.o jslock.o jsparse.d jsutil.d
>> jsarray.d jsdate.d jsgc.d jslog2.d jsparse.o jsutil.o
>> jsarray.o jsdate.o jsgc.o jslog2.o jsprf.d jsxdrapi.d
>> jsatom.d jsdbgapi.d jshash.d jslong.d jsprf.o jsxdrapi.o
>> jsatom.o jsdbgapi.o jshash.o jslong.o jsregexp.d jsxml.d
>> jsautocfg.h jsdhash.d jsinterp.o jsmath.d jsregexp.o jsxml.o
>> jsautokw.h jsdhash.o jsinvoke.d jsmath.o jsscan.d libjs.a
>> jsbool.d jsdtoa.d jsinvoke.o jsnum.d jsscan.o libjs.so
>> jsbool.o jsdtoa.o jsiter.d jsnum.o jsscope.d prmjtime.d
>> jscntxt.d jsemit.d jsiter.o js.o jsscope.o prmjtime.o
>> ]
>>
>> (note: the .so file is in there to)
>>
>> So to recap
>>
>> LD_LIBRARY_PATH is set to /tmp/js/src/Linux_All_OPT.OBJ
>>
>> ./configure --with-js-include=/tmp/js/src
>> --with-js-lib=/tmp/js/src/Linux_All_OPT.OBJ
>>
>> thanks again.
>>
Re: ./bootstrap and/or ./configure not working on Linux
Posted by j d <do...@gmail.com>.
Great, thank you both for the help.
Running:
JS_DIST=/usr/local/spidermonkey make -f Makefile.ref export
export LD_LIBRARY_PATH=/usr/local/spidermonkey/lib64
./configure --with-js-include=/usr/local/spidermonkey/include
--with-js-lib=/usr/local/spidermonkey/lib64
gets me past the spidermonkey errors.
Now on to my ICU issues. I'll take a few good cracks at fixing that
before I post again.
Re: ./bootstrap and/or ./configure not working on Linux
Posted by Paul Davis <pa...@gmail.com>.
Are you looking for the command:
$ JS_DIST=/usr/local/spidermonkey make -f Makefile.ref export
There are docs on the wiki that should help:
http://wiki.apache.org/couchdb/Installation
You might also want to check out the "Avoiding DYLD_LIBRARY_PATH" in
the OS X instructions.
HTH,
Paul Davis
On Sun, Mar 7, 2010 at 2:34 PM, j d <do...@gmail.com> wrote:
> Red Hat Enterprise Linux Server release 5.1 (Tikanga)
>
> Autoconf 2.13 (because Mozilla said only that's the only version that
> works for them). It would be nice to know the proper Linux way of
> keeping/referencing multiple versions of execs. This may be my issue
> for the latest attempts at bootstraping couchdb, however i still need
> to solve the js-lib issue.
>
> I am using absolute paths for the --with-js-* options but I didn't
> have the LD_LIBRARY_PATH env var set. It is set now
> (/tmp/js/src/Linux_All_OPT.OBJ) but I get the same results from the
> "./configure ****" execute.
>
> In the interest of clarity:
>
> I have spidermonkey 1.8RC1 in the following folder: /tmp/js/src (i
> know it shouldn't be in tmp, not sure what's the best place?)
>
> The contents of that directory are:
>
> [
> build.mk jsdbgapi.h jslocko.asm jsscript.c
> config jsdhash.c jslog2.c jsscript.h
> config.mk jsdhash.h jslong.c jsshell.msg
> CVS jsdtoa.c jslong.h jsstddef.h
> editline jsdtoa.h jsmath.c jsstr.c
> fdlibm jsdtracef.c jsmath.h jsstr.h
> javascript-trace.d jsdtracef.h js.mdp jstypes.h
> js jsemit.c js.msg jsutil.c
> js3240.rc jsemit.h jsnum.c jsutil.h
> jsapi.c jsexn.c jsnum.h jsxdrapi.c
> jsapi.h jsexn.h jsobj.c jsxdrapi.h
> jsarena.c jsfile.c jsobj.h jsxml.c
> jsarena.h jsfile.h jsopcode.c jsxml.h
> jsarray.c jsfile.msg jsopcode.h Linux_All_DBG.OBJ
> jsarray.h jsfun.c jsopcode.tbl Linux_All_OPT.OBJ
> jsatom.c jsfun.h jsOS240.def liveconnect
> jsatom.h jsgc.c jsotypes.h lock_SunOS.s
> jsbit.h jsgc.h jsparse.c Makefile.in
> jsbool.c jshash.c jsparse.h Makefile.ref
> jsbool.h jshash.h js.pkg perfect.js
> js.c js_headers.txt jsprf.c plify_jsdhash.sed
> jsclist.h jsify.pl jsprf.h prmjtime.c
> jscntxt.c jsinterp.c jsproto.tbl prmjtime.h
> jscntxt.h jsinterp.h jsprvtd.h README.html
> jscompat.h jsinvoke.c jspubtd.h resource.h
> jsconfig.h jsiter.c jsregexp.c rules.mk
> jsconfig.mk jsiter.h jsregexp.h SpiderMonkey.rsp
> jscpucfg.c jskeyword.tbl jsreops.tbl win32.order
> jscpucfg.h jskwgen.c jsscan.c Y.js
> jsdate.c jslibmath.h jsscan.h
> jsdate.h jslock.c jsscope.c
> jsdbgapi.c jslock.h jsscope.h
> ]
>
> The contents of /Linux_All_OPT.OBJ are:
> [
> js jscntxt.o jsemit.o jskwgen jsobj.d jsscript.d
> jsapi.d jscpucfg jsexn.d jskwgen.d jsobj.o jsscript.o
> jsapi.o jscpucfg.d jsexn.o jskwgen.o jsopcode.d jsstr.d
> jsarena.d jscpucfg.o jsfun.d jslock.d jsopcode.o jsstr.o
> jsarena.o js.d jsfun.o jslock.o jsparse.d jsutil.d
> jsarray.d jsdate.d jsgc.d jslog2.d jsparse.o jsutil.o
> jsarray.o jsdate.o jsgc.o jslog2.o jsprf.d jsxdrapi.d
> jsatom.d jsdbgapi.d jshash.d jslong.d jsprf.o jsxdrapi.o
> jsatom.o jsdbgapi.o jshash.o jslong.o jsregexp.d jsxml.d
> jsautocfg.h jsdhash.d jsinterp.o jsmath.d jsregexp.o jsxml.o
> jsautokw.h jsdhash.o jsinvoke.d jsmath.o jsscan.d libjs.a
> jsbool.d jsdtoa.d jsinvoke.o jsnum.d jsscan.o libjs.so
> jsbool.o jsdtoa.o jsiter.d jsnum.o jsscope.d prmjtime.d
> jscntxt.d jsemit.d jsiter.o js.o jsscope.o prmjtime.o
> ]
>
> (note: the .so file is in there to)
>
> So to recap
>
> LD_LIBRARY_PATH is set to /tmp/js/src/Linux_All_OPT.OBJ
>
> ./configure --with-js-include=/tmp/js/src
> --with-js-lib=/tmp/js/src/Linux_All_OPT.OBJ
>
> thanks again.
>
Re: ./bootstrap and/or ./configure not working on Linux
Posted by j d <do...@gmail.com>.
Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Autoconf 2.13 (because Mozilla said only that's the only version that
works for them). It would be nice to know the proper Linux way of
keeping/referencing multiple versions of execs. This may be my issue
for the latest attempts at bootstraping couchdb, however i still need
to solve the js-lib issue.
I am using absolute paths for the --with-js-* options but I didn't
have the LD_LIBRARY_PATH env var set. It is set now
(/tmp/js/src/Linux_All_OPT.OBJ) but I get the same results from the
"./configure ****" execute.
In the interest of clarity:
I have spidermonkey 1.8RC1 in the following folder: /tmp/js/src (i
know it shouldn't be in tmp, not sure what's the best place?)
The contents of that directory are:
[
build.mk jsdbgapi.h jslocko.asm jsscript.c
config jsdhash.c jslog2.c jsscript.h
config.mk jsdhash.h jslong.c jsshell.msg
CVS jsdtoa.c jslong.h jsstddef.h
editline jsdtoa.h jsmath.c jsstr.c
fdlibm jsdtracef.c jsmath.h jsstr.h
javascript-trace.d jsdtracef.h js.mdp jstypes.h
js jsemit.c js.msg jsutil.c
js3240.rc jsemit.h jsnum.c jsutil.h
jsapi.c jsexn.c jsnum.h jsxdrapi.c
jsapi.h jsexn.h jsobj.c jsxdrapi.h
jsarena.c jsfile.c jsobj.h jsxml.c
jsarena.h jsfile.h jsopcode.c jsxml.h
jsarray.c jsfile.msg jsopcode.h Linux_All_DBG.OBJ
jsarray.h jsfun.c jsopcode.tbl Linux_All_OPT.OBJ
jsatom.c jsfun.h jsOS240.def liveconnect
jsatom.h jsgc.c jsotypes.h lock_SunOS.s
jsbit.h jsgc.h jsparse.c Makefile.in
jsbool.c jshash.c jsparse.h Makefile.ref
jsbool.h jshash.h js.pkg perfect.js
js.c js_headers.txt jsprf.c plify_jsdhash.sed
jsclist.h jsify.pl jsprf.h prmjtime.c
jscntxt.c jsinterp.c jsproto.tbl prmjtime.h
jscntxt.h jsinterp.h jsprvtd.h README.html
jscompat.h jsinvoke.c jspubtd.h resource.h
jsconfig.h jsiter.c jsregexp.c rules.mk
jsconfig.mk jsiter.h jsregexp.h SpiderMonkey.rsp
jscpucfg.c jskeyword.tbl jsreops.tbl win32.order
jscpucfg.h jskwgen.c jsscan.c Y.js
jsdate.c jslibmath.h jsscan.h
jsdate.h jslock.c jsscope.c
jsdbgapi.c jslock.h jsscope.h
]
The contents of /Linux_All_OPT.OBJ are:
[
js jscntxt.o jsemit.o jskwgen jsobj.d jsscript.d
jsapi.d jscpucfg jsexn.d jskwgen.d jsobj.o jsscript.o
jsapi.o jscpucfg.d jsexn.o jskwgen.o jsopcode.d jsstr.d
jsarena.d jscpucfg.o jsfun.d jslock.d jsopcode.o jsstr.o
jsarena.o js.d jsfun.o jslock.o jsparse.d jsutil.d
jsarray.d jsdate.d jsgc.d jslog2.d jsparse.o jsutil.o
jsarray.o jsdate.o jsgc.o jslog2.o jsprf.d jsxdrapi.d
jsatom.d jsdbgapi.d jshash.d jslong.d jsprf.o jsxdrapi.o
jsatom.o jsdbgapi.o jshash.o jslong.o jsregexp.d jsxml.d
jsautocfg.h jsdhash.d jsinterp.o jsmath.d jsregexp.o jsxml.o
jsautokw.h jsdhash.o jsinvoke.d jsmath.o jsscan.d libjs.a
jsbool.d jsdtoa.d jsinvoke.o jsnum.d jsscan.o libjs.so
jsbool.o jsdtoa.o jsiter.d jsnum.o jsscope.d prmjtime.d
jscntxt.d jsemit.d jsiter.o js.o jsscope.o prmjtime.o
]
(note: the .so file is in there to)
So to recap
LD_LIBRARY_PATH is set to /tmp/js/src/Linux_All_OPT.OBJ
./configure --with-js-include=/tmp/js/src
--with-js-lib=/tmp/js/src/Linux_All_OPT.OBJ
thanks again.
Re: ./bootstrap and/or ./configure not working on Linux
Posted by Noah Slater <ns...@tumbolia.org>.
On 7 Mar 2010, at 17:51, j d wrote:
> checking for pthread_create in -lpthread... yes
> checking for JS_NewContext in -lmozjs... no
> checking for JS_NewContext in -ljs... yes
> checking jsapi.h usability... no
> checking jsapi.h presence... no
> checking for jsapi.h... no
> checking js/jsapi.h usability... no
> checking js/jsapi.h presence... no
> checking for js/jsapi.h... no
Looks like it's working fine to me! Hehe.
Like Paul said, check your library paths to see if it fixes things.
> Executing "./bootstrap" from the couchdb dir returns:
>
> Usage: autoheader [-h] [--help] [-m dir] [--macrodir=dir]
> [-l dir] [--localdir=dir] [--version] [template-file]
What distro are you using. What autoheader do you have installed, and what version?
Re: ./bootstrap and/or ./configure not working on Linux
Posted by Paul Davis <pa...@gmail.com>.
On Sun, Mar 7, 2010 at 12:51 PM, j d <do...@gmail.com> wrote:
> from an svn checkout of rev 919949 I can run "./bootstrap" and then
> "./configure --with-js-include=my/path --with-js-lib=my/lib/path".
> However configure complains:
>
> [
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 accepts -g... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld -m elf_x86_64
> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for g77 option to produce PIC... -fPIC
> checking if g77 PIC flag -fPIC works... yes
> checking if g77 static flag -static works... yes
> checking if g77 supports -c -o file.o... yes
> checking whether the g77 linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether ln -s works... yes
> checking for pthread_create in -lpthread... yes
> checking for JS_NewContext in -lmozjs... no
> checking for JS_NewContext in -ljs... yes
> checking jsapi.h usability... no
> checking jsapi.h presence... no
> checking for jsapi.h... no
> checking js/jsapi.h usability... no
> checking js/jsapi.h presence... no
> checking for js/jsapi.h... no
> ]
>
> I am ~sure I've pointed the js paths to the right place. I haven't
> been able to officially install spidermonkey, their build/install
> directions aren't working (not sure what I've screwed up).
>
> I've also tried couchdb rev 920001 from svn and HEAD from git but I
> find the following:
>
> Executing "./bootstrap" from the couchdb dir returns:
>
> Usage: autoheader [-h] [--help] [-m dir] [--macrodir=dir]
> [-l dir] [--localdir=dir] [--version] [template-file]
>
> Executing "./configure" returns:
>
> ./configure: No such file or directory
>
> Not sure what I'm doing wrong or what I need to do. Sorry for the
> newbie question.
>
> I really need the account/login/roles functionality or I have to
> switch to another DB (but I'm really into couchdb).
>
> Thanks!
>
Try specifying absolute paths for ./configure. Also remember that
LD_LIBRARY_PATH is going to need to be set when you run CouchDB if
your library isn't in a standard search location.
HTH,
Paul Davis