Bluemerlin, the package libatomic-ops has a challenging package failure that can be looked at. A log of the failure I got when building it can be seen here.
The description for this package is:
Libatomic-ops implements a large collection of operations, each one of which is a combination of an (optional) atomic memory operation, and a memory barrier. It also implements associated feature-test macros that determine whether a particular operation is available on the current target hardware (either directly or by synthesis). Libatomic-ops attempts to replace various existing files with similar goals, since they usually do not handle differences in memory barrier styles with sufficient generality.
The error is:
gcc -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DNDEBUG -c atomic_ops_stack.c
/tmp/ccSYadB5.s: Assembler messages:
/tmp/ccSYadB5.s:181: Error: selected processor does not support ARM mode `ldrexd r2,[r0]'
/tmp/ccSYadB5.s:192: Error: selected processor does not support ARM mode `strexd r3,r6,[r0]'
make: *** [atomic_ops_stack.o] Error 1
It's unclear to me whether the compiler itself is generating bogus assembly code or there are inline assembly statements or something that is causing this error.
I believe the package may believe it's being compiled on an armv7 armhf system and we need to tweak it to use what assembly code that might be used on an armv5 armel system. But this is just a wild guess on my part what a fix might be.
It would be REALLY useful if you could come up with whatever changes are needed to get this package working.