[OSM-dev] mod_tile stable version ?

Bernard Fouché bernard.fouche at kuantic.com
Thu Mar 28 08:11:19 UTC 2013

Le 28/03/2013 02:44, Dane Springmeyer a écrit :
>>   For instance for Tirex I applied such a patch:
>> Index: backend-mapnik/Makefile
>> ===================================================================
>> --- backend-mapnik/Makefile	(revision 29404)
>> +++ backend-mapnik/Makefile	(working copy)
>> @@ -1,7 +1,7 @@
>> INSTALLOPTS=-g root -o root
>> CXXFLAGS = $(CFLAGS) `mapnik-config --cflags`
>> -LDFLAGS= `mapnik-config --libs --ldflags --dep-libs`
>> +LDFLAGS= `mapnik-config --libs --ldflags --dep-libs| sed -e s/-l.agg.//`
> ^^ this looks either like a mapnik-config bug or a packaging bug. Working around in tirex is fine, but personally I would want to understand why -lagg is in the config flags in the first place before fixing this way. As far as I can tell there is not a mapnik version I see that reports -lagg like this.
> Can you provide more details about how you installed mapnik and the exact version of mapnik you see this with to a support ticket at:
> https://github.com/mapnik/mapnik/issues
> Also, if you are using mapnik from some fedora package, then this may be a bug in fedora packaging. Please provide details.
Hello Dan,

done here: https://github.com/mapnik/mapnik/issues/1779
>> Index: backend-mapnik/metatilehandler.cc
>> ===================================================================
>> --- backend-mapnik/metatilehandler.cc	(revision 29404)
>> +++ backend-mapnik/metatilehandler.cc	(working copy)
>> @@ -23,7 +23,7 @@
>> #include <mapnik/datasource_cache.hpp>
>> #include <mapnik/font_engine_freetype.hpp>
>> #include <mapnik/agg_renderer.hpp>
>> -#include <mapnik/expression.hpp>
>> +//#include <mapnik/expression.hpp>
> Thanks for reporting, this is now fixed: https://trac.openstreetmap.org/changeset/29407/subversion
> Note that I am not a tirex user or developer and I did not test this but as a Mapnik developer I know the header is both 1) not needed and 2) was only added in Mapnik 2.x, so including it makes for harder compatibility with multiple versions of Mapnik. So, nice catch.

As stated in the github issue report I just did, I'm using mapnik 
packages tagged 2.0.0-7 : these packages are broken or this file 
appeared after 2.0.0-7.

>> So for Tirex I made up a .tgz of the revision I got including this patch, and have ansible to copy it to the target and recompile it locally. I also copy mapnik fonts,
> You should not need to copy mapnik fonts around. Sounds like a configuration problem or something messed up with the install.

In which packages should the fonts appear? I reported the font problem 
in the same issue, which seems a broken set of RPM for F18 and/or 
missing packages.


More information about the dev mailing list