# EFM32 Pearl Gecko tickless demo build error

**URL:** <https://forums.freertos.org/t/efm32-pearl-gecko-tickless-demo-build-error/6674>\
**Category:** Kernel\
**Created:** [July 12, 2017, 7:55am UTC](https://forums.freertos.org/t/efm32-pearl-gecko-tickless-demo-build-error/6674 "2017-07-12T07:55:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [July 12, 2017, 7:55am UTC](https://forums.freertos.org/t/efm32-pearl-gecko-tickless-demo-build-error/6674/1 "2017-07-12T07:55:30Z")

</div>

**[daichiertl](https://sourceforge.net/u/daichiertl/)** wrote on [Wednesday, July 12, 2017](https://sourceforge.net/p/freertos/discussion/382005/thread/57f68073/#acd1):

I imported the sample project for Pearl Gecko to Simplicity Studio (`CORTEX_EFM32_Pearl_Gecko_Simplicity_Studio`).  
[http://www.freertos.org/EFM32-Giant-Gecko-Pearl-Gecko-tickless-RTOS-demo.html](http://www.freertos.org/EFM32-Giant-Gecko-Pearl-Gecko-tickless-RTOS-demo.html)  
But, the following error was found and I couldn’t build it.

Error Description:  
make: \*\*\* No rule to make target `clean’. Stop.  
Error Resource:  
RTOSDemo  
Error Type:  
C/C++ Problem

`Makefile` that Simplicity Studio automatically created was empty.  
How can I fix it?

Environment:

- Microcontroller: EFM32 Pearl Gecko
- Tool: Simplicity Studio v4
- OS: macOS Sierra 10.12.3
- Version of FreeRTOS: 9.0.0

---

<div class="post-metadata">

**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\
**Post date:** [July 12, 2017, 4:17pm UTC](https://forums.freertos.org/t/efm32-pearl-gecko-tickless-demo-build-error/6674/2 "2017-07-12T16:17:52Z")

</div>

**[rtel](https://sourceforge.net/u/rtel/)** wrote on [Wednesday, July 12, 2017](https://sourceforge.net/p/freertos/discussion/382005/thread/57f68073/#acd1/446d):

I have no idea about running SimplicityStudio on a Mac, but a recent  
post reporting something similar was resolved when the poster updated  
their version of SimplicityStudio to the most recent.