Control: tags -1 + upstream On Mon, 4 Jul 2016 09:36:08 +0200 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <g...@debian.org> wrote: > On Sun, Jul 3, 2016 at 1:46 PM, Christian Kastner <c...@debian.org> wrote: > > On 2016-07-03 12:30, László Böszörményi (GCS) wrote: > >> In that clean chroot, may you rebuild -13 from source? Then install > >> it still in that chroot and see the output of 'dot'. > > > > You were right: with a rebuilt -13, jpeg is no longer present in > > 'device', either: > Checked the build logs and -13 was built with libjpeg-turbo 1.4.2 and > -14 with 1.5.0 which is a new upstream release and rearranged at least > one pkg-config file. Tried to downgrade libjpeg-turbo 1.4.2 and > rebuilt -13, but the jpeg is still missing from 'devices'. Give me > some days to further look into it until I have a network setup which > likes me. Now it's hard. :(
I've also stumbled over this problem and the issue is that the standard check for libgd in configure.ac still tries to use the obsolete gdlib-config, which has been dropped from libgd in 2.2.1-1 (May 23rd, 2016). Instead, one should use pkg-config. However, gdlib-config --features (which is used by graphviz to detect libgd's supported formats) does not have a proper equivalent in pkg-config. (You should probably ask the libgd2 people what to use instead. Note that custom variables in pkg-config are allowed, so maybe they could add that.) graphviz still finds libgd in another way, but then doesn't think any of it's features are enabled, so HAVE_GD_JPEG etc. are not defined. Regards, Christian
