couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1197) trunk no longer builds on Windows
Date Thu, 16 Jun 2011 02:38:47 GMT


Dave Cottlehuber commented on COUCHDB-1197:

Error with jsapi.h is:

checking for JS... no
checking for JS_NewContext in -lmozjs... yes
checking for iscc... /relax/inno5/iscc
checking jsapi.h usability... no
checking jsapi.h presence... yes
configure: WARNING: jsapi.h: present but cannot be compiled
configure: WARNING: jsapi.h:     check for missing prerequisite headers?
configure: WARNING: jsapi.h: see the Autoconf documentation
configure: WARNING: jsapi.h:     section "Present But Cannot Be Compiled"
configure: WARNING: jsapi.h: proceeding with the compiler's result
checking for jsapi.h... no
checking js/jsapi.h usability... no
checking js/jsapi.h presence... no
checking for js/jsapi.h... no
configure: error: Could not find the jsapi header.

successful configure from 1.1.0:
checking for pthread_create in -lpthread... no
checking for JS_NewContext in -lmozjs... yes
checking for iscc... /relax/inno5/iscc
checking jsapi.h usability... yes
checking jsapi.h presence... yes

> trunk no longer builds on Windows
> ---------------------------------
>                 Key: COUCHDB-1197
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System, JavaScript View Server
>         Environment: Windows 7 Enterprise x64
> Cygwin
> MS Visual Studio 2008 Express
>            Reporter: Dave Cottlehuber
>              Labels: cygwin, windows
>             Fix For: 1.2
>         Attachments: COUCHDB-1197_fix_libcurl.patch
> ./configure fails
> - can no longer correctly find libcurl (after COUCHDB-1042) and instead compiles against
cygwin's curl which is *bad*. Patch attached to resolve this.
> - finds jsapi.h correctly but can no longer use it. Work by dch to identify when it broke
and how to fix this underway.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message