# TI\_Arm\_Clang\_Compiler\_1.3.0 not passing initial compiler test

**URL:** https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759
**Category:** Usage
**Tags:** os:windows
**Created:** [May 30, 2022, 11:56am UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759 "2022-05-30T11:56:37Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Raisha](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/r/dec6dc/32.png) [@Raisha](https://discourse.cmake.org/u/Raisha)
#### Post date: [May 30, 2022, 11:56am UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759/1 "2022-05-30T11:56:37Z")

</div>

Hello,

I am trying to build using TI\_Arm\_Clang\_Compiler\_1.3.0 using cmake.  
The compiler test is failing at linking and the compiler is identified as Clang instead of TI.

**– The C compiler identification is Clang 12.0.1**

Do you know why the compiler is not detected properly ?

Error during compiler test is as below.

error: no input section is linked in  
warning: no suitable entry-point found; setting to 0  
error: errors encountered during linking; “a.out” not built

Thank you.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [May 30, 2022, 12:41pm UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759/2 "2022-05-30T12:41:55Z")

</div>

It may be that the compiler needs more specific detections. I don’t see support for this compiler in CMake at the moment. Is there somewhere someone can get a copy of it to play around with to add support (not sure who could do it; depends on free time mostly). MRs welcome though. I don’t know if we have docs on how to add a new compiler or not.

Cc: @brad.king

---

<div class="post-metadata">

### Author: ![jtxa](https://discourse.cmake.org/user_avatar/discourse.cmake.org/jtxa/32/1535_2.png) [@jtxa](https://discourse.cmake.org/u/jtxa)
#### Post date: [May 31, 2022, 1:52am UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759/3 "2022-05-31T01:52:40Z")

</div>

This Clang based compiler seems to be released by TI last year for the first time.  
The currently supported TI compilers are not based on Clang, so probably even a new `TIClang` compiler id has to be introduced.

---

<div class="post-metadata">

### Author: ![brad.king](https://discourse.cmake.org/user_avatar/discourse.cmake.org/brad.king/32/11_2.png) [@brad.king](https://discourse.cmake.org/u/brad.king)
#### Post date: [May 31, 2022, 5:38pm UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759/4 "2022-05-31T17:38:57Z")

</div>

Yes, a new `TIClang` compiler id and supporting compiler information modules will probably be needed. Please open an issue to propose the work.

---

<div class="post-metadata">

### Author: ![Raisha](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/r/dec6dc/32.png) [@Raisha](https://discourse.cmake.org/u/Raisha)
#### Post date: [June 1, 2022, 10:28am UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759/5 "2022-06-01T10:28:57Z")

</div>

Hi,  
Thank you for the response.  
To avoid the compiler test, we have added set(CMAKE\_C\_COMPILER\_WORKS 1) flag and build a sample application using TI\_ARM\_ClangCompiler\_1.3.0 successfully…  
Will there any issue by doing this ?

---

<div class="post-metadata">

### Author: ![brad.king](https://discourse.cmake.org/user_avatar/discourse.cmake.org/brad.king/32/11_2.png) [@brad.king](https://discourse.cmake.org/u/brad.king)
#### Post date: [June 1, 2022, 1:02pm UTC](https://discourse.cmake.org/t/ti-arm-clang-compiler-1-3-0-not-passing-initial-compiler-test/5759/6 "2022-06-01T13:02:56Z")

</div>

`CMAKE_C_COMPILER_WORKS` is not documented for public use, and causes several inspection checks to be skipped, whose results may be needed in some cases for the generators to work correctly.
