[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#725880: marked as done (gcc-4.8: ICE on armhf: in cond_exec_process_insns, at ifcvt.c:339)

Your message dated Mon, 05 May 2014 21:37:01 +0200
with message-id <5367E85D.3050109@debian.org>
and subject line Re: gcc-4.8: ICE on armhf: in cond_exec_process_insns, at ifcvt.c:339
has caused the Debian Bug report #725880,
regarding gcc-4.8: ICE on armhf: in cond_exec_process_insns, at ifcvt.c:339
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
725880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725880
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:vips
Version: 7.34.2-1
Severity: serious

Dear Maintainer,

vips fails to build on armhf. The build log says:

libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../libvips/include -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -pthread -fopenmp -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/orc-0.4 -I/usr/include/openslide -I/usr/include/libxml2 -I/usr/include/libpng12 -I/usr/include/libexif -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/include/freetype2 -I/usr/include/arm-linux-gnueabihf/libtiff5-alt -I/usr/include/OpenEXR -I/usr/include/ImageMagick -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c image.c  -fPIC -DPIC -o .libs/image.o
image.c: In function 'vips_image_new_temp_file':
image.c:1717:1: internal compiler error: in cond_exec_process_insns, at ifcvt.c:323
 }
 ^

Of course this is ultimately a bug in gcc-4.8. However, until the bug is fixed
in GCC, you may want to consider a workaround. For example, I was able to build
the problematic file with gcc-4.7.

Cheers,

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://www.dynare.org/sebastien
  `-      GPG Key: 4096R/381A7594

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
that should be fixed in testing and unstable at this time

--- End Message ---
Reply to: