From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/canfestival: fix musl compilation
Date: Tue, 18 Aug 2015 07:37:23 +0200 [thread overview]
Message-ID: <1439876243.1710.8.camel@embedded.rocks> (raw)
In-Reply-To: <1439848293-26836-1-git-send-email-brendanheading@gmail.com>
On Mo, 2015-08-17 at 22:51 +0100, Brendan Heading wrote:
> Fixes: http://autobuild.buildroot.net/results/75a/75aa6e7e4f3dcd74e4b
> 65496060328ec7bd0e747/
>
> ANSI signal handlers take an int parameter, not sigval_t.
This is true for uClibc, but for other libc timer_notify is asigned to
the `sigev_notify_function` function which has an `union sigval` as
argument [1].
Snipped from the source code of timers_unix.c:
#if defined(__UCLIBC__)
[..]
signal(SIGALRM, timer_notify);
#else
[..]
sigev.sigev_notify_function = timer_notify;
[..]
#endif
}
[1] http://man7.org/linux/man-pages/man7/sigevent.7.html
Best regards
J?rg Krause
>
next prev parent reply other threads:[~2015-08-18 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 21:51 [Buildroot] [PATCH v2 1/1] package/canfestival: fix musl compilation Brendan Heading
2015-08-18 5:37 ` Jörg Krause [this message]
2015-08-18 14:28 ` Brendan Heading
2015-08-18 5:53 ` Baruch Siach
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=1439876243.1710.8.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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