Jiri Drbalek

@jucajuca I did it as you wrote. There were two boost-python libraries on my system and setup.py has chosen the bad one. I noticed these boost-python versions have different name...

I tried your script with Mapnik 3 and got this:  After setting `spacing="50"` to the `TextSymbolizer`: 

Does your Mapnik see fonts? This should print out a list of fonts available to Mapnik by default: ```console python -c "import mapnik; print '\n'.join(mapnik.FontEngine.face_names());" ``` But you should get...

> not sure how to tell python to use built version By setting `PYTHONPATH`. I'm doing it this way ``` export PYTHONPATH=/home/talaj/mapnik-build/lib/python2.7/site-packages ``` while building by ``` ./setup.py develop --prefix...

@Biboba Concerning the missing `mapnik/warning_ignore.hpp` problem, that file is relatively new invention and not yet existing in your version 3.0.0 of Mapnik. You can check it out in https://github.com/mapnik/mapnik/tree/v3.0.0 Concerning...

It is just an idea, but when I was playing with color fonts I was getting this error on some systems only when I was using these color fonts. Maybe...

> How can I check the list of available plugins (and recognized)? ``` js var mapnik = require('mapnik'); mapnik.register_default_input_plugins(); console.log(mapnik.datasources()); ``` Output on my system: ``` js [ 'csv', 'gdal',...

`datasource_cache` is the only place in Mapnik where `std::recursive_mutex` is used: [src/datasource_cache.cpp#L163](https://github.com/mapnik/mapnik/blob/d2ba5e5eec2d71a5c1532b2c2e7ec96f40d82764/src/datasource_cache.cpp#L163). I'm wondering whether this cannot be somehow connected to your problem. Maybe the mutex actually created is not...

Are you building Mapnik directly in Docker? In that case it would be great if you can share the dockerfile.

Thanks, I can reproduce it. Will try to take a look deeper later today.