Configuring on Linux in *release mode*... Checking for dlfcn.h support ... yes KeyError: 'LIBPATH': File "/var/tmp/portage/sci-geosciences/mapnik-3.0.18/work/mapnik-v3.0.18/SConstruct", line 1472: conf.prioritize_paths(silent=True) File "/usr/lib64/python2.7/site-packages/SCons/SConf.py", line 693: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_20190327-141919 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy3 (fallback) [4] pypy (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * emerge -qpvO sci-geosciences/mapnik [ebuild N ] sci-geosciences/mapnik-3.0.18 USE="-cairo -debug -doc -gdal -osmfonts -postgres -sqlite"
Created attachment 571144 [details] emerge-info.txt
Created attachment 571146 [details] emerge-history.txt
Created attachment 571148 [details] environment
Created attachment 571150 [details] etc.portage.tbz2
Created attachment 571152 [details] logs.tbz2
Created attachment 571154 [details] sci-geosciences:mapnik-3.0.18:20190329-080551.log
Created attachment 571156 [details] temp.tbz2
I did also run into this issue. I could fix is by downgrading dev-util/scons from 3.0.5 to 3.0.4. Afterwards I could emerge mapnik without any issues.
(In reply to Per Pascal Seeland from comment #8) > I did also run into this issue. I could fix is by downgrading dev-util/scons > from 3.0.5 to 3.0.4. Afterwards I could emerge mapnik without any issues. the same here: after downgrading to dev-util/scons-3.0.4 the installation of sci-geosciences/mapnik-3.0.18 works fine.
Upstream bug report: https://github.com/mapnik/mapnik/issues/4081
*** Bug 714144 has been marked as a duplicate of this bug. ***
Hi guys, I ran into this problem with the latest scons (3.1.2) as well. Since there is no ebuild for 3.0.4 to overcome this bug. I see in mapnik build instructions that they bundle scons now. [https://github.com/mapnik/mapnik/blob/master/INSTALL.md] I think the best way is to bump mapnik to a more recent version and until then to mask the package as unbuildable.
(In reply to milev.philip from comment #12) [...] > I see in mapnik build instructions that they bundle scons now. > [https://github.com/mapnik/mapnik/blob/master/INSTALL.md] pls see my ebuild proposal attached to bug 691130.
Package removed.
