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

Paul Joseph Davis commented on COUCHDB-562:
-------------------------------------------

I don't think we should ever drop the --with vars because then making use of 
non-standard installs of spidermonkey goes back to crazy town. I think the 
situation we have now of using pkg-config if its available, overriding it all 
with --with* and using a promiscuous search as a last resort is the best 
solution.

How is it not a build dependency? Everyone building couchdb has to ./configure 
it, which is what depends on pkg-config unless I'm mistaken?

Although, we should update the instructions around --with to indicate that 
commonly on linux distributions (and whoever else) will generally as of 
recently automagically find the js libraries even though they're in weirdo 
places. But we should word it better than that.

> link couchjs with bound libmozjs
> --------------------------------
>
>                 Key: COUCHDB-562
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-562
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: 0.11
>         Environment: linux, ubuntu,debian
>            Reporter: Meno Abels
>             Fix For: 1.2
>
>         Attachments: couchdb-562.patch, couchdb-562_2.patch, 
> couchdb-562_3.patch, couchdb-mozjs-rpath.patch
>
>
> If you build the couchdb from the source with a prefix set and 
> --with-js-[lib|include] option the resulting couchjs programm in 
> <prefix>/lib/couchdb/bin/couchjs does not know where to find the specified 
> libmozjs.so which was specified in with-js-lib. This causes that quite all 
> test will fail. 
> To fix this the rpath has to setup during the compile. I don't had a look 
> where to do this.
> but a small shell wrapper fix it also
> #!/bin/sh
> LD_LIBRARY_PATH=...  exec $0.orig $@

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

Reply via email to