The impact of BROKEN_CLANG_ATOMICS is that fallback code using thread locking is used instead of the atomics calls. Cheers, Richard On Tue, 20 Dec 2022 14:11:36 +0100, Samiya Khanum via openssl-users wrote: > > Hi, > > After upgrading openssl to 3.0.7 from 1.1.1 , I see below errors. > > libcrypto.so: undefined reference to `__atomic_is_lock_free' > libcrypto.so: undefined reference to `__atomic_fetch_or_8' > libcrypto.so: undefined reference to `__atomic_load_8' > libcrypto.so: undefined reference to `__atomic_fetch_add_8' > I tried this patch, still seeing the same errors . > Prevent Clang from emitting atomic libcalls by xtkoba · Pull Request #16584 · openssl/openssl · > GitHub > > If we define "-DBROKEN_CLANG_ATOMICS" , it works. What is the impact If we define " > BROKEN_CLANG_ATOMICS". > > Can someone please suggest the correct way? > > Thanks & Regards, > Samiya khanum > > This electronic communication and the information and any files transmitted with it, or attached > to it, are confidential and are intended solely for the use of the individual or entity to whom it > is addressed and may contain information that is confidential, legally privileged, protected by > privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended > recipient or the person responsible for delivering the e-mail to the intended recipient, you are > hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or > copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return > the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. > -- Richard Levitte levitte@xxxxxxxxxxx OpenSSL Project http://www.openssl.org/~levitte/
