Package: bazaar Version: 1.4.2-2 Followup-For: Bug #334320 Hi,
I just built 1.4.2-2 on my IA64 machine and it does build OK. The relevant part where the buildd failed looks like ======= TESTING: id-tagging-defaults ======= Test 1: id-tagging-defaults Test 1: PASS baz(30725): unaligned access to 0x60000fffffb7191e, ip=0x40000000001095f0 baz(30725): unaligned access to 0x60000fffffb71922, ip=0x40000000001095f0 baz(30725): unaligned access to 0x60000fffffb71926, ip=0x40000000001095f0 baz(30725): unaligned access to 0x60000fffffb7192a, ip=0x40000000001095f0 Having a look [EMAIL PROTECTED]:/usr/lib/debug/usr/bin$ addr2line - e ./baz 40000000001095f0 /tmp/bazaar-1.4.2/src/hackerlab/hash/sha1.c:370 which dereferences the buffer in a sha1_context struct. I've seen problems with stack alignment and gcc 4 on IA64 and I'd suggest this is similar. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22605 The two possible solutions I can see is that you either change sha1_process_blocks to not assume the input is aligned or to change sha1_process_blocks so it is defined as only taking aligned input. Either is messy unfortunatley. caballero is an Itanium 1 right? That has stricter alignment requirements than Itanium 2. I'm not sure if this could cause the problem on the other architectures too. -i -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-rc4-gbb7e257e Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages bazaar depends on: ii diff 2.8.1-11 File comparison utilities ii gawk 1:3.1.4-2 GNU awk, a pattern scanning and pr ii libc6.1 2.3.5-6 GNU C Library: Shared libraries an ii libgpgme11 1.1.0-1 GPGME - GnuPG Made Easy ii libneon24 0.24.7.dfsg-2 An HTTP and WebDAV client library ii libssl0.9.7 0.9.7g-2 SSL shared libraries ii patch 2.5.9-2 Apply a diff file to an original bazaar recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
