Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of xkeitarox@gmail.com
 designates 74.125.83.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=GOsBB6ovhPs9EWkq4e02SJsOi8R/rPXzzz85Xb1YBZloK+tmS67nxi66RRwHmuGjC1
         wzxtp3Tz05Ui2aitz/tPrgFPrKLpphHQV5Qb6hZlepWwKVaAU48rmfwrNgpSs3ZnDYSG
         SOIF55+CfFRP/c05DCUCzQB20Lak5IKs2KUEA=
MIME-Version: 1.0
In-Reply-To: <t2k45ef89081004201136m3accd7eeme1885ca16d4b504d@mail.gmail.com>
References: <x2w58d05dea1004042313ia8af0e7fl9f11101fa6455483@mail.gmail.com>
	 <D1EE6389-592D-4216-987E-4283BECC7BB7@apache.org>
	 <o2q45ef89081004200915rfe2a7bb3l97ed53e5074365b2@mail.gmail.com>
	 <A9DC438D6CAFFF4BBB299581444408810117FFC0789C@VS-EX-01.intra.vpro.nl>
	 <o2x32870c431004201127hd3be29c1obf1299057e24daf0@mail.gmail.com>
	 <t2k45ef89081004201136m3accd7eeme1885ca16d4b504d@mail.gmail.com>
Date: Tue, 20 Apr 2010 12:33:12 -0700
Message-ID: <i2x45ef89081004201233lc0cac681n673e13a6a8264ea2@mail.gmail.com>
Subject: Re: Dependency problem while installing the new CouchDB-0.11.0
	(libmozjs-dev)
From: Dan Smythe <xkeitarox@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001636c92775f1238c0484b02558

--001636c92775f1238c0484b02558
Content-Type: text/plain; charset=ISO-8859-1

So, here's an interesting tidbit.

If the -static flag is present during the spidermonkey configure tests, they
fail. So,

 -- RHEL ( nor EPEL ) have curl-7.18.0 available for RHEL5, so you have to
force it in (breaking numerous dependencies ) to have a chance with CouchDB
0.11.

 -- Trying to statically compile CouchDB 0.11 fails, because the
spidermonkey ./configure tests fail with the -static flag present.

Therefore, it seems you can only get CouchDB 0.11 running on RHEL5 if you're
OK with breaking any curl dependencies, which I'm not, because it's a long
list and includes php-*.

I'm convinced that CouchDB 0.11 isn't going to fly on RHEL5 at this point.

Anyone manage to do so, with spidermonkey, and without breaking curl
dependencies?

Cheers~


On Tue, Apr 20, 2010 at 11:36 AM, Dan Smythe <xkeitarox@gmail.com> wrote:

> Same thing here Bharat. I'm working on trying to build the RPM with a
> force-installed curl-devel 7.18 RPM I whipped up, hoping to compile CouchDB
> statically against it so I don't have to mess with curl ( and all the other
> dependencies ) on my numerous other hosts. I just can't get this
> spirdermonkey thing worked out.
>
> I'm doing this on a RHEL5 VM, with a snapshot prior to working, so if/when
> I bust anything I can just revert back. I wouldn't suggest taking this path
> on a non-VM.
>
> Cheers~
>
>
> On Tue, Apr 20, 2010 at 11:27 AM, Bharat <bharat.kjsce@gmail.com> wrote:
>
>> I have a similar issue. I am also trying to build couchdb 0.11 rpm from
>> 0.11
>> source, 0.10 spec and init but since I am building on RHEL 5,
>> libcurl-devel
>> version cant go pass 7.15 and 0.11 needs atleast 7.18.
>>
>> any workarounds for that? I dont wanna download 7.18 source and upgrade
>> since this rpm needs to run on several machines and manually upgrading all
>> the machines will be a big pain.
>>
>> Thanks!
>>
>> On Tue, Apr 20, 2010 at 11:17 AM, Nils Breunese <N.Breunese@vpro.nl>
>> wrote:
>>
>> > Did you look at the package that EPEL currently has in their repository
>> for
>> > 0.10? That might have some clues? SRPM is here:
>> >
>> http://download.fedora.redhat.com/pub/epel/5/SRPMS/repoview/couchdb.html
>> >
>> > I have done several CouchDB from source installs following the
>> instructions
>> > on http://wiki.apache.org/couchdb/Installing_on_RHEL5 for dependencies.
>> > Not updated to 0.11 yet, though.
>> >
>> > HTH, Nils.
>> > ________________________________________
>> > Van: Dan Smythe [xkeitarox@gmail.com]
>> > Verzonden: dinsdag 20 april 2010 18:15
>> > Aan: user@couchdb.apache.org
>> > Onderwerp: Re: Dependency problem while installing the new
>> CouchDB-0.11.0
>> >     (libmozjs-dev)
>> >
>> > All --
>> >
>> > Trying to build an RPM out of CouchDB 0.11 and I'm running into a
>> similar
>> > issue. This is on a CentOS 5.4 box, and I've used the directions here:
>> >
>> >
>> http://wiki.apache.org/couchdb/Installing_SpiderMonkey?action=show&redirect=InstallingSpiderMonkeyto
>> > get SpiderMonkey installed in /usr/local/spidermonkey.
>> >
>> > Once installed following the directions, I have
>> > /usr/local/spidermonkey/{bin,include,lib64} which contain the usual
>> files.
>> >
>> > My RPM configure line looks as such:
>> >
>> > %configure --with-erlang=%_libdir/erlang%_includedir \
>> >  --with-js-lib=/usr/local/spidermonkey/lib64 \
>> >  --with-js-include=/usr/local/spidermonkey/include
>> >
>> > Yet still it refuses to locate the libraries:
>> >
>> > /*snip*/
>> > checking for pthread_create in -lpthread... yes
>> > checking for JS_NewContext in -lmozjs... no
>> > checking for JS_NewContext in -ljs... no
>> > checking for JS_NewContext in -ljs3250... no
>> > checking for JS_NewContext in -ljs32... no
>> > configure: error: Could not find the js library.
>> >
>> > Is the Mozilla SpiderMonkey library installed?
>> > error: Bad exit status from /var/tmp/rpm-tmp.2894 (%build)
>> >
>> >
>> > RPM build errors:
>> >    Bad exit status from /var/tmp/rpm-tmp.2894 (%build)
>> > /*snip*/
>> >
>> > I have tried a number of different times and methods. The js-devel
>> package
>> > is installed as well. Furthermore, I've tried to set the LD_LIBRARY_PATH
>> > and
>> > LD_INCLUDE_PATH, all to no avail.
>> >
>> > Anyone have any ideas? I've started from the ground up twice now and am
>> > running out of patience.
>> >
>> > Cheers~
>> >
>> > --Dan
>> >
>> > De informatie vervat in deze  e-mail en meegezonden bijlagen is
>> uitsluitend
>> > bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke
>> informatie
>> > bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of
>> verstrekking
>> > van deze informatie aan derden is voorbehouden aan geadresseerde. De
>> VPRO
>> > staat niet in voor de juiste en volledige overbrenging van de inhoud van
>> een
>> > verzonden e-mail, noch voor tijdige ontvangst daarvan.
>> >
>>
>
>

--001636c92775f1238c0484b02558--