Your message dated Sat, 26 Jul 2014 16:41:19 +0200
with message-id <53d3be0f.7090...@googlemail.com>
and subject line Re: Bug#746879: libphash: ftbfs with GCC-4.9
has caused the Debian Bug report #746879,
regarding libphash: ftbfs with GCC-4.9
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 ow...@bugs.debian.org
immediately.)


-- 
746879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libphash
Version: 0.9.4-1.4
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

The package fails to build in a test rebuild on at least amd64 with
gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The
severity of this report may be raised before the jessie release.

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/libphash_0.9.4-1.4_unstable_gcc49.log
The last lines of the build log are at the end of this report.

To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols
files.  For other C/C++ related build failures see the porting guide
at http://gcc.gnu.org/gcc-4.9/porting_to.html

[...]
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating examples/Makefile
config.status: creating pHash.pc
config.status: creating bindings/Makefile
config.status: creating bindings/java/Makefile
config.status: creating config.h
config.status: creating pHash-config.h
config.status: pHash-config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
make[1]: Leaving directory `/«PKGBUILDDIR»'
   dh_auto_build -a
make[1]: Entering directory `/«PKGBUILDDIR»'
make  all-recursive
make[2]: Entering directory `/«PKGBUILDDIR»'
Making all in src
make[3]: Entering directory `/«PKGBUILDDIR»/src'
/bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-O2 -pthread -I/usr/local/include -I/usr/include/ffmpeg -Dcimg_use_jpeg 
-Dcimg_use_png  -D__STDC_CONSTANT_MACROS -ffast-math -O3 -c -o pHash.lo 
pHash.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -O2 -pthread 
-I/usr/local/include -I/usr/include/ffmpeg -Dcimg_use_jpeg -Dcimg_use_png 
-D__STDC_CONSTANT_MACROS -ffast-math -O3 -c pHash.cpp  -fPIC -DPIC -o 
.libs/pHash.o
In file included from pHash.cpp:25:0:
pHash.h:43:0: warning: "__STDC_CONSTANT_MACROS" redefined
 #define __STDC_CONSTANT_MACROS
 ^
<command-line>:0:0: note: this is the location of the previous definition
In file included from pHash.h:50:0,
                 from pHash.cpp:25:
/usr/include/CImg.h: In function 'cimg_library::CImg<T> 
cimg_library::CImg<T>::get_resize(int, int, int, int, int, unsigned int, float, 
float, float, float) const [with T = float]':
/usr/include/CImg.h:20807:5: error: insn does not satisfy its constraints:
     }
     ^
(insn 641 195 196 48 (set (reg:DI 21 xmm0)
        (reg:DI 0 ax)) 89 {*movdi_internal}
     (nil))
/usr/include/CImg.h:20807:5: internal compiler error: in 
copyprop_hardreg_forward_1, at regcprop.c:775
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[3]: *** [pHash.lo] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/src'
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

--- End Message ---
--- Begin Message ---
Hi,

I can't reproduce this FTBFS in a current sid/amd64 chroot.

As the logs indicate that this was an 'internal compiler error', I assume gcc 4.9 got fixed in the meantime.

Therefore I'm closing this bug. If you can still reproduce it, please reopen the bug.

Best regards,
Andreas

--- End Message ---
_______________________________________________
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Reply via email to