emerge of sci-geosciences/mapnik concludes without error. According to the MapNik documentation at http://trac.mapnik.org/wiki/GettingStarted: Make sure you have mapnik installed. Depending on your installation path you may need to modify your PYTHONPATH, /etc/ld.so.conf or export LD_LIBRARY_PATH, or whatever your system requires. The simple check is to start python interpreter from a command line by typing python and then just type: >>> import mapnik and if you don't see any complaints, you're on the right track. If you do, you have to check your installation again. Reproducible: Always Steps to Reproduce: 1. python 2. import mapnik Actual Results: hermes examples # python Python 2.6.5 (release26-maint, Aug 24 2010, 15:25:45) [GCC 4.4.4] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import mapnik Problem loading plugin library: /usr/lib64/mapnik/input/ogr.input (libtool error: file not found) Problem loading plugin library: /usr/lib64/mapnik/input/gdal.input (libtool error: file not found) registered datasource : postgis registered datasource : raster registered datasource : sqlite registered datasource : shape >>> Expected Results: hermes examples # python Python 2.6.5 (release26-maint, Aug 24 2010, 15:25:45) [GCC 4.4.4] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import mapnik registered datasource : postgis registered datasource : raster registered datasource : sqlite registered datasource : shape >>> Here's the final installation notes: >>> Completed installing mapnik-0.6.1-r3 into /var/tmp/portage/sci-geosciences/mapnik-0.6.1-r3/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/lib64/python2.6/site-packages/mapnik/_mapnik.so usr/lib64/mapnik/input/ogr.input usr/lib64/mapnik/input/gdal.input usr/lib64/mapnik/input/postgis.input usr/lib64/mapnik/input/raster.input usr/lib64/mapnik/input/sqlite.input usr/lib64/mapnik/input/shape.input usr/lib64/libmapnik.so.0.6.1 usr/bin/shapeindex usr/bin/pgsql2sqlite >>> Installing (1 of 1) sci-geosciences/mapnik-0.6.1-r3 * * See the home page or the OpenStreetMap wiki for more info, and * the installed examples for the default mapnik ogcserver config. * * Messages for package sci-geosciences/mapnik-0.6.1-r3: * mapnik-0.6.1 BOOST_VERSION is 1_39 * mapnik-0.6.1 BOOST_INC is /usr/include/boost-1_39 * mapnik-0.6.1 BOOST_LIB is /usr/lib64/boost-1_39 * * See the home page or the OpenStreetMap wiki for more info, and * the installed examples for the default mapnik ogcserver config. * >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. hermes examples #
Please try running: $ /usr/lib64/mapnik/input/ogr.input $ /usr/lib64/mapnik/input/gdal.input
ouch: hermes var # /usr/lib64/mapnik/input/ogr.input Segmentation fault hermes var # /usr/lib64/mapnik/input/gdal.input Segmentation fault hermes var #
(In reply to comment #2) > ouch: > hermes var # /usr/lib64/mapnik/input/ogr.input > Segmentation fault > hermes var # /usr/lib64/mapnik/input/gdal.input > Segmentation fault That's normal. Doesn't look like having broken linkage.
"import mapnik" gives me no errors, and no output at all...
Seems to work with 2.0.1 at least here. Please reopen or open new bug if you can reproduce it with that version.
I successfully emerged mapnik: [I] sci-geosciences/mapnik Available versions: (~)0.7.1-r1 (~)0.7.1-r2 {M}(~)2.0.0 [M](~)9999[1] {bidi cairo curl debug (-)doc (+)gdal geos nobfonts postgres proj python sqlite} Installed versions: 2.0.0(07:15:19 05/26/12)(cairo debug gdal postgres python sqlite -bidi -doc -geos -nobfonts) Homepage: http://www.mapnik.org/ Description: A Free Toolkit for developing mapping applications. I had to tweak some settings and add "python" as a use variable to dev-libs/boost. After all that, I tried an assay (with the new 2.0 tool mapnik-conf and nothing happened. hermes ~ # mapnik-config -v hermes ~ # This is a different issue and warrants a different bug which I may get around to logging at some point; however, I did not want someone visiting this bug to think all is well by a lack of comment by me. Since this really wasn't "Fixed", I'm changing the status to "Obsolete".
