From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14636] New: azure-iot-sdk-c: Installed headers do not compile
Date: Fri, 04 Mar 2022 23:28:14 +0000 [thread overview]
Message-ID: <bug-14636-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14636
Bug ID: 14636
Summary: azure-iot-sdk-c: Installed headers do not compile
Product: buildroot
Version: 2021.02.10
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: jcowgill+busybox@jcowgill.uk
CC: buildroot@uclibc.org
Target Milestone: ---
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".
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-03-04 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 23:28 bugzilla [this message]
2022-03-06 9:05 ` [Buildroot] [Bug 14636] azure-iot-sdk-c: Installed headers do not compile bugzilla
2022-03-06 21:04 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14636-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.