Package: vip_7.12.5-2
Usertags: ftbfs-gcc-4.3

Hey Jay,

Your package fails to build with GCC 4.3.  Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning.  In GCC 4.3, the C++ header
dependencies have been cleaned up.  The advantage of this is that
programs will compile faster.  The downside is that you actually
need to directly #include everything you use (but you really should
do this anyway, otherwise your program won't work with any compiler
other than GCC).  There's some more information about this at
http://www.cyrius.com/journal/2007/05/10#gcc-4.3-include

You can reproduce this problem with gcc-snapshot from unstable.  Note
that Red Hat, Novell and Ubuntu have done some work getting packages
to build with GCC 4.3 so there might be patches floating around
somewhere.  I suggest you talk to your upstream.

> Automatic build of vips_7.12.5-2 on em64t by sbuild/amd64 0.53
...
> mkdir .libs
>  g++ -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
> -DPNG_NO_MMX_CODE -I/usr/include/libpng12 -I/usr/include/libexif 
> -I/usr/include/OpenEXR -I/usr/include/liboil-0.3 -g -Wall -O2 -c VImage.cc  
> -fPIC -DPIC -o .libs/VImage.o
> VImage.cc: In destructor 'vips::Vargv::~Vargv()':
> VImage.cc:350: error: 'strcmp' was not declared in this scope
> make[3]: *** [VImage.lo] Error 1
> make[3]: Leaving directory 
> `/build/tbm/vips-7.12.5/build-tree/vips-7.12.5/libsrcCC'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/tbm/vips-7.12.5/build-tree/vips-7.12.5'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/tbm/vips-7.12.5/build-tree/vips-7.12.5'
> make: *** [debian/stamp-makefile-build] Error 2

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to