On Sat, Oct 04, 2014 at 04:34:11PM +0200, David Suárez wrote:
> Hi Moritz,
>
> El Viernes, 3 de octubre de 2014 16:45:52 Moritz Mühlenhoff escribió:
> > On Sun, Sep 28, 2014 at 06:41:58PM +0200, David Suárez wrote:
> > > Source: fbi
> > > Version: 2.07-14
> > > Severity: serious
> > > Tags: jessie sid
> > > User: debian...@lists.debian.org
> > > Usertags: qa-ftbfs-20140926 qa-ftbfs
> > > Justification: FTBFS on amd64
> > >
> > > Hi,
> > >
> > > During a rebuild of all packages in sid, your package failed to build on
> > > amd64.
> >
> > Hi David,
> > thanks for your archive rebuilds. I tried to reproduce this, but fbi builds
> > fine with current unstable. Can you still reproduce it?
>
> Just build it again some minutes ago. It's still failing.
>
> Failure lines:
>
> > Make.config written, edit if needed
> >
> > CC exiftran.o
> > CC genthumbnail.o
> > CC jpegtools.o
> > CC jpeg/transupp.o
> > In file included from jpeg/transupp.c:21:0:
> > jpeg/jpeglib.h:40:0: warning: "JPEG_LIB_VERSION" redefined
> > #define JPEG_LIB_VERSION 80 /* Compatibility version 8.0 */
> > ^
> > In file included from jpeg/jinclude.h:20:0,
> > from jpeg/transupp.c:20:
> > /usr/include/x86_64-linux-gnu/jconfig.h:5:0: note: this is the location of
> the previous definition
> > #define JPEG_LIB_VERSION 62
> > ^
> > CC filter.o
> > CC op.o
> > CC readers.o
> > CC rd/read-jpeg.o
> > LD exiftran
> > jpeg/transupp.o: In function `jtransform_request_workspace':
> > /«PKGBUILDDIR»/jpeg/transupp.c:892: undefined reference to
> `jpeg_core_output_dimensions'
> > collect2: error: ld returned 1 exit status
> > make[2]: *** [exiftran] Error 1
> > mk/Compile.mk:83: recipe for target 'exiftran' failed
> > make[2]: Leaving directory '/«PKGBUILDDIR»'
> > make[1]: *** [override_dh_auto_build] Error 2
> > debian/rules:7: recipe for target 'override_dh_auto_build' failed
> > make[1]: Leaving directory '/«PKGBUILDDIR»'
> > make: *** [build] Error 2
> > debian/rules:4: recipe for target 'build' failed
> > dpkg-buildpackage: error: debian/rules build gave error exit status 2
I can now reproduce it. On my system libjpeg was provided by libjpeg8-dev,
after installing libjpeg-dev from libjpeg-turbo I can reproduce the bug.
I'm adding the libjpeg-turbo maintainers to CC; is there a reason
jpeg_core_output_dimensions is not available in -turbo? Shall I use
libjpeg8-dev instead?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
