for me compiling it there was only problem with 'ar crT' where T is not supported by maemo ar (neither busybox or gnu). It does seem to hang with no activity whatsoever(except cpu) whether in monitor/bleeding/stock after compiling without this flag (also without providing target which tells immediately its buggy). WPSCrack seems to send 00000000 packets endlessly, which maybe result of two errors (scapy/python-crypto got many packages suggested, some not available for maemo, and most non-optified it would seem) that pop up. Considering multitude of bugs being reported from standard distro users we might have better chances once the main probs are addressed by the authors. Looking forward to it anyway
EDIT: the above is my experience with 1.2, 1.0 from above posts is just as borked, maybe initial release will be luckier though that's doubtful at best
lack of T is probably not the cause of problem. From only man page around I found for ar that contained this flag (MacOS ouch):
-T Select and/or name archive members using only the first fifteen characters of the archive mem-ber member
ber or command line file name. The historic archive format had sixteen bytes for the name, but
some historic archiver and loader implementations were unable to handle names that used the
entire space. This means that file names that are not unique in their first fifteen characters
can subsequently be confused. A warning message is printed to the standard error output if any
file names are truncated. (See ar(5) for more information.)

Doesn't look as if it would make difference (as if binary compiling wouldn't be enough of an indicator), maybe pcap 0.8 is too old (pcap-dev 1.0 conflicts though for me)