| Summary: | azure-iot-sdk-c: Installed headers do not compile | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | James Cowgill <jcowgill+busybox> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot, yann.morin.1998 |
| Priority: | P5 | ||
| Version: | 2021.02.10 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
Thanks for your bug report, can you confirm that the following patch fixes your issue: https://patchwork.ozlabs.org/project/buildroot/patch/20220305204446.823802-1-fontaine.fabrice@gmail.com/ James, All, Thanks for the report. We believe fis is now fixed with the patch from Fabrice applied to master: d1debbb4c7eb package/azure-iot-sdk-c: drop custom install rules Regards, Yann E. MORIN. |
After building azure-iot-sdk-c... test.c contains: #include <iothub_client.h> Running this: $ output/host/bin/aarch64-none-linux-gnu-gcc -c test.c Gives: In file included from test.c:1: .../output/host/aarch64-buildroot-linux-gnu/sysroot/usr/include/iothub_client.h:22:10: fatal error: umock_c/umock_c_prod.h: No such file or directory 22 | #include "umock_c/umock_c_prod.h" | ^~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. Most of the headers seem to depend on umock_c which isn't installed. $ find output/staging/usr/include -name umock_c $ This bug pretty much makes the package unusable. ---- It's only slightly related, but I also wonder why the headers are installed directly into "/usr/include" even though upstream installs them under "/usr/include/azureiot".