build error

[jqtrde]

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!

💌

[springmeyer]

@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]

I had the same issue yesterday on an entirely fresh 10.9 installation. For
my part npm install goes 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

wrote:

@jacquestardie https://github.com/jacquestardie - question: did you
recompile mapnik after installing 10.9? Also reported at
mapnik/node-mapnik#189 mapnik/node-mapnik#189.
I'm looking into it (need to get 10.9 set up first myself).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-27515981
.

[springmeyer]

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]

Found a workaround:

rm -rf node_modules/
export CXXFLAGS="-mmacosx-version-min=10.9"
export CFLAGS="-mmacosx-version-min=10.9"
export LDFLAGS="-mmacosx-version-min=10.9"
npm install

[thomasgalambos]

It works, thank you!

[jqtrde]

works here too, thanks @springmeyer

[springmeyer]

@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]

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]

Just tried Safari, opened immediately..

[springmeyer]

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]

yep, grabbing it now

[jqtrde]

The binary is certainly more stable than what I compiled.

I get a segfault when 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]

@jacquestardie - thanks for the details. Regarding uploading: there is no support for uploading at this time.

[cappelaere]

Just add the same problem installing node-mapnik in a node.js app. Thank you for the workaround.
Pat.

[Pana]

TKS, this works for me

[connor]

Workaround worked for me! Thanks @springmeyer

[springmeyer]

@connor - great, thanks for the followup!

[zzolo]

I can confirm that the workaround that @springmeyer mentioned worked for me.
#73 (comment)

[springmeyer]

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]

Thanks! springmeyer's workaround worked for me too