Hi Marcel >Hi Andy, > >> using gcc atomic buildins breaks support for older gcc/platforms. >> >> src/bluetoothd-adapter.o: In function `btd_adapter_unref': >> adapter.c:(.text+0x63f8): undefined reference to `__sync_sub_and_fetch_4' >> >> I suggest to use glib g_atomic_* group of functions. >> They fall back to traditional locking if buildins are not available. > >the GLib atomic API functions are not really stable. The GLib people for >some reason decided to break their own API/ABI guarantee. So we moved >away from using them. And I have no intention to get back to them. > >Long term, we are moving away from GLib and want to switch to ELL. So >that means gcc atomics are required. My advise would be to get a modern >platform and not rely on workarounds. > >Regards > >Marcel many thanks for your answer. unfortunately a modern platform is not an option for me, hopefully changes some day. so I will maintain another local patch (yieha) :P ELL? sounds interesting... will have a look at it. regards andy-- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
