Error when building /Windshaft-cartodb

313 views
Skip to first unread message

Christian Ledermann

unread,
May 10, 2012, 12:21:27 PM5/10/12
to cartodb
Waf: Leaving directory
`/home/iwlearn3/downloads/Windshaft-cartodb/node_modules/windshaft/node_modules/tilelive-mapnik-cartodb/node_modules/mapnik/build'
Build failed:
-> task failed (err #1):
{task: cxx mapnik_geometry.cpp -> mapnik_geometry_1.o}
-> task failed (err #1):
{task: cxx mapnik_feature.cpp -> mapnik_feature_1.o}
-> task failed (err #1):
{task: cxx mapnik_grid.cpp -> mapnik_grid_1.o}
-> task failed (err #1):
{task: cxx mapnik_grid_view.cpp -> mapnik_grid_view_1.o}
-> task failed (err #1):
{task: cxx node_mapnik.cpp -> node_mapnik_1.o}
-> task failed (err #1):
{task: cxx mapnik_map.cpp -> mapnik_map_1.o}
npm ERR! error installing map...@0.5.11 Error: map...@0.5.11 install:
`node-waf -v configure build`
npm ERR! error installing map...@0.5.11 `sh "-c" "node-waf -v
configure build"` failed with 1
npm ERR! error installing map...@0.5.11 at
ChildProcess.<anonymous>
(/home/iwlearn3/lib/node_modules/npm/lib/utils/exec.js:49:20)
npm ERR! error installing map...@0.5.11 at ChildProcess.emit
(events.js:67:17)
npm ERR! error installing map...@0.5.11 at ChildProcess.onexit
(child_process.js:192:12)
npm ERR! error installing tilelive-ma...@0.2.4 Error:
map...@0.5.11 install: `node-waf -v configure build`
npm ERR! error installing tilelive-ma...@0.2.4 `sh "-c"
"node-waf -v configure build"` failed with 1
npm ERR! error installing tilelive-ma...@0.2.4 at
ChildProcess.<anonymous>
(/home/iwlearn3/lib/node_modules/npm/lib/utils/exec.js:49:20)
npm ERR! error installing tilelive-ma...@0.2.4 at
ChildProcess.emit (events.js:67:17)
npm ERR! error installing tilelive-ma...@0.2.4 at
ChildProcess.onexit (child_process.js:192:12)
npm ERR! error installing wind...@0.4.6 Error: map...@0.5.11
install: `node-waf -v configure build`
npm ERR! error installing wind...@0.4.6 `sh "-c" "node-waf -v
configure build"` failed with 1
npm ERR! error installing wind...@0.4.6 at
ChildProcess.<anonymous>
(/home/iwlearn3/lib/node_modules/npm/lib/utils/exec.js:49:20)
npm ERR! error installing wind...@0.4.6 at ChildProcess.emit
(events.js:67:17)
npm ERR! error installing wind...@0.4.6 at ChildProcess.onexit
(child_process.js:192:12)
npm ERR! map...@0.5.11 install: `node-waf -v configure build`
npm ERR! `sh "-c" "node-waf -v configure build"` failed with 1
npm ERR!
npm ERR! Failed at the map...@0.5.11 install script.
npm ERR! This is most likely a problem with the mapnik package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf -v configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls mapnik
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Linux 2.6.32-220.13.1.el6.x86_64
npm ERR! command "node" "/home/iwlearn3/bin/npm" "install"
npm ERR! cwd /home/iwlearn3/downloads/Windshaft-cartodb
npm ERR! node -v v0.4.12
npm ERR! npm -v 1.0.106
npm ERR! code ELIFECYCLE
g++ -o obj/jsatom.o -c -Wall -Wno-format -MMD -DXP_UNIX -DSVR4 -DSYSV
-D_BSD_SOURCE -DPOSIX_SOURCE -DHAVE_LOCALTIME_R -DLINUX -DHAVE_VA_COPY
-DVA_COPY=va_copy -DPIC -fPIC -UDEBUG -DNDEBUG -UDEBUG_iwlearn3
-DEDITLINE -I. -I./obj -Os -fstrict-aliasing -fno-exceptions
-fno-rtti -Wstrict-aliasing=2 jsatom.cpp
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/iwlearn3/downloads/Windshaft-cartodb/npm-debug.log
npm not ok



my mapnik is installed in /home/iwlearn3

with the libraries in /home/iwlearn3/lib64
and LD_LIBRARY_PATH=/home/iwlearn3/lib:/home/iwlearn3/lib64

any pointers?

--
Best Regards,

Christian Ledermann

Nairobi - Kenya
Mobile : +254 702978914

<*)))>{

If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.

1) Don’t drive species to extinction

2) Don’t destroy a habitat that species rely on.

3) Don’t change the climate in ways that will result in the above.

}<(((*>

Dane Springmeyer

unread,
May 10, 2012, 4:18:08 PM5/10/12
to car...@googlegroups.com
Your Mapnik version is likely too new. Windshaft is pinned against a version of node-mapnik (javascript bindings to mapnik) that expects the 2.0.0 be available.

If you are wondering, TileMill however tracks the latest tag of node-mapnik, which itself tracks mapnik master, which makes running cartodb alongside TileMill not feasible on the same machine.

I'd like to avoid this problem in the future - which would require getting a Mapnik 2.1 release in the wild and this is on target for the next month or so - at that time hopefully both Cartodb and TileMill (and other apps using node-mapnik) will be able to pin against the 2.1.0 release.

Dane

Javier de la Torre

unread,
May 10, 2012, 4:38:49 PM5/10/12
to car...@googlegroups.com
HEy Dane,

Thanks for the response. Yes, CartoDB only works with Mapnik 2.0.0

Yes, we will do our best to upgrade to 2.1 when it becomes available.

Christian Ledermann

unread,
May 11, 2012, 2:44:56 AM5/11/12
to car...@googlegroups.com
right the installation succeeds with mapnik 2.0.1


A few hints when installing mapnik into your $HOME (i.e when you do not have
root access on your machine):

set:
LD_LIBRARY_PATH=$HOME/lib:$HOME/lib64

before you install mapnik (on a 64 bit linux)

If you already have boost installed with a package manager and mapnik
is fine with that version do NOT try to install a newer version from source,
that will give you a lot of headaches!

mapniks

$ ./configure --prefix=$HOME

will sometimes ignore the prefix and still try to install it in
/usr/local anyway
check with

$ ./configure --help

that is has the right install path and finds the right python before you run

$ make install


thanks for your help :)

On Thu, May 10, 2012 at 11:38 PM, Javier de la Torre <jat...@gmail.com> wrote:
> HEy Dane,
>
> Thanks for the response. Yes, CartoDB only works with Mapnik 2.0.0

--
Best Regards,

Christian Ledermann

Nairobi - Kenya

Alberto Labarga

unread,
Jul 28, 2012, 11:43:14 PM7/28/12
to car...@googlegroups.com
HI,

 I installed mapnik-2.0 according to instructions here


basically,

sudo add-apt-repository ppa:mapnik/nightly-2.0
sudo apt-get update
sudo apt-get install libmapnik mapnik-utils python-mapnik

and I am getting a similar error,

should I get mapnik-2.0.0 and install from source?

 thanks for your help,

Alberto


Travis Webb

unread,
Dec 2, 2012, 11:58:07 PM12/2/12
to car...@googlegroups.com
I am also seeing the same error in trying to setup CartoDB 2.0. I am using mapnik 2.0.2. What can I do?

Sandro Santilli

unread,
Dec 3, 2012, 3:51:06 AM12/3/12
to car...@googlegroups.com
On Sun, Dec 02, 2012 at 08:58:07PM -0800, Travis Webb wrote:
> I am also seeing the same error in trying to setup CartoDB 2.0. I am using
> mapnik 2.0.2. What can I do?
...
> > npm ERR! node -v v0.4.12
> > npm ERR! npm -v 1.0.106
> > npm ERR! code ELIFECYCLE
...
> > npm ERR! Additional logging details can be found in:
> > npm ERR! /home/iwlearn3/downloads/Windshaft-cartodb/npm-debug.log

You need node-0.8+ to use Windshaft-CartoDB.
Update node or try the `node0.4` branch (unrecommended).

--strk;

http://www.cartodb.com - Map, analyze and build applications with your data

~~ http://strk.keybit.net

Travis Webb

unread,
Dec 3, 2012, 9:14:48 AM12/3/12
to car...@googlegroups.com
I am using node 0.8.15. 

Side note: CartoDB's README dumbly says that it will only work with node versions 0.4 <= x < 0.5: https://github.com/Vizzuality/cartodb


--




Sandro Santilli

unread,
Dec 3, 2012, 9:23:38 AM12/3/12
to car...@googlegroups.com
On Mon, Dec 03, 2012 at 09:14:48AM -0500, Travis Webb wrote:
> I am using node 0.8.15.

In that case I suggest you ask on the mapnik mailing list or tracker
as that's the component that was failing to install (reading the
error log).

> Side note: CartoDB's README dumbly says that it will only work with node
> versions 0.4 <= x < 0.5: https://github.com/Vizzuality/cartodb

Thanks for pointing that out. CartoDB component itself actually doesn't
need node at all. I guess the correct fix here would be to simply report
that CartoDB depends on Windshaft-CartoDB and CartoDB-SQL-API and leave
install instructions for them to their own.

--strk;

Travis Webb

unread,
Dec 3, 2012, 11:33:36 AM12/3/12
to car...@googlegroups.com
Yes I think that would be better. It's very confusing to say "install node 0.4.11", and then in the next step it say "ok, now install node 0.8.x"
Reply all
Reply to author
Forward
0 new messages