# Int32\_t could not be resolved

**URL:** <https://forum.legato.io/t/int32-t-could-not-be-resolved/3002>\
**Category:** Uncategorized\
**Created:** [February 1, 2018, 11:14am UTC](https://forum.legato.io/t/int32-t-could-not-be-resolved/3002 "2018-02-01T11:14:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![isabelv](https://avatars.discourse-cdn.com/v4/letter/i/b487fb/32.png) [@isabelv](https://forum.legato.io/u/isabelv)\
**Post date:** [February 1, 2018, 11:14am UTC](https://forum.legato.io/t/int32-t-could-not-be-resolved/3002/1 "2018-02-01T11:14:53Z")

</div>

Hi,

I’ve installed Legato Application Development Kit for Windows, WP770X Release 7 (Legato 17.11.0).  
Hello\_World runs without problems, but gpioCf3PinComponent gives the error ‘int32\_t could not be resolved’.  
Looking at legato.h, I see a lot of header files can’t be found:

 ![afbeelding](https://us1.discourse-cdn.com/flex019/uploads/legato1/original/1X/7de079c2cd5025364d1946b06ece448af889592f.png)

If I switch from compiling for the WP77 ([Built-in] Legato for WP77 R7 (17.11.0.wp77xx-docker-201801031728)), to compiling for the WP85 ([Built-in] Legato for WP85/WP75 R14 (16.10.3.wp85-wp75-docker-201705311408)), I can compile without any problems. Looking at the include directories I see the WP85 has a ‘include-usr’ directory in which all the header files I seem to be missing for the WP77 are listed. This directory doesn’t exist for the WP77.  
Should this directory exist? Or is something else going wrong?  
Any suggestions how to fix this?

Best regards,

Isabel.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/jyijyi/32/822_2.png) [@jyijyi](https://forum.legato.io/u/jyijyi)\
**Post date:** [February 2, 2018, 7:18am UTC](https://forum.legato.io/t/int32-t-could-not-be-resolved/3002/2 "2018-02-02T07:18:41Z")

</div>

Hi,

No idea how to resolve in Developer studio. I saw the “fatal error: unistd.h: No such file or directory” error.

However I found that I can build in the terminal in Ubuntu 14.  
Please see below log:

owner@owner-ThinkPad-T60:~$  
owner@owner-ThinkPad-T60:~$ cd /home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/  
owner@owner-ThinkPad-T60:~/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato$ . bin/configlegatoenv  
[ar7] No toolchain found for target ‘ar7’.  
[ar86] No toolchain found for target ‘ar86’.  
[wp85] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[wp750x] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[wp76xx] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[wp77xx] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[ar758x] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[ar759x] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[em75xx] Toolchain dir[/opt/swi/y22-ext/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi] prefix[arm-poky-linux-gnueabi-]  
[virt] No toolchain found for target ‘virt’.  
owner@owner-ThinkPad-T60:~/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato$ cd …  
owner@owner-ThinkPad-T60:~/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources$ cd …  
owner@owner-ThinkPad-T60:~/legato/packages/legato.framework.17.11.0.wp77xx-201801031552$ cd …  
owner@owner-ThinkPad-T60:~/legato/packages$ cd …  
owner@owner-ThinkPad-T60:~/legato$ cd workspace/  
owner@owner-ThinkPad-T60:~/legato/workspace$ cd gpioCf3PinDemo/  
owner@owner-ThinkPad-T60:~/legato/workspace/gpioCf3PinDemo$ mkapp -t wp77xx -o Target\_Legato\_Debug -w Target\_Legato\_Debug -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/airVantage/legacy” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/modemServices” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/positioning” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/portService” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/supervisor” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/secureStorage” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/airVantage” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/watchdog” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/logDaemon” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/atServices” -i “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/interfaces/wifi” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/dataConnectionService/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/apps/platformServices/airVantageConnector” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/airVantage” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/modules/WiFi/apps/tools/wifi” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/positioning” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/secStore” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/portService” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/uartMode/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/modemServices/platformAdaptor/default” -s “.” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/audio/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/3rdParty” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/apps/tools” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/fwupdate/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/dataConnectionService” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/modules/WiFi/service” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/airVantage/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/fwupdate” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/positioning/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/devMode” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/secStore/platformAdaptor/default” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/atServices” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/modemServices” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components” -s “/home/owner/legato/packages/legato.framework.17.11.0.wp77xx-201801031552/resources/legato/components/uartMode” -C -g -X -g -L -g gpioCf3PinDemo.adef  
[11/11] Packaging app  
owner@owner-ThinkPad-T60:~/legato/workspace/gpioCf3PinDemo$ ls ./Target\_Legato\_Debug/  
api build.ninja gpioCf3PinDemo.wp77xx.update mktool\_args staging  
app component Makefile mktool\_environment  
owner@owner-ThinkPad-T60:~/legato/workspace/gpioCf3PinDemo$

---

<div class="post-metadata">

**Author:** ![Manukumar](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@Manukumar](https://forum.legato.io/u/Manukumar)\
**Post date:** [February 3, 2018, 6:07am UTC](https://forum.legato.io/t/int32-t-could-not-be-resolved/3002/3 "2018-02-03T06:07:25Z")

</div>

My suggestion is:  
I think there may be chance of no updated version of clib(library). try updating that.  
or you can try compiling and build using uint32\_t insted of int32\_t.  
or you can rebuild it once again after getting “Int32\_t could not be resolved”.

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/daav/32/64_2.png) [@daav](https://forum.legato.io/u/daav)\
**Post date:** [February 8, 2018, 8:48am UTC](https://forum.legato.io/t/int32-t-could-not-be-resolved/3002/4 "2018-02-08T08:48:22Z")

</div>

Hi here,

there was an issue with WP77 R7 package.  
A new build has been done, fixing the issue.  
It is available in the **Packages** perspective of DS (build timestamp: 20180207xxxx)
