From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Error while building libevas, SFD_NONBLOCK undeclared
Date: Tue, 9 Jul 2013 00:57:58 +0300 [thread overview]
Message-ID: <20130708215758.GL5098@tarshish> (raw)
In-Reply-To: <CAF3SDA77hPn0TiYNajKZNTBGWAobSuFKEyWcvRZmmrNhyjRPkA@mail.gmail.com>
Hi Daniel,
On Mon, Jul 08, 2013 at 06:01:26PM +0000, Daniel. wrote:
> I'm receiving this error while trying to build with buildroot.
>
> make[5]: Entering directory
> `/home/hilst/buildroot/buildroot-2013.05/output/build/libevas-1.7.4/src/bin'
> CC evas_cserve2_main_loop_linux.o
> evas_cserve2_main_loop_linux.c: In function '_signalfd_setup':
> evas_cserve2_main_loop_linux.c:156: error: 'SFD_NONBLOCK' undeclared (first
> use in this function)
> evas_cserve2_main_loop_linux.c:156: error: (Each undeclared identifier is
> reported only once
> evas_cserve2_main_loop_linux.c:156: error: for each function it appears in.)
> evas_cserve2_main_loop_linux.c:156: error: 'SFD_CLOEXEC' undeclared (first
> use in this fu
>
> My .config can be found here: https://gist.github.com/gkos/5950964
>
> Any help is appreciated,
>
> I'm on archilinux using Sourcery CodeBench toolchain..
The signalfd(2) man page says that these flags (SFD_NONBLOCK and SFD_CLOEXEC)
are only defined since kernel version 2.6.27. It seems that your toolchain
uses an older kernel. Which version of the Sourcery CodeBench do you use?
baruch
--
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:[~2013-07-08 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 18:01 [Buildroot] Error while building libevas, SFD_NONBLOCK undeclared Daniel.
2013-07-08 21:57 ` Baruch Siach [this message]
[not found] ` <CAF3SDA6AyqLbAgba3ZcK+o4tsHJAOVZ=LhQAfRdqWrGWjEtoew@mail.gmail.com>
2013-07-09 3:10 ` 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=20130708215758.GL5098@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