I'm interested in this, too. I disabled fenced blocking when I upgraded to 1.44 (platform is m68k-coldfire). Thus far I didn't notice any problems. I'd like to know what exactly this fenced blocking does and whether it is safe to disable or not. Regards On 11/09/2010 01:37 PM, Igor R wrote:

Hello,

I'm trying to cross-compile my project for Android (Win, cygwin, crystax-ndk). The linker emits the following error: ../asio/detail/gcc_fenced_block.hpp:41: undefined reference to `__sync_lock_test_and_set_4'

I understand that in 1.44 I can disable this "fenced-block" by defining BOOST_ASIO_DISABLE_FENCED_BLOCK, but I'm not sure it's safe to do this. IUUC, __sync_lock_test_and_set gcc function is unavailable for some older arm-based platforms, but should be available for the newer ones, shouldn't it? So maybe I have to define some compiler flag to enable it? I'd appreciate any idea.

Thanks. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- Dipl.-Ing. (FH) Andreas Wehrmann Software Development -------------------------------------------------------------- Center Communication Systems GmbH A-1210 Wien, Ignaz-Köck-Straße 19 Sitz in Wien FN 796 88p, Firmenbuchgericht Wien www.centersystems.com Tel.: +43 (0) 190 199 - 3616 Mobile: +43 (0) 664 884 75916 Fax: +43 (0) 190 199 - 2110 E-Mail: a.wehrmann@centersystems.com