search for: libatomic

Hi renato, 1. The command above is followed by the guide[ HowToCrossCompileLLVM.rst ] and I specify some path(ex. <path-to-host-bin>). 2. The including x86_64 libraries is added because of some missing libraries(ex. "error: Host compiler appears to require libatomic, but cannot find it"). As I have found that the bugs needed to dealt with is some ARM-dependent libraries, I cannot download them on Ubuntu14, could you share them or some available links? Thanks very much! Best, Liyang 2016-04-25 18:33 GMT+08:00 Renato Golin <renato.golin at linaro.org&...

...switch to an unsupported GCC like v4.6.4 to build LLVM v3.8-rc3 with cmake I get the following: ... -- Looking for __atomic_fetch_add_4 in atomic -- Looking for __atomic_fetch_add_4 in atomic - not found CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:296 (include) CMakeLists.txt:407 (include) -- Configuring incomplete, errors occurred! See also "/home/wearefam/src/llvm-toolchain/llvm-build/CMakeFiles/CMakeOutput.log". See also "/home/wearefam/sr...

...on is AppleClang 4.1.0.4211166 -- The CXX compiler identification is AppleClang 4.1.0.4211166 [...] -- Looking for __atomic_fetch_add_4 in atomic -- Looking for __atomic_fetch_add_4 in atomic - not found CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:291 (include) CMakeLists.txt:360 (include) How is libatomic supposed to be installed on OS X? (perhaps it's somewhat of a newbie question - I'm not a OS X user...) Thank you, Antoine.

On Dec 11, 2016, at 3:33 AM, Eric Fiselier via llvm-dev <llvm-dev at lists.llvm.org> wrote: > So it seems that libatomic went missing between build #1379 and #1380, so I don't think this is related to the -std=c++11 failure. Instead it seems likely that the compile test for -std=c++11 is failing due to mis-configuring -latomic. > > Can you confirm the bot has libatomic installed? You shouldn't need it...

...d > writes, but not writes emitted by other compilers. This would mean that > linking object files with atomics might break their atomicity. I'm not > sure we want to allow that. Maybe we can do that only if the > synchronization scope allows it or something? > GCC does it in libatomic: https://github.com/gcc-mirror/gcc/tree/master/libatomic They agree on the function name, so AFAIK either runtime allows this to work properly: the compiler just emits a call to the function, and one of the runtimes has to be present. -------------- next part -------------- An HTML attachment was...

So it seems that libatomic went missing between build #1379 and #1380, so I don't think this is related to the -std=c++11 failure. Instead it seems likely that the compile test for -std=c++11 is failing due to mis-configuring -latomic. Can you confirm the bot has libatomic installed? -------------- next part -----------...

...-x86_64-linux-fuzzer> to make it green. The problem remains, of course. :( On Sun, Dec 11, 2016 at 7:23 AM, James Knight <jyknight at google.com> wrote: > On Dec 11, 2016, at 3:33 AM, Eric Fiselier via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > So it seems that libatomic went missing between build #1379 and #1380, > so I don't think this is related to the -std=c++11 failure. Instead it > seems likely that the compile test for -std=c++11 is failing due to > mis-configuring -latomic. > > > > Can you confirm the bot has libatomic installed? &g...

...l7_4.2.x86_64.rpm e62f707dcfe7d24bf106d593589b5b33fec977c8138a0a28cbaa1ac3538aa910 libasan-static-4.8.5-16.el7_4.2.i686.rpm 022cc384ba0b92554d9d00fc4eb346e8d764497adf7f16907b36354a323b1462 libasan-static-4.8.5-16.el7_4.2.x86_64.rpm 7e102fd7e98cc413b3b9c10595407c004dc8b61cd804a4428962f3068fa24ef6 libatomic-4.8.5-16.el7_4.2.i686.rpm 1392c5302e9bc7ae7f9c2750700d6c8944c4e5b631290520833a971e36104bed libatomic-4.8.5-16.el7_4.2.x86_64.rpm 75818d083de77affb85b1db921ac3ef8140dec7a1560b9505f710506e22f9e18 libatomic-static-4.8.5-16.el7_4.2.i686.rpm 9addc48203b5a56bd9c5fe800028f92d323f453bfb0b739da48ada5f4dbd...

...l7_6.2.x86_64.rpm 90b931d343aacc05679bcb364abaa4e81aadb109432df7dec57011152dc28e75 libasan-static-4.8.5-36.el7_6.2.i686.rpm 8a474ea77ad996a57261226b2bfe9db46e5387ed879d355794c5788681640cf5 libasan-static-4.8.5-36.el7_6.2.x86_64.rpm f0a454fa2b64d4db9f3e6e36aa520ab7a0eab903543012189f7f4094a2b6a856 libatomic-4.8.5-36.el7_6.2.i686.rpm 8d16d345c51f3709c45c2fd03bc428a9b402fc40bdc07b4a913ec09b2f297a66 libatomic-4.8.5-36.el7_6.2.x86_64.rpm 866968c2ee28b8eacb0fa3ce99b2a9217e7c8f289cf984531391d8f4e43f4a39 libatomic-static-4.8.5-36.el7_6.2.i686.rpm 71971abdddb5f1ba218ba14b74b5af9839957a784fa66609c5f97b862935...

...l7_4.1.x86_64.rpm dcaaf63d9e595e4adc604f30bd1495490e72487cd970496c77bc5c99e1127a95 libasan-static-4.8.5-16.el7_4.1.i686.rpm cc62110941aaa47c0bbef909f67de5dcaa28216eaa4eef1ab739f2cd86ffc115 libasan-static-4.8.5-16.el7_4.1.x86_64.rpm 6a2ecef93d9147d25518a87ce6eadf5194887727cae415469c1211ae6d08f508 libatomic-4.8.5-16.el7_4.1.i686.rpm e2d96fe99f8b0349ce9f608b4741ff1b3907663d56f3666b9bbac3e701d0e254 libatomic-4.8.5-16.el7_4.1.x86_64.rpm 27110ff06299571e85a728e6525029540a1aa4900b31a2b72be02766085e9f82 libatomic-static-4.8.5-16.el7_4.1.i686.rpm bee90d1e8deba43fbfab9a53212cbfbde54d63b49fbf000b07edc15e10d7...

...l7_6.1.x86_64.rpm b82653f894c2e4ccf2d6041e18f6e6f5079ab719731b3346a76d148d2108c172 libasan-static-4.8.5-36.el7_6.1.i686.rpm e151a3c1253a69525a46a5fb725df848795b1b8a341d2b89a02efd799bf3e1dd libasan-static-4.8.5-36.el7_6.1.x86_64.rpm 4848eac686c9d20a0e07630409b5fca5048dcf0e5e7686f67684ebfeaf4aab8e libatomic-4.8.5-36.el7_6.1.i686.rpm 99f808a165fe4770d22880b84d6074d6710b5cd7a7f67f66b7533dcdd8ee187b libatomic-4.8.5-36.el7_6.1.x86_64.rpm 161b96eb063f4532f62509c603a224f3624acc23e9fa9d4db55e50e757072d16 libatomic-static-4.8.5-36.el7_6.1.i686.rpm a1a0f9beb24784b3dd01aab1a220b5e335d627028282fadfbf5812595455...

...l7_5.1.x86_64.rpm 77c231756853658ade09c8cc29ac747e53ef8fd576b0532e6bec6832df1271eb libasan-static-4.8.5-28.el7_5.1.i686.rpm bc79885f34aa659544240ee2644a6f77e9e04bbe6b3e654d61bcea82b19dedeb libasan-static-4.8.5-28.el7_5.1.x86_64.rpm 00429f7761864887066449da1b541ee14fce467f2eabb2202bc8fa530e11896f libatomic-4.8.5-28.el7_5.1.i686.rpm 6e7183c4b4cedaf79d623d0085f3cebec1c1bbdfabf2153485961e98e18a0626 libatomic-4.8.5-28.el7_5.1.x86_64.rpm a5ab8bf9158d38482d20eb254ea12d9837ffaaf476914a226ffd91146935c578 libatomic-static-4.8.5-28.el7_5.1.i686.rpm 7ed163ad7585ee3639e24489ddfdef6b6c55ad1b6355a2c5c2674593885d...

....el7_0.x86_64.rpm beadf9ad5fcfe7eeaa3f2c9c5e08f5c347a2857c543f0b2e88096801b6dea093 libasan-static-4.8.2-16.2.el7_0.i686.rpm ef3914fcfc6f03a6cca23b2e1606f5446740d1b6a5315f35946eba87cc5f1b5e libasan-static-4.8.2-16.2.el7_0.x86_64.rpm e7ca0661b66866254c4a0de162b6fe099493b0aaaa7c27d46f99d3e011211ed9 libatomic-4.8.2-16.2.el7_0.i686.rpm c1e02d1f800984a7e8f24f66666a1b81e75661fd19c22b8c9c1bf618c4ada01f libatomic-4.8.2-16.2.el7_0.x86_64.rpm d2e3955b8ecb2a288be007fea870c372e6448319d0342ec11d555e2e3766be35 libatomic-static-4.8.2-16.2.el7_0.i686.rpm 29a8904a70483ec734cf2828b17bbdce82035b2c5cc84a55e84c445e5cb9...

...quot; \ ../llvm Firstly, I encounter the known problem with __atomic_load_8. arm-cortex-m{3,4} most probably doesn't support 64bit atomic read/write, but as long as I don't use it, changing the line in CheckAtomic.cmake: message(FATAL_ERROR "Host compiler appears to require libatomic, but cannot find it.") to: message(WARNING "Host compiler appears to require libatomic, but cannot find it.") could push the things further. But then I encounter that error: -- Targeting ARM CMake Error at /home/kacper/Workspace/LLVMProject/libcxxabi/CMakeLists.txt:...

...reverting it does not help. Maybe an update in Ubuntu 14.04 broke this? On Sat, Dec 10, 2016 at 3:35 PM, Eric Fiselier <eric at efcs.ca> wrote: > I can't reproduce right away. I wonder if the check for the -std=c++11 > flag is failing due to the earlier error about failing to find libatomic. > > When these bots start failing? > > /Eric > > On Fri, Dec 9, 2016 at 10:18 PM, Kostya Serebryany via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> several hours ago one of the bots that does a bootstrap started to fail >> (http://lab.llvm.org:801...

...rrata and Enhancement Advisory 2017:2848 Upstream details at : https://access.redhat.com/errata/RHEA-2017:2848 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 958f6406a183678e59a9062ffb11f4f343ea4c6b72711ee24ff3b8c219f3793c libatomic-7.1.1-2.3.1.el6_9.i686.rpm 2ffab6a8f704d18a5af1aa31d373a08f78d39523223378fbc745ae01ade02a8a libcilkrts-7.1.1-2.3.1.el6_9.i686.rpm d354ef0dd5200833aded9867772cb16a3e93d4865d9104c63d7a321df0afb19c libgfortran4-7.1.1-2.3.1.el6_9.i686.rpm 908d15646f9a5c38f3383ef953cbc51d46aebea595be5bd42cbc17ac11d6a9...

...OS Errata and Bugfix Advisory 2018:1363 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1363 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 323ad8d5df9a986714d005ef68522add594e30649126df621a17bb4c9b8408f8 libatomic-7.1.1-2.4.1.el6_9.i686.rpm 5a08cc9e5b374e7c7f4bbf8f7a52d3aad149b9e1c0b52f26da74bab204f81819 libcilkrts-7.1.1-2.4.1.el6_9.i686.rpm e655f830b1cb725f1e16d29ab9523aa05e35652ab0a97f941c98c06f81ae1501 libgfortran4-7.1.1-2.4.1.el6_9.i686.rpm 248c681d393d114567ad1b52f62b3f9bebd4c6f739a940ff58b21a914d9588...

...OS Errata and Bugfix Advisory 2018:2893 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2893 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b16e88c5efb2d60a55d5d33d0ba827c9dfdb08060287f1f5c1cb38f0ae6dab55 libatomic-8.2.1-1.3.1.el6_10.i686.rpm d8be6386d411cf8ca0a0f5c82e2995a41004a4c3dc84a8221268abc030afc4dd libgfortran4-8.2.1-1.3.1.el6_10.i686.rpm 24768d8707729dc785de4e500558e2e88de3b1b01e1586351508ebde0b121496 libgfortran5-8.2.1-1.3.1.el6_10.i686.rpm ec52cf5268e00779b0736fb0d14bb701dcb103dc287106e3c4c30d26a...

...libitm.so.1.0.0 gcj-4.9.0-15 libitm.spec go libltdl.so.7 i386 libltdl.so.7.3.0 lib-gnu-awt-xlib.so liblzma.so.5 lib-gnu-awt-xlib.so.15 liblzma.so.5.0.5 lib-gnu-awt-xlib.so.15.0.0 libmpc.so.3 libatomic.a libmpc.so.3.0.0 libatomic.la libmpfr.so.4 libatomic.so libmpfr.so.4.1.2 libatomic.so.1 libncurses.so.5 libatomic.so.1.1.0 libncurses.so.5.9 libaugeas.so libnetsnmp.so libaugeas.so.0 libnetsnmp.s...

...-g++ \ -DCMAKE_ASM_COMPILER=${MYGNUARM_ROOT}/bin/arm-none-eabi-as \ ../llvm ... -- Looking for __atomic_load_8 in atomic -- Looking for __atomic_load_8 in atomic - not found CMake Error at cmake/modules/CheckAtomic.cmake:74 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:350 (include) CMakeLists.txt:585 (include) arm-none-eabi toolchain doesn't contain libatomic, but I need to build compiler_rt using this tool to get the runtime for ARM, so it's confusing. Or building compi...