[Android-tools-devel] Bug#769251: android-platform-build: FTBFS in jessie/i386: libutils.so: undefined reference to `android_atomic_or'

[Lucas Nussbaum]

Source: android-platform-build
Version: 21-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o zipalign ZipAlign.o ZipEntry.o ZipFile.o -lz -lpthread -L/usr/lib/android -llog -lutils -lcutils 
> /usr/lib/android/libutils.so: undefined reference to `android_atomic_or'
> /usr/lib/android/libutils.so: undefined reference to `android_atomic_dec'
> /usr/lib/android/libutils.so: undefined reference to `android_atomic_inc'
> /usr/lib/android/libutils.so: undefined reference to `android_atomic_release_cas'
> /usr/lib/android/libutils.so: undefined reference to `android_atomic_add'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/11/12/android-platform-build_21-2_jessie-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.