Artem Pavlenko

@hholzgra as a quick test you could try defining literal like ```c++ lit("isnot") ``` Just to see everything else works as expected

@cpaulik - looks good :+1: Lets see if I can manage to update test images :) My plan is: * get a fresh `mapnik` clone * `./bootstrap.sh` * `./configure &&...

### reference  ### gdal-do-not-use-special-mapnik-logic-for-overviews  I have 140 visual tests failing, most look OK-ish but I see some artifacts like second letter `V` above ^ Looks like...

https://github.com/mapnik/mapnik/tree/cpaulik-gdal-do-not-use-special-mapnik-logic-for-overviews https://github.com/mapnik/mapnik/compare/cpaulik-gdal-do-not-use-special-mapnik-logic-for-overviews?expand=1 @cpaulik could you verify all is good ^ /cc @talaj @lightmare

@GISerliang - this can be related to `encoding`. If you could share more details (e.g font, dataset changes ), I can try to replicate and see what's going wrong.

@b00ga - Would adding `#include ` conditionally if `BOOST_VERSION >= 1_77` (https://github.com/mapnik/mapnik/commit/737e7a69c2679b33093e1ebf0b4c3fa34ae36878) solve this issue for you ? /cc @mathisloge

@b00ga For your particular use case, would you consider building boost libraries yourself? This is what I do on Linux: 1. `cd boost_dir` 2. `./bootstrap.sh` // to build latest `b2`...

@yohanboniface - I don't see anything obvious from configure stderr. Could you re-post link to full log, I'm getting `Not found`?

Could you post output from `nm -C srs/libmapnik.so | grep feature_style_processor` ?

@yohanboniface so the symbol in question is defined `libmapnik.so` hmm.. it's difficult to guess how your build system configured exactly, perhaps you have multiple `libmapnik.so` libs accessible via `LD_LIBRARY_PATH` ?