gcc-4.2 cannot compile bind 9.5.0.P2 on i386

Bug #261831 reported by Ondřej Surý
4
Affects Status Importance Assigned to Milestone
bind9 (Debian)
Fix Released
Unknown
bind9 (Ubuntu)
Won't Fix
Undecided
Unassigned
gcc-4.2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gcc-4.2

On i386 (amd64 is fine) bind9 9.5.0.P2 (and higher) stops with:

/bin/bash /tmp/buildd/bind9-9.5.0.dfsg.P2/libtool --mode=compile gcc -I/tmp/buildd/bind9-9.5.0.dfsg.P2 -I. -Iinclude -I/tmp/buildd/bind9-9.5.0.dfsg.P2/lib/dns/include -I../../lib/dns/include -I/tmp/buildd/bind9-9.5.0.dfsg.P2/lib/isc/include -I../../lib/isc -I../../lib/isc/include -I../../lib/isc/unix/include -I../../lib/isc/pthreads/include -I../../lib/isc/x86_32/include -I/usr/include -D_REENTRANT -DUSE_MD5 -DOPENSSL -DGSSAPI -DUSE_ISC_SPNEGO -fno-strict-aliasing -O2 -I/usr/include/libxml2 -W -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wformat -Wpointer-arith -fno-strict-aliasing -c stats.c
 gcc -I/tmp/buildd/bind9-9.5.0.dfsg.P2 -I. -Iinclude -I/tmp/buildd/bind9-9.5.0.dfsg.P2/lib/dns/include -I../../lib/dns/include -I/tmp/buildd/bind9-9.5.0.dfsg.P2/lib/isc/include -I../../lib/isc -I../../lib/isc/include -I../../lib/isc/unix/include -I../../lib/isc/pthreads/include -I../../lib/isc/x86_32/include -I/usr/include -D_REENTRANT -DUSE_MD5 -DOPENSSL -DGSSAPI -DUSE_ISC_SPNEGO -fno-strict-aliasing -O2 -I/usr/include/libxml2 -W -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wformat -Wpointer-arith -fno-strict-aliasing -c stats.c -fPIC -DPIC -o .libs/stats.o
/tmp/ccPORbv2.s: Assembler messages:
/tmp/ccPORbv2.s:555: Error: suffix or operands invalid for `xadd'
/tmp/ccPORbv2.s:659: Error: suffix or operands invalid for `xadd'
make: *** [stats.lo] Error 1

Strange thing is that x86_64 and x86_32 share same configuration (lib/isc/x86_32/include/isc/atomic.h) on platforms where gcc is available (configure.in overrides platform in this case) and x86_64 compiles just fine.

I also have checked diff between P1 and P2 (P1 compiled fine some time ago) and I didn't discovered any changes which should affect this.

I am trying this in clean pbuilder environment (hardy, hardy-security and hardy-updates enabled).

gcc-4.2 version is:

gcc:
  Installed: 4:4.2.3-1ubuntu6
  Candidate: 4:4.2.3-1ubuntu6
  Version table:
 *** 4:4.2.3-1ubuntu6 0
        500 http://cz.archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     4:4.2.3-1ubuntu3 0
        500 http://cz.archive.ubuntu.com hardy/main Packages
root@howl:/# apt-cache policy gcc-4.2
gcc-4.2:
  Installed: 4.2.3-2ubuntu7
  Candidate: 4.2.3-2ubuntu7
  Version table:
 *** 4.2.3-2ubuntu7 0
        500 http://cz.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Matthias Klose (doko) wrote :

please attach the (compressed) preprocessed source (generated using -save-temps).

Changed in gcc-4.2:
status: New → Incomplete
Revision history for this message
Ondřej Surý (ondrej) wrote :

Attached.

I have one idea. Maybe the problem could be related to fact I am running i386 pbuilder chroot inside amd64 system.

So either there is some detection in Bind build process which mixes x86_32 and x86_64 together or there is some other bug.

Revision history for this message
Matthias Klose (doko) wrote :

do you set the personality to 32bit? wither configure schroot with this personality, or start the build prefixed with 'linux32'.

Revision history for this message
Ondřej Surý (ondrej) wrote :

It's really bug in bind9 build system, see debbug #515110

affects: bind (Ubuntu) → bind9 (Ubuntu)
Changed in gcc-4.2 (Ubuntu):
status: Incomplete → Invalid
Changed in bind9 (Debian):
status: Unknown → Won't Fix
Revision history for this message
LaMont Jones (lamont) wrote :

cross-compiling bind9 is not supported by the package at this time.

Please set the personality correctly to use a 32-bit pbuilder chroot on a 64-bit machine.

lamont

Changed in bind9 (Ubuntu):
status: New → Won't Fix
Changed in bind9 (Debian):
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.