# Legato building for wp76xx fails with missing 'le\_tpf.api'

**URL:** <https://mangoh.discourse.group/t/legato-building-for-wp76xx-fails-with-missing-le-tpf-api/3074>\
**Category:** mangOH Red\
**Created:** [November 19, 2019, 9:58pm UTC](https://mangoh.discourse.group/t/legato-building-for-wp76xx-fails-with-missing-le-tpf-api/3074 "2019-11-19T21:58:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![garify](https://avatars.discourse-cdn.com/v4/letter/g/d26b3c/32.png) [@garify](https://mangoh.discourse.group/u/garify)\
**Post date:** [November 19, 2019, 9:58pm UTC](https://mangoh.discourse.group/t/legato-building-for-wp76xx-fails-with-missing-le-tpf-api/3074/1 "2019-11-19T21:58:30Z")

</div>

I’m building Legato tag ` 18.09.0`. It fails with the error:

```auto
ninja: error: '$LEGATO_ROOT/interfaces/airVantage/le_tpf.api',
 needed by '$LEGATO_ROOT/build/wp76xx/system/api/0cb6f940ec18e2baa5093c68e2eddf27/le_tpf_commonclient.c', missing and no known rule to make it 
Makefile:607: recipe for target 'system_wp76xx' failed 
make: *** [system_wp76xx] Error 1 

```

I’ve checked and indeed that file is not available.

I’ve googled around with no success. Any assistance will be appreciated.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [November 20, 2019, 2:37am UTC](https://mangoh.discourse.group/t/legato-building-for-wp76xx-fails-with-missing-le-tpf-api/3074/2 "2019-11-20T02:37:14Z")

</div>

I tried build legato 19.02 for WP76.  
No problem is found.  
Maybe you can have a try.

---

<div class="post-metadata">

**Author:** ![garify](https://avatars.discourse-cdn.com/v4/letter/g/d26b3c/32.png) [@garify](https://mangoh.discourse.group/u/garify)\
**Post date:** [November 25, 2019, 7:13pm UTC](https://mangoh.discourse.group/t/legato-building-for-wp76xx-fails-with-missing-le-tpf-api/3074/3 "2019-11-25T19:13:35Z")

</div>

Yes, this worked. I took the leaf way, which worked quite well for me.
