Your message dated Sun, 25 Aug 2013 18:42:52 +0200
with message-id <[email protected]>
and subject line Re: Bug#701246: biosig4c++: ftbfs with GCC-4.8
has caused the Debian Bug report #701246,
regarding biosig4c++: ftbfs with GCC-4.8
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 [email protected]
immediately.)
--
701246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701246
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:biosig4c++
Version: 1.3.0-2
Severity: important
Tags: sid jessie
User: [email protected]
Usertags: ftbfs-gcc-4.8
The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.
cstdlib:174:20: error: declaration of C function 'long long int std::abs(long
long int)' conflicts with
The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/biosig4c++_1.3.0-2_unstable_gcc48.log
The last lines of the build log are at the end of this report.
To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev
The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.
[...]
: # Assure additional interesting to us pieces are built
make LIBEXT=so libbiosig.so mex4o biosig4python
/usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:548: UserWarning:
Specified path /usr/local/include/python2.7 is invalid.
warnings.warn('Specified path %s is invalid.' % d)
/usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:548: UserWarning:
Specified path /usr/include/suitesparse/python2.7 is invalid.
warnings.warn('Specified path %s is invalid.' % d)
make[2]: Entering directory `/build/biosig4c++-VpUeNl/biosig4c++-1.3.0'
make[2]: `libbiosig.so' is up to date.
make -C mex DEFINES="-D=WITH_ZLIB -D=__4HAERTEL__ -D=WITH_FAMOS
-D=WITH_CHOLMOD -D=WITHOUT_NETWORK"
CROSS=/usr/local/src/mxe/usr/bin/i686-pc-mingw32
CROSS64=/usr/local/src/mce-w64/usr/bin/i686-pc-mingw32 LDLIBS="-lz -lcholmod"
OCTAVE_VERSION= mex4o
make[3]: Entering directory `/build/biosig4c++-VpUeNl/biosig4c++-1.3.0/mex'
mkoctfile -D=WITH_ZLIB -D=__4HAERTEL__ -D=WITH_FAMOS -D=WITH_CHOLMOD
-D=WITHOUT_NETWORK -v -g --mex mexSLOAD.cpp -L.. -lbiosig -lz -lcholmod
g++ -c -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-3.6.2/octave/..
-I/usr/include/octave-3.6.2/octave -I/usr/include/mpi -I/usr/include/freetype2
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -fopenmp -g -I. -D=WITH_ZLIB -D=__4HAERTEL__
-D=WITH_FAMOS -D=WITH_CHOLMOD -D=WITHOUT_NETWORK mexSLOAD.cpp -o mexSLOAD.o
In file included from /usr/include/octave-3.6.2/octave/mexproto.h:52:0,
from /usr/include/octave-3.6.2/octave/mex.h:77,
from mexSLOAD.cpp:15:
/usr/include/c++/4.8/cstdlib: In function 'long long int std::abs(long long
int)':
/usr/include/c++/4.8/cstdlib:174:20: error: declaration of C function 'long
long int std::abs(long long int)' conflicts with
abs(long long __x) { return __builtin_llabs (__x); }
^
/usr/include/c++/4.8/cstdlib:166:3: error: previous declaration 'long int
std::abs(long int)' here
abs(long __i) { return __builtin_labs(__i); }
^
/usr/include/c++/4.8/cstdlib: In function '__int128 std::abs(__int128)':
/usr/include/c++/4.8/cstdlib:179:19: error: declaration of C function '__int128
std::abs(__int128)' conflicts with
abs(__int128 __x) { return __x >= 0 ? __x : -__x; }
^
/usr/include/c++/4.8/cstdlib:174:3: error: previous declaration 'long long int
std::abs(long long int)' here
abs(long long __x) { return __builtin_llabs (__x); }
^
/usr/include/c++/4.8/cstdlib:179:19: error: declaration of C function '__int128
std::abs(__int128)' conflicts with
abs(__int128 __x) { return __x >= 0 ? __x : -__x; }
^
/usr/include/c++/4.8/cstdlib:166:3: error: previous declaration 'long int
std::abs(long int)' here
abs(long __i) { return __builtin_labs(__i); }
^
mexSLOAD.cpp: In function 'void mexFunction(int, mxArray**, int, const
mxArray**)':
mexSLOAD.cpp:458:149: warning: format '%i' expects argument of type 'int', but
argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
fprintf(stderr,"\n[129] SREAD/SCLOSE on %s successful [%i,%i] [%Li,%i]
%i.\n",hdr->FileName,hdr->data.size[0],hdr->data.size[1],hdr->NRec,count,NS);
^
mexSLOAD.cpp:458:149: warning: format '%i' expects argument of type 'int', but
argument 5 has type 'size_t {aka long unsigned int}' [-Wformat=]
mexSLOAD.cpp:458:149: warning: format '%Li' expects argument of type 'long long
int', but argument 6 has type 'nrec_t {aka long int}' [-Wformat=]
mexSLOAD.cpp:458:149: warning: format '%i' expects argument of type 'int', but
argument 7 has type 'size_t {aka long unsigned int}' [-Wformat=]
make[3]: *** [mexSLOAD.mex] Error 1
make[3]: Leaving directory `/build/biosig4c++-VpUeNl/biosig4c++-1.3.0/mex'
make[2]: *** [mex4o] Error 2
make[2]: Leaving directory `/build/biosig4c++-VpUeNl/biosig4c++-1.3.0'
make[1]: *** [override_dh_auto_build] Error 2
make: *** [build-arch] Error 2
make[1]: Leaving directory `/build/biosig4c++-VpUeNl/biosig4c++-1.3.0'
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
On 2013-08-11 01:05:48, Andreas Moog wrote:
> I can confirm that biosig4c++ does no longer FTBFS in unstable, please
> see the attached build log.
I can confirm that too. Thus I'm closing this bug.
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
--- End Message ---
