Gdal is built with the following configure options: --with-libtiff=external --with-geotiff=external This is problematic for other applications depending on the gdal-config utility for finding library that gdal depends on (example: postgis-2.1). With those options, the output of gdal-config looks like this: -ljpeg -Lexternal/lib -lgeotiff -Lexternal/lib Switching those to --with-libtiff and --with-geotiff seems to solve the problem.
Created attachment 348452 [details, diff] Patch which seems to fix the issue
*gdal-1.10.0-r1 (24 Jun 2013) 24 Jun 2013; Aaron W. Swenson <titanofold@gentoo.org> -gdal-1.10.0.ebuild, +gdal-1.10.0-r1.ebuild: Actually apply the changes from bug 468592. Thanks Jean-Claude Repetto. *gdal-1.10.0 (24 Jun 2013) 24 Jun 2013; Aaron W. Swenson <titanofold@gentoo.org> -files/1.7.2-ruby_cflags.patch, -files/gdal-1.4.2-datadir.patch, -files/gdal-1.5.1-python-install.patch, -files/gdal-1.6.0-swig-fix.patch, -files/gdal-1.6.1-ruby-make.patch, -gdal-1.6.3-r1.ebuild, -files/gdal-1.6.3-libpng15.patch, -gdal-1.8.1-r1.ebuild, -gdal-1.9.1.ebuild, -files/gdal-1.9.1-opencl.patch, -files/gdal-1.9.1-poppler-0.20.1.patch, +gdal-1.10.0.ebuild, metadata.xml: Version bump. (Bug 468592) Call java-pkg-opt-2 functions. (Bug 471262; thanks to Tom Wijsman) Remove "=external". (Bug 470046; thanks to Ronan Dunklau.) Clean out old versions and patches, and update hdf to hdf5 in the local USE description.
