[
https://issues.apache.org/jira/browse/COUCHDB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220411#comment-13220411
]
Benoit Chesneau commented on COUCHDB-1426:
------------------------------------------
I don't see the interrest to specify a lib and include paths if they are not
handled in priority. This isn't common at all.
"On the other hand, there's also this large rearrangement to fix the detection
of SM170 which didn't have the anonymous function option. It sure does seem
like there's quite a bit of change for this." Can you elaborate ?
The patch can't be really splitted since all this change is needed. I didn't
want at first introduce this detection, but the way the tests are done
currently mozjs185 will be always took in priotirty if it exists on the disk
even if another path to find js libs has been used. It's probably the same for
1.8.0 though it should be fixed too.
The other way may be having something like --with-js-version= and we test
against that. Though it's still unusual to not use paths defined by the user to
find the correct lib. I guess it will give some headache to maintainers on OS
when they will have to deal with xulrunner, js 1.8 ... and maybe old lib still
installed for old programs. I think the correct way is to discover the versions
in this order :
path given : we should find the version in this path. I think in this case we
should test 1.7.0 -> 1.8.5
if lib or include is not given: 1.8.5 -> 1.8.0 -> ... 1.7.0
> error while building with 2 spidermonkey installed
> --------------------------------------------------
>
> Key: COUCHDB-1426
> URL: https://issues.apache.org/jira/browse/COUCHDB-1426
> Project: CouchDB
> Issue Type: Bug
> Components: Build System
> Affects Versions: 1.1.1, 1.2
> Reporter: Benoit Chesneau
> Priority: Blocker
> Attachments:
> 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch,
> 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch,
> 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch,
> 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch
>
>
> Context:
> To bench the differences between different versions of couchdb I had to test
> against spidermonkey 1.7 and 1.8.5 . 1.8.5 is installed globally in
> /usr/local while the 1.7 version is installed on a temporary path.
> Problem:
> Using --witth-js-include & --with-js-lib configure options aren't enough to
> use the 1.7 version it still want to use spidermonkey 1.8.5 . Removing
> js-config from the path doesn't change anything. I had to uninstall
> spidermonkey 1.8.5 to have these setting working.
> Error result:
> $ ./configure
> --with-erlang=/Users/benoitc/local/otp-r14b04/lib/erlang/usr/include
> --with-js-include=/Users/benoitc/local/js-1.7.0/include
> --with-js-lib=/Users/benoitc/local/js-1.7.0/lib64
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... build-aux/install-sh -c -d
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> 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 ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking build system type... i386-apple-darwin11.3.0
> checking host system type... i386-apple-darwin11.3.0
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for fgrep... /usr/bin/grep -F
> checking for ld used by gcc...
> /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
> checking if the linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm
> checking the name lister (/usr/bin/nm) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 196608
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
> option to reload object files... -r
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm output from gcc object... ok
> checking for dsymutil... dsymutil
> checking for nmedit... nmedit
> checking for lipo... lipo
> checking for otool... otool
> checking for otool64... no
> checking for -single_module linker flag... yes
> checking for -exported_symbols_list linker flag... yes
> 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 for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fno-common -DPIC
> checking if gcc PIC flag -fno-common -DPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... darwin11.3.0 dyld
> 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
> checking whether ln -s works... yes
> checking for pthread_create in -lpthread... yes
> checking for JS_NewContext in -lmozjs185... yes
> checking jsapi.h usability... yes
> checking jsapi.h presence... yes
> checking for jsapi.h... yes
> checking whether JSOPTION_ANONFUNFIX is declared... no
> configure: error: Your SpiderMonkey library is too new.
> Versions of SpiderMonkey after the js185-1.0.0 release remove the optional
> enforcement of preventing anonymous functions in a statement context. This
> will most likely break your existing JavaScript code as well as render all
> example code invalid.
> If you wish to ignore this error pass --enable-js-trunk to ./configure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
