You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "john.tiger" <jo...@gmail.com> on 2012/11/11 21:36:44 UTC
cors testing build
just went to compile on another debian testing machine
I'm getting that spider monkey version is too new ? xulrunner-devel-10.0
that same version formerly compiled the stable couchdb package. maybe
something else is at play here ?
Re: cors testing build
Posted by "john.tiger" <jo...@gmail.com>.
On 11/12/2012 10:59 AM, Dave Cottlehuber wrote:
> On 12 November 2012 00:06, john.tiger <jo...@gmail.com> wrote:
>
>> removed the xulrunner stuff - ran configure with libmozjs (as per wiki) -
>> still same newer version error - this is on Debian Testing
> amd64? i386?
i386 but hopefully w/ Debian it shouldn't matter
>
> I'll try with 7.0 b3 amd64 here.
>
>> I see that there was a lot of discussion on this earlier in year - hope we
>> can resolve and should probably have something in release notes for 1.3
>> since many will be developing from source until pkgs catch up
> yup, sigh, its a real PITA this is.
>
>> Also re the python sphinx installation - failing on the "source" line - what
>> is source supposed to be ?
> The variables are all $PREFIXED_IN_CAPS. So source is just that,
> source, a bash/zsh shell built-in. Given I'm a relative newcomer to
> unix that could be wrong, btu it's fine on my mac (not really a
> veritable paragon of adherence to the One Unix Way).
>
> Noah's added lots of tex-stuff which I still haven't gotten working -
> YMMV on that.
>
> A+
> Dave
>
Re: cors testing build
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 12 November 2012 00:06, john.tiger <jo...@gmail.com> wrote:
> removed the xulrunner stuff - ran configure with libmozjs (as per wiki) -
> still same newer version error - this is on Debian Testing
amd64? i386?
I'll try with 7.0 b3 amd64 here.
> I see that there was a lot of discussion on this earlier in year - hope we
> can resolve and should probably have something in release notes for 1.3
> since many will be developing from source until pkgs catch up
yup, sigh, its a real PITA this is.
> Also re the python sphinx installation - failing on the "source" line - what
> is source supposed to be ?
The variables are all $PREFIXED_IN_CAPS. So source is just that,
source, a bash/zsh shell built-in. Given I'm a relative newcomer to
unix that could be wrong, btu it's fine on my mac (not really a
veritable paragon of adherence to the One Unix Way).
Noah's added lots of tex-stuff which I still haven't gotten working -
YMMV on that.
A+
Dave
Re: cors testing build
Posted by Noah Slater <ns...@apache.org>.
If we get a fix, Debian can include a patch.
On 1 December 2012 21:52, Randall Leeds <ra...@gmail.com> wrote:
> It presents a real problem for packaging on debian unstable.
>
>
> On Sat, Dec 1, 2012 at 11:58 AM, Robert Newson <robert.newson@gmail.com
> >wrote:
>
> > No, but problem when we support > 1.8.5
> >
> > Sent from the ocean floor
> >
> > On 1 Dec 2012, at 19:49, Noah Slater <ns...@apache.org> wrote:
> >
> > > On 13 November 2012 22:44, Randall Leeds <ra...@gmail.com>
> > wrote:
> > >
> > >> https://issues.apache.org/jira/browse/COUCHDB-1602
> > >
> > >
> > > Is this a blocker for 1.3?
> > >
> > > --
> > > NS
> >
>
--
NS
Re: cors testing build
Posted by Randall Leeds <ra...@gmail.com>.
It presents a real problem for packaging on debian unstable.
On Sat, Dec 1, 2012 at 11:58 AM, Robert Newson <ro...@gmail.com>wrote:
> No, but problem when we support > 1.8.5
>
> Sent from the ocean floor
>
> On 1 Dec 2012, at 19:49, Noah Slater <ns...@apache.org> wrote:
>
> > On 13 November 2012 22:44, Randall Leeds <ra...@gmail.com>
> wrote:
> >
> >> https://issues.apache.org/jira/browse/COUCHDB-1602
> >
> >
> > Is this a blocker for 1.3?
> >
> > --
> > NS
>
Re: cors testing build
Posted by Robert Newson <ro...@gmail.com>.
No, but problem when we support > 1.8.5
Sent from the ocean floor
On 1 Dec 2012, at 19:49, Noah Slater <ns...@apache.org> wrote:
> On 13 November 2012 22:44, Randall Leeds <ra...@gmail.com> wrote:
>
>> https://issues.apache.org/jira/browse/COUCHDB-1602
>
>
> Is this a blocker for 1.3?
>
> --
> NS
Re: cors testing build
Posted by Noah Slater <ns...@apache.org>.
On 13 November 2012 22:44, Randall Leeds <ra...@gmail.com> wrote:
> https://issues.apache.org/jira/browse/COUCHDB-1602
Is this a blocker for 1.3?
--
NS
Re: cors testing build
Posted by Randall Leeds <ra...@gmail.com>.
Issue-ified: https://issues.apache.org/jira/browse/COUCHDB-1602
On Tue, Nov 13, 2012 at 2:41 PM, Randall Leeds <ra...@gmail.com>wrote:
> I bisected mozilla-central and believe I found the commit that removed
> that operator overload[0].
> Looks like we have a little more work to do before couch works with trunk
> spidermonkey.
> I do find it strange that Debian (even in testing) ships these unreleased
> versions.
>
> [0]
> https://github.com/mozilla/mozilla-central/commit/96a3b337000b2d0757cc32ba41815a580613123e
>
>
>
> On Mon, Nov 12, 2012 at 5:10 PM, john.tiger <jo...@gmail.com>wrote:
>
>> On 11/12/2012 03:36 PM, Randall Leeds wrote:
>>
>>> ./configure --enable-js-trunk
>>>
>> thks
>> on debian testing i386 configure runs okay
>>
>> but make breaks
>> couch_js/util.c: In function ‘couch_print’:
>> couch_js/util.c:216:33: error: invalid operands to binary == (have
>> ‘jsval’ and ‘jsval’)
>> make[4]: *** [couchjs-util.o] Error 1
>> make[4]: Leaving directory `/home/couchdbtest/couchdb-**
>> 915c811/src/couchdb/priv'
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory `/home/couchdbtest/couchdb-**
>> 915c811/src/couchdb'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/home/couchdbtest/couchdb-**915c811/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/couchdbtest/couchdb-**915c811'
>> make: *** [all] Error 2
>>
>>
>>
>>
>>
>>
>
Re: cors testing build
Posted by Randall Leeds <ra...@gmail.com>.
I bisected mozilla-central and believe I found the commit that removed that
operator overload[0].
Looks like we have a little more work to do before couch works with trunk
spidermonkey.
I do find it strange that Debian (even in testing) ships these unreleased
versions.
[0]
https://github.com/mozilla/mozilla-central/commit/96a3b337000b2d0757cc32ba41815a580613123e
On Mon, Nov 12, 2012 at 5:10 PM, john.tiger <jo...@gmail.com>wrote:
> On 11/12/2012 03:36 PM, Randall Leeds wrote:
>
>> ./configure --enable-js-trunk
>>
> thks
> on debian testing i386 configure runs okay
>
> but make breaks
> couch_js/util.c: In function ‘couch_print’:
> couch_js/util.c:216:33: error: invalid operands to binary == (have ‘jsval’
> and ‘jsval’)
> make[4]: *** [couchjs-util.o] Error 1
> make[4]: Leaving directory `/home/couchdbtest/couchdb-**
> 915c811/src/couchdb/priv'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/couchdbtest/couchdb-**
> 915c811/src/couchdb'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/couchdbtest/couchdb-**915c811/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/couchdbtest/couchdb-**915c811'
> make: *** [all] Error 2
>
>
>
>
>
>
Re: cors testing build
Posted by "john.tiger" <jo...@gmail.com>.
On 11/12/2012 03:36 PM, Randall Leeds wrote:
> ./configure --enable-js-trunk
thks
on debian testing i386 configure runs okay
but make breaks
couch_js/util.c: In function ‘couch_print’:
couch_js/util.c:216:33: error: invalid operands to binary == (have
‘jsval’ and ‘jsval’)
make[4]: *** [couchjs-util.o] Error 1
make[4]: Leaving directory
`/home/couchdbtest/couchdb-915c811/src/couchdb/priv'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/couchdbtest/couchdb-915c811/src/couchdb'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/couchdbtest/couchdb-915c811/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/couchdbtest/couchdb-915c811'
make: *** [all] Error 2
Re: cors testing build
Posted by Randall Leeds <ra...@gmail.com>.
./configure --enable-js-trunk
The rationale is that in the newest builds of spidermonkey (actually
post-1.8.5, which Debian ships in testing), a bug was corrected which was
previously tolerated by the interpreter. The result is that our typical
map/reduce examples break.
If I recall correctly,
function (doc) {
emit(doc._id, 1);
}
becomes
var map = function (doc) {
emit(doc._id, 1);
}
In other words, top-level, anonymous functions are no longer allowed and we
have not yet decided exactly what to do about it. Some attempts were made
to automatically forward-port old views, but they are brittle enough that
we haven't decided to do it automatically.
Therefore, building with ./configure --enable-js-trunk is there as a little
warning that you have to take care with how you write your views until we
decide how to proceed with js > 1.8.5 view functions.
On Sun, Nov 11, 2012 at 3:06 PM, john.tiger <jo...@gmail.com>wrote:
> On 11/11/2012 02:33 PM, Dave Cottlehuber wrote:
>
>> On 11 November 2012 21:36, john.tiger <jo...@gmail.com> wrote:
>>
>>> just went to compile on another debian testing machine
>>>
>>> I'm getting that spider monkey version is too new ? xulrunner-devel-10.0
>>>
>>> that same version formerly compiled the stable couchdb package. maybe
>>> something else is at play here ?
>>>
>>>
>>> Hi John,
>>
>> I updated http://wiki.apache.org/**couchdb/Installing_on_Debian<http://wiki.apache.org/couchdb/Installing_on_Debian>
>> recently, the key packages are libmozjs-dev libmozjs2d.
>>
>> If you need xulrunner for something else, you may need to fiddle a
>> little with the various js include parameters in configure to nudge it
>> in the right direction.
>>
>> If that doesn't work, tell us what version of debian it is, and what
>> configure you're using, and I will give it a look tomorrow.
>>
>
> removed the xulrunner stuff - ran configure with libmozjs (as per wiki) -
> still same newer version error - this is on Debian Testing
>
> I see that there was a lot of discussion on this earlier in year - hope we
> can resolve and should probably have something in release notes for 1.3
> since many will be developing from source until pkgs catch up
>
> Also re the python sphinx installation - failing on the "source" line -
> what is source supposed to be ?
>
>
>
>
>
>> A+
>> Dave
>>
>>
>
Re: cors testing build
Posted by "john.tiger" <jo...@gmail.com>.
On 11/11/2012 02:33 PM, Dave Cottlehuber wrote:
> On 11 November 2012 21:36, john.tiger <jo...@gmail.com> wrote:
>> just went to compile on another debian testing machine
>>
>> I'm getting that spider monkey version is too new ? xulrunner-devel-10.0
>>
>> that same version formerly compiled the stable couchdb package. maybe
>> something else is at play here ?
>>
>>
> Hi John,
>
> I updated http://wiki.apache.org/couchdb/Installing_on_Debian
> recently, the key packages are libmozjs-dev libmozjs2d.
>
> If you need xulrunner for something else, you may need to fiddle a
> little with the various js include parameters in configure to nudge it
> in the right direction.
>
> If that doesn't work, tell us what version of debian it is, and what
> configure you're using, and I will give it a look tomorrow.
removed the xulrunner stuff - ran configure with libmozjs (as per wiki)
- still same newer version error - this is on Debian Testing
I see that there was a lot of discussion on this earlier in year - hope
we can resolve and should probably have something in release notes for
1.3 since many will be developing from source until pkgs catch up
Also re the python sphinx installation - failing on the "source" line -
what is source supposed to be ?
>
> A+
> Dave
>
Re: cors testing build
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 11 November 2012 21:36, john.tiger <jo...@gmail.com> wrote:
> just went to compile on another debian testing machine
>
> I'm getting that spider monkey version is too new ? xulrunner-devel-10.0
>
> that same version formerly compiled the stable couchdb package. maybe
> something else is at play here ?
>
>
Hi John,
I updated http://wiki.apache.org/couchdb/Installing_on_Debian
recently, the key packages are libmozjs-dev libmozjs2d.
If you need xulrunner for something else, you may need to fiddle a
little with the various js include parameters in configure to nudge it
in the right direction.
If that doesn't work, tell us what version of debian it is, and what
configure you're using, and I will give it a look tomorrow.
A+
Dave