This repository was archived by the owner on Dec 3, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 3, 2018. It is now read-only.
build error #73
Description
osx: 10.9 node -v: 0.10.21 mapnik: 2.2.0
Ran through the source install steps as described here.
Getting the following error on node index.js
dyld: lazy symbol binding failed: Symbol not found: __ZN6mapnik16datasource_cache20register_datasourcesERKSs
Referenced from: /Users/Jacques/bin/tm2/node_modules/mapnik/lib/_mapnik.node
Expected in: dynamic lookup
dyld: Symbol not found: __ZN6mapnik16datasource_cache20register_datasourcesERKSs
Referenced from: /Users/Jacques/bin/tm2/node_modules/mapnik/lib/_mapnik.node
Expected in: dynamic lookup
[1] 71880 trace trap node index.js
I'd happily just use one of the binaries, but https://tilemill.s3.amazonaws.com/index.html?path=dev/ just sits at loading... forever.
I want to make cool maps like AJ Ashton!
💌
Activity
springmeyer commentedon Oct 31, 2013
@jacquestardie - question: did you recompile mapnik after installing 10.9? Also reported at mapnik/node-mapnik#189. I'm looking into it (need to get 10.9 set up first myself).
rclark commentedon Oct 31, 2013
I had the same issue yesterday on an entirely fresh 10.9 installation. For
my part
npm installgoes fine (once I installed xcode in its entirety),but these errors are thrown when I try and run tm2.
On Thu, Oct 31, 2013 at 12:08 PM, Dane Springmeyer <notifications@github.com
springmeyer commentedon Nov 1, 2013
The root of problem appears to be that while libmapnik is being properly linked to libc++ (when rebuilt on 10.9) node-mapnik still ending up linking to libstdc++. Linking to 2 different incompatible c++ standard libraries is not going to work. Node itself is also linking to libstdc++ (even when I compile from source on homebrew).
So, I have no viable workaround yet: will continue investigating tomorrow.
springmeyer commentedon Nov 1, 2013
Found a workaround:
thomasgalambos commentedon Nov 1, 2013
It works, thank you!
jqtrde commentedon Nov 1, 2013
works here too, thanks @springmeyer
springmeyer commentedon Nov 1, 2013
@jacquestardie - glad the workaround fixed your source compile. However the binaries should work. Can you tell me which binary you tried and provide more detail about the hang? I just tested the latest one: http://tilemill.s3.amazonaws.com/dev/tm2-osx-2013-11-01-d734ec2.tar.gz. I needed to edit my security settings to be able to run the
start.command, but otherwise things worked:jqtrde commentedon Nov 1, 2013
Didn't actually get to try any of the binaries. https://tilemill.s3.amazonaws.com/index.html?path=dev/ just sits and hangs for me.
Can wait here 30m, and it'll just keep
loading.... I've tried with different connections, always using Chrome.jqtrde commentedon Nov 1, 2013
Just tried Safari, opened immediately..
springmeyer commentedon Nov 1, 2013
ah, I see. cool, well can you try http://tilemill.s3.amazonaws.com/dev/tm2-osx-2013-11-01-d734ec2.tar.gz ? I'd also be interested if you can detect any differences in performance between the binary and your source compiled version, but no worries if you can't.
jqtrde commentedon Nov 1, 2013
yep, grabbing it now
jqtrde commentedon Nov 1, 2013
The binary is certainly more stable than what I compiled.
I get a
segfaultwhen I try to affect any of the options in the compiled version. In addition, the basemap itself doesn't render with the source build. Meanwhile, the binary works fine.I'm hoping to get around to actually making and uploading a map later today, if I have any issues I'll post em up.
springmeyer commentedon Nov 1, 2013
@jacquestardie - thanks for the details. Regarding uploading: there is no support for uploading at this time.
cappelaere commentedon Nov 20, 2013
Just add the same problem installing node-mapnik in a node.js app. Thank you for the workaround.
Pat.
Pana commentedon Nov 21, 2013
TKS, this works for me
connor commentedon Jan 9, 2014
Workaround worked for me! Thanks @springmeyer
springmeyer commentedon Jan 9, 2014
@connor - great, thanks for the followup!
zzolo commentedon Feb 12, 2014
I can confirm that the workaround that @springmeyer mentioned worked for me.
#73 (comment)
springmeyer commentedon Aug 11, 2014
Note: the final solution I arrived at to avoid this issue was mapnik/node-mapnik@e21503b. But overall this only ever a problem with source installed node-mapnik + externally compiled mapnik on 10.9 and luckily this is much more of a rare case now that node-mapnik ships with https://github.com/mapbox/node-pre-gyp binaries.
andfinally commentedon Sep 11, 2015
Thanks! springmeyer's workaround worked for me too