Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.212.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAM-agWgw9AYeet2wSw8uDiPrf+Nwrqyv_9a__SDTkeuZKK2DXQ@mail.gmail.com>
References: 
 <CAM-agWiS1K-NVMLGfCGEXmP8jWVTWfObobH=NRPM89xH73nnaw@mail.gmail.com>
 <A4E2DE04-5842-4D77-9CD4-BF2CD5DE173F@apache.org>
 <4EA57854.8080805@gmail.com>
 <1B88D95B-94A9-469F-8B32-6A958C39E315@apache.org>
 <4EA57C59.6020707@gmail.com>
 <AA198385-B1C0-402F-93C6-C9CF1497B6E4@apache.org>
 <CAM-agWj3OePzr8hXO3-eX7Di64FCdcYax_KhTDmM7nZ+U0cARA@mail.gmail.com>
 <CAN-3CB+nshMnVcsUoqhpxc4sXT1Pj2BNCb3WxoaaBYVA3v4_Jg@mail.gmail.com>
 <4EA65D1A.1040307@gmail.com>
 <CAN-3CBKqo13xjphr6t=iK+3cPRN36EY8n=bwFa8pKD52ekTWjg@mail.gmail.com>
 <CAM-agWhfd+EcZQA6UVWRuNS1aLnV_j6W735S7sSOZuMQmguBAA@mail.gmail.com>
 <CAM-agWgw9AYeet2wSw8uDiPrf+Nwrqyv_9a__SDTkeuZKK2DXQ@mail.gmail.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Tue, 25 Oct 2011 14:17:39 -0500
Message-ID: 
 <CAJ_m3YBhqK++cbEyPnbaR3nJqscdU8fLUgM7tzqAybecPiFzJg@mail.gmail.com>
Subject: Re: undefined reference to JS_SealObject
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Jim,

You should be able to build BigCouch master with the tarball at [1].
You should be able to just ignore the steps in the BigCouch README
about SpiderMonkey and just replace them with a standard "./configure
&& make && make install" pattern for the tarball (though I haven't yet
tested this on CentOS).

Alternatively, I've been hacking on the deb packages at [2] if you
have an Ubuntu/Debian machine somewhere. I've only tested these
packages on Ubuntu 10.04 and Debian 5.0 which we use internally for
hosting. We plan on making rpm's at some point, but I don't have an
ETA for them yet.

Let me know if you have any issues.

[1] http://ftp.mozilla.org/pub/mozilla.org/js/js185-1.0.0.tar.gz
[2] http://builds.cloudant.com/libmozjs185-1.0.0/Ubuntu/10.04/amd64/

On Tue, Oct 25, 2011 at 1:40 PM, Jim R. Wilson <wilson.jim.r@gmail.com> wro=
te:
> So, back to Oneiric + BigCouch. =A0Should I use spidermonkey 1.9.2 or 185=
?
> =A0Should I build from source or install from a repo? =A0Thanks in advanc=
e,
>
> -- Jim
>
> On Tue, Oct 25, 2011 at 8:59 AM, Jim R. Wilson <wilson.jim.r@gmail.com>wr=
ote:
>
>> Hi Jason,
>>
>> Thanks for all your work on build-couchdb. =A0I had about given up on
>> building couch when I found it, and it made my life significantly simple=
r.
>>
>> -- Jim
>>
>>
>> On Tue, Oct 25, 2011 at 4:29 AM, Jason Smith <jhs@iriscouch.com> wrote:
>>
>>> On Tue, Oct 25, 2011 at 6:54 AM, CGS <cgsmcmlxxv@gmail.com> wrote:
>>> > Hi Jason,
>>> >
>>> > First of all, good job that you thought to share from your experience
>>> and
>>> > put everything into a package.
>>> >
>>> > Just out of curiosity, I would like to ask you few questions if I may=
.
>>> >
>>> > 1. I noticed you put all the dependencies in your project (or at leas=
t
>>> most
>>> > of them). Why didn't you use wget (or git or whatever) instead to bri=
ng
>>> them
>>> > locally from the projects web pages?
>>>
>>> CouchDB could run anywhere. We should be able to burn a checkout onto
>>> a CD-ROM and install offline.
>>>
>>> > 2. I also noticed you used log files for some processes while for oth=
ers
>>> > there are no such file (e.g., for icu you used config.log, but you
>>> didn't
>>> > add also the the compilation and installation to that log). Is there =
a
>>> > reason or just the time didn't allow you to add logs for that? I am
>>> sorry if
>>> > this question is not correct, I see that scripting language for the
>>> first
>>> > time (I use BASH/AWK/SED and maybe few more for scripting).
>>>
>>> Build CouchDB was debugged into existence. Every feature was made to
>>> solve some purpose at some time. I have not (intentionally) made
>>> anything consistent. I have not worried about architecture or best
>>> practices. Instead, I focus on continuous testing and confirming that
>>> it works on every operating system. Once CouchDB is built, you never
>>> run build-couchdb ever again.
>>>
>>> > 3. And one last thing related to the choice of scripting language. Is
>>> there
>>> > a reason you chose rake or it is just because you feel yourself "at
>>> home"
>>> > with it?
>>>
>>> Rake is an excellent domain-specific language for accomplishing stuff.
>>> It is nice for building software because you can mix file tasks (like
>>> Make) and also abstract tasks (like Ant). Rake is based on Ruby which
>>> is widely-available, probably second-best language (after Perl): it is
>>> bundled in the operating system by every Linux distribution and OS X;
>>> and it is very convenient to install on Solaris.
>>>
>>> > Don't get me wrong, my intention was never to criticize your work. I
>>> think
>>> > you did great especially that you shared it with all of us. I am just
>>> curios
>>> > because I've seen different ways to do the same job and I am trying t=
o
>>> learn
>>> > which one is the most suitable for such a job (maybe I will follow it=
 as
>>> > well because I am doing also some sys admin work).
>>>
>>> Totally. Sometimes I joke that build-couchdb is the worst thing I've
>>> ever made; however, to a large extent, it is necessarily complex and
>>> unaesthetic because the job it must perform is complex and
>>> unaesthetic.
>>>
>>> --
>>> Iris Couch
>>>
>>
>>
>