from /usr/include/GraphicsMagick/magick/api.h:55, from map_geo.c:137: /usr/include/GraphicsMagick/magick/image.h:1108:10: fatal error: magick/image-private.h: No such file or directory 1108 | #include "magick/image-private.h" | ^~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-hardened_libressl_20190615-171927 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * Available Rust versions: [1] rust-1.35.0 * emerge -qpvO media-radio/xastir [ebuild N ] media-radio/xastir-2.1.2 USE="graphicsmagick (-festival) -geotiff"
Created attachment 580290 [details] emerge-info.txt
Created attachment 580292 [details] emerge-history.txt
Created attachment 580294 [details] environment
Created attachment 580296 [details] etc.portage.tbz2
Created attachment 580298 [details] logs.tbz2
Created attachment 580300 [details] media-radio:xastir-2.1.2:20190620-214826.log
Created attachment 580302 [details] temp.tbz2
Bah, I just ran into this. Feels like an media-gfx/graphicsmagick didn't install image-private.h for whatever reason, but why media-radio/xastir is the only package that needs image-private.h I don't know.
I copied image-private.h and pixel_cache-private.h from $GRAPHICSMAGICWORK/GraphicsMagick-1.3.32/magick/ to /usr/include/GraphicsMagick/magick/ and then I was able to emerge xastir - and the GUI seems to come up fine. I'm not an experienced user of xastir yet nor GraphicsMagick - I have a feeling the -private headers were never meant to be installed but in this case they seem to be required.
(In reply to Ben from comment #9) > I copied image-private.h and pixel_cache-private.h from > $GRAPHICSMAGICWORK/GraphicsMagick-1.3.32/magick/ to > /usr/include/GraphicsMagick/magick/ and then I was able to emerge xastir - > and the GUI seems to come up fine. I'm not an experienced user of xastir > yet nor GraphicsMagick - I have a feeling the -private headers were never > meant to be installed but in this case they seem to be required. The bug got fixed in xastir-2.1.4. Please retest with the new version.
Backported fix from xastir-2.1.4 to stable xastir-2.0.8-r1. Dropped buggy versions 2.1.0 and 2.1.2 Please reopen if problem still shows up.
