Boost C++ Libraries: Ticket #12551: Building boost on arm64 causes error: unknown directive https://svn.boost.org/trac10/ticket/12551 <blockquote> <p> "clang++" -x assembler-with-cpp -O3 -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_STATIC_LINK=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/clang-linux-3.8.0/release/abi-aapcs/architecture-arm/link-static/target-os-android/threading-multi/asm/jump_arm64_aapcs_elf_gas.o" "libs/context/src/asm/jump_arm64_aapcs_elf_gas.S" </p> </blockquote> <p> ...failed clang-linux.compile.asm bin.v2/libs/context/build/clang-linux-3.8.0/release/abi-aapcs/architecture-arm/link-static/target-os-android/threading-multi/asm/jump_arm64_aapcs_elf_gas.o... clang-linux.compile.asm bin.v2/libs/context/build/clang-linux-3.8.0/release/abi-aapcs/architecture-arm/link-static/target-os-android/threading-multi/asm/ontop_arm64_aapcs_elf_gas.o libs/context/src/asm/ontop_arm64_aapcs_elf_gas.S:40:1: error: unknown directive .cpu generic+fp+simd </p> <p> This happens when trying to run the boost build on arm64. I don't have this issue for arm7 architecture. Is there a work around for this or a potential fix? </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/12551 Trac 1.4.3 edaskel@… Tue, 08 Nov 2016 22:37:29 GMT component changed https://svn.boost.org/trac10/ticket/12551#comment:1 https://svn.boost.org/trac10/ticket/12551#comment:1 <ul> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">Building Boost</span> </li> </ul> Ticket Kohei Takahashi Fri, 18 Nov 2016 10:42:58 GMT component changed; owner set https://svn.boost.org/trac10/ticket/12551#comment:2 https://svn.boost.org/trac10/ticket/12551#comment:2 <ul> <li><strong>owner</strong> set to <span class="trac-author">olli</span> </li> <li><strong>component</strong> <span class="trac-field-old">Building Boost</span> → <span class="trac-field-new">context</span> </li> </ul> Ticket olli Sat, 19 Nov 2016 11:15:17 GMT <link>https://svn.boost.org/trac10/ticket/12551#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/12551#comment:3</guid> <description> <p> compiles fine for AArch64 (APM X-Gene Mustang board) with gcc 4.8.4<br /> </p> <p> might be a problem of clang </p> </description> <category>Ticket</category> </item> <item> <dc:creator>olli</dc:creator> <pubDate>Mon, 05 Dec 2016 08:16:24 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/12551#comment:4 https://svn.boost.org/trac10/ticket/12551#comment:4 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> Ticket anonymous Tue, 20 Dec 2016 21:59:23 GMT <link>https://svn.boost.org/trac10/ticket/12551#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/12551#comment:5</guid> <description> <p> This is happening to me too with the android NDK installed by android studio, ie: I get an 'unrecognized directive .code' from the assembler when building arm64, for jump, move and ontop. </p> <p> I get this is a clang issue, but it would be VERY convenient if this code could be used as-is with the android NDK! </p> <p> Just commenting out the .cpu directive allows the code to build, although I haven't tried to run it on an emulator or anything yet. </p> <p> Should it be OK to comment this out? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>anonymous</dc:creator> <pubDate>Wed, 21 Dec 2016 16:56:00 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/12551#comment:6 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/12551#comment:6</guid> <description> <p> directive .code is no longer contained in the files (1.64) </p> </description> <category>Ticket</category> </item> </channel> </rss>