From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] collectd: fix musl builds (ipc module)
Date: Mon, 23 Nov 2015 12:57:59 +0200 [thread overview]
Message-ID: <20151123105759.GO2177@tarshish> (raw)
In-Reply-To: <20151123105437.GA14445@vostro>
Hi Alex,
On Mon, Nov 23, 2015 at 12:54:37PM +0200, Alex Suykov wrote:
[...]
> diff --git a/package/collectd/0002-ipc-enable-gnu-source.patch b/package/collectd/0002-ipc-enable-gnu-source.patch
> new file mode 100644
> index 0000000..5d8813a
> --- /dev/null
> +++ b/package/collectd/0002-ipc-enable-gnu-source.patch
> @@ -0,0 +1,26 @@
> +https://github.com/collectd/collectd/commit/3e3848349b753d78a0b1d19648fb394866856bda
> +
> + ipc: enable _GNU_SOURCE to fix build with musl libc
> +
> + This fixes compile the compile error:
> +
> + > ipc.c:154:49: error: 'struct shm_info' has no member named 'used_ids'
> + > ipc_submit_g("shm", "segments", NULL, shm_info.used_ids);
> + > ^
> +
> + Fixes #1147
Please add you sign-off here.
baruch
> +
> +diff --git a/src/ipc.c b/src/ipc.c
> +index 3763f24..b403847 100644
> +--- a/src/ipc.c
> ++++ b/src/ipc.c
> +@@ -32,6 +32,9 @@
> + #include "configfile.h"
> +
> + #if KERNEL_LINUX
> ++ /* _GNU_SOURCE is needed for struct shm_info.used_ids on musl libc */
> ++# define _GNU_SOURCE
> ++
> + /* X/OPEN tells us to use <sys/{types,ipc,sem}.h> for semctl() */
> + /* X/OPEN tells us to use <sys/{types,ipc,msg}.h> for msgctl() */
> + /* X/OPEN tells us to use <sys/{types,ipc,shm}.h> for shmctl() */
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-11-23 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 10:54 [Buildroot] [PATCH] collectd: fix musl builds (ipc module) Alex Suykov
2015-11-23 10:57 ` Baruch Siach [this message]
2015-11-23 11:17 ` Alex Suykov
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=20151123105759.GO2177@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox