Your message dated Wed, 28 Jun 2006 11:57:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in hoichess 0.4.3-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: hoichess
Version: 0.4.0-1
Severity: serious
Hello,
There was an error while trying to autobuild your package:
> bitboard.cc:0: error: CPU you selected does not support x86-64 instruction set
> bitboard.cc:0: error: CPU you selected does not support x86-64 instruction set
> g++-4.0 -E -W -Wall -O3 -march=i686 -MM -MT 'bench.o' bench.cc \
> | sed 's,\(bench\)\.o[ :]*,\1.o .deps/bench.d: ,g' >
> .deps/bench.d; \
> [ -s .deps/bench.d ] || rm -f .deps/bench.d
> bench.cc:0: error: CPU you selected does not support x86-64 instruction set
> bench.cc:0: error: CPU you selected does not support x86-64 instruction set
> g++-4.0 -W -Wall -O3 -march=i686 -c -o bench.o bench.cc
> bench.cc:1: error: CPU you selected does not support x86-64 instruction set
> bench.cc:1: error: CPU you selected does not support x86-64 instruction set
> make[2]: *** [bench.o] Error 1
> make[2]: Leaving directory `/build/buildd/hoichess-0.4.0/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/hoichess-0.4.0'
> make: *** [build-stamp] Error 2
Please do not use -march=i686 on an arch: any package, or make it arch:
i386 if it is not portable at all.
A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64&pkg=hoichess&ver=0.4.0-1
Best regards
Frederik Schueler
--- End Message ---
--- Begin Message ---
Source: hoichess
Source-Version: 0.4.3-1
The maintainer fixed this on his own in 0.4.1-1 (though it wasn't
uploaded until 0.4.3-1).
Cheers,
Matej
--- End Message ---
