I have just tried to build unixcw-2.3 on merkel.debian.org (another amd64
machine).
While the build log reports:
-
make[3]: Entering directory `/build/buildd/unixcw-2.3/src/cwlib'
if [ no = yes ]; then \
2006/11/25, Steve Langasek [EMAIL PROTECTED]:
This is also crap, and the test fails silently because you're not allowed
to
link objects into a .so on amd64 unless they're built with -fPIC, which is
enforced by the toolchain.
Guessing how to build shared objects on different platforms is a
Package: unixcw
Version: 2.2-15
Severity: serious
Justification: FTBFS on amd64, already has amd64 binaries in etch
Usertags: grid5000
Hi,
During a rebuild of all packages in etch, I discovered that your package
failed to build on amd64.
Relevant parts:
ln -sf unixcw
2006/11/24, Lucas Nussbaum [EMAIL PROTECTED]:
Package: unixcw
Version: 2.2-15
Severity: serious
Justification: FTBFS on amd64, already has amd64 binaries in etch
Usertags: grid5000
Hi,
During a rebuild of all packages in etch, I discovered that your package
failed to build on amd64.
On Fri, Nov 24, 2006 at 09:25:42PM +0100, Joop Stakenborg wrote:
Very weird. All architectures build fine, so why does amd64 fail?
libcw.so.0.0.0 seems to be created correctly.
Not in the log file that he cited, it doesn't.
make[3]: Entering directory /build/buildd/unixcw-2.3/src/cwlib'
if [
5 matches
Mail list logo
