[ https://issues.apache.org/jira/browse/COUCHDB-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593066#action_12593066 ] 

Robert Rees commented on COUCHDB-47:
------------------------------------

Yeah I'll try and explain a bit better and provide a hacky fix that might explain better than just words! I have built Spidermonkey using the default instructions and the during the build the jsautocfg.h is created in the target (DARWIN_DBG.OBJ). I imagine that during the install process for Spidermonkey the headers from both source and target platform are placed in the same include directory, however by default the headers in both js/src/ and js/src/TARGET_PLATFORM need to be included.

So for example I have managed to fix the issue by changing the --with-js-lib case to the following:

# Check whether --with-js-lib was given.
if test "${with_js_lib+set}" = set; then
  withval=$with_js_lib; JS_LIB_FLAGS="-L$withval"
  JS_INCLUDE_FLAGS="$JS_INCLUDE_FLAGS -I$withval"
fi

Looking at it again I think the issue is that -with-js-include is probably meant to point at an installed Spidermonkey whereas I am building ICU, Spidermonkey and CouchDB side by side without ever installing any of them to /usr/local (or similar).

If this is the case then the bug could probably be resolved by documentation and I could just symbolically link jsautocfg.h to js/src to make this compilation step pass.

> --with-js-lib configure flag does not work
> ------------------------------------------
>
>                 Key: COUCHDB-47
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-47
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System
>         Environment: OSX Leopard, Spidermonkey 1.7, Erlang 5.6, CouchDB r650729
>            Reporter: Robert Rees
>
> When trying to build against my source distribution of Spidermonkey the build script acknowledges the existence of libjs but gives an error message that the header files (jsapi.h) is not present. This seems to be due to an error in the test file the build script constructs to test the include of the header file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.