tags 323815 patch thanks Hello Tim,
> Other had report that recompiling fixed the issue, so the working theory
> was that it was a glitch in the toolchain that has since been
> resolved.
I tried the solution of Aaron Maxwell (it's in the bug logs) by adding
-m64 to CFLAGS and CXXFLAGS. And indeed, he is right, compiling bzflag
with -m64 solves the problem, I can happily kill other tanks.
> Can you try rebuilding from the sources and see if that fixes it?
Merely rebuilding does not suffice, the -m64 switch is what does the
trick. I have also tried it with GCC 4.1, which yields the same
behaviour (-m64 works, without -m64 doesn't)
I do not quite understand this behavior. But as a workaround, you
could run configure with the variables set as above for the amd64
architecture. It's not very nice, though.
You have a case distinction in debian/rules anyway, so adding the
amd64-case would not be much work. (patch attached, just in case you
want it)
I wonder if other 64bit platforms are affected, though. I can't test
it.
> Pay special attention to any changes in the libraries in use by the
> bzflag binaries.
ldd gives the exactly same list for the binary in your package and my
binaries (for the working and non-working ones).
If you want me to test other things, I'm happy to try them out.
René
--- bzflag-2.0.6.20060412/debian/rules 2006-04-10 06:08:54.000000000 +0200
+++ /home/rvb/rules 2006-04-17 21:17:29.000000000 +0200
@@ -20,6 +20,7 @@
else
case "$(DEB_BUILD_ARCH)" in \
i386) ./configure --prefix=/usr --host=i486-pc-linux-gnu ;; \
+ amd64) CFLAGS=-m64 CXXFLAGS=-m64 ./configure --prefix=/usr ;; \
*) ./configure --prefix=/usr ;; \
esac
endif
pgpfA1MTidSnY.pgp
Description: PGP signature
