Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-10-14 Thread Noel Grandin
On Wed, 13 Oct 2021 at 18:50, Luke Benes wrote: > I can successfully build LO on i686 with > LDFLAGS="-latomic" > > > external/clew/Library_clew.mk looks like a good example of stuff that adds library paths, see the gb_Library_add_libs command there

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-10-14 Thread Stephan Bergmann
On 13/10/2021 18:49, Luke Benes wrote: I can successfully build LO on i686 with LDFLAGS="-latomic" This is overkill. I think patch is needed for the cuckoo module that you added in https://cgit.freedesktop.org/libreoffice/core/commit/?id=3749d9af3745 for IA-32 clang. I attempted to do this but

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-10-13 Thread Luke Benes
Noel, I can successfully build LO on i686 with LDFLAGS="-latomic" This is overkill. I think patch is needed for the cuckoo module that you added in https://cgit.freedesktop.org/libreoffice/core/commit/?id=3749d9af3745 for IA-32 clang. I attempted to do this but I'm not family with how this

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-09-16 Thread Luke Benes
Rene, > Or clang needs -latomic and gcc not. Yes, it does. Looks like a known bug in clang: https://bugs.llvm.org/show_bug.cgi?id=45785 Building with "-DCMAKE_CXX_FLAGS=-latomic", resolves the undefined reference to `__atomic_load' and allows the build to complete successfully. However, it

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-09-15 Thread Rene Engelhard
Hi, Am 16.09.21 um 01:48 schrieb Luke Benes: > Thanks for helping me to try to reproduce this. I'm building with clang-14. > Are you building with gcc? Yes. gcc 10 (as of yet), as I wrote :) > I've confirmed that when I built libcuckoo from > https://github.com/efficient/libcuckoo with

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-09-15 Thread Luke Benes
Thanks for helping me to try to reproduce this. I'm building with clang-14. Are you building with gcc? I've confirmed that when I built libcuckoo from https://github.com/efficient/libcuckoo with clang, I get a similar failure to the initial failure. When I build it with gcc-11, the build is

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-09-15 Thread Rene Engelhard
Hi, Am 15.09.21 um 02:34 schrieb Luke Benes: > [DEP] LNK:Library/libsvllo.so > [LNK] Library/libsvllo.so > /usr/lib/gcc/i586-suse-linux/11/../../../../i586-suse-linux/bin/ld: > /core/workdir/CxxObject/svl/source/misc/sharedstringpool.o: in function > `libcuckoo::cuckoohash_map<_rtl_uString*,

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

2021-09-15 Thread Rene Engelhard
Hi, Am 15.09.21 um 02:34 schrieb Luke Benes: > undefined reference to `__atomic_load' Probably you need to add -latomic to the link command line... Regards, Rene

Build failure on x86 linux: undefined reference to `__atomic_load'

2021-09-14 Thread Luke Benes
Noel, After commit 3749d9af3745c0eaff7239e379578e4e2af89e9d tdf#130795 use concurrent hashmap in SharedStringPool On both OpenSUSE Tumbleweed and Arch 32, I see the build failure below. Would you like any additional debugging info? -Luke [DEP] LNK:Library/libsvllo.so [LNK]