couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] Commented: (COUCHDB-80) LD_LIBRARY_PATH shouldn't be needed
Date Sun, 02 Aug 2009 19:17:14 GMT


Paul Joseph Davis commented on COUCHDB-80:

As I explained in IRC, LD_LIBRARY_PATH is for people that don't feel like putting their libraries
into directories that are searched by ld by default. The proper way to do make the LD_LIBRARY_PATH
disappear is to tell people to use the system default paths, change their or deal

Most of the reports I've seen on this are in reference to spidermonkey on OS X. Checking the
build instructions at [1] shows that we're telling people to put the library in a unsearched
library path...

The proper directions are to either use a command like this:

JS_DIST=/usr/local/ make -f Makefile.ref export

to install the bits into a default searched directory (On OS X, I seem to recall that not
all distros search /usr/local/lib but I could be making that up...)

Or we can add a couple symlinks like such:

JS_DIST=/usr/local/spidermonkey make -f Makefile.ref export
sudo ln -s /usr/local/spidermonkey/lib/libjs.dylib /usr/local/lib
sudo ln -s /usr/local/spidermonkey/include /usr/local/include/js

in case people don't want to install directly into those directories for some odd reason.

I verified both approaches but I have a port version of spidermonkey installed so I would
like someone without the port version installed to double check that it wasn't sneaking in
there somehow. otool said it wasn't but who can be certain without checking.

Just to point out, there's still noting in CouchDB that needs LD_LIBRARY_PATH XD

> LD_LIBRARY_PATH shouldn't be needed
> -----------------------------------
>                 Key: COUCHDB-80
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Noah Slater
>            Assignee: Noah Slater
> This should be configured at build time, see:

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

View raw message