From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Raspberry Pi - WiringPi Library Package
Date: Thu, 11 Jul 2013 09:04:19 +0300 [thread overview]
Message-ID: <20130711060419.GD4338@tarshish> (raw)
In-Reply-To: <20130711060008.GA5570@enterprise.localdomain>
Hi Guillermo,
On Wed, Jul 10, 2013 at 11:00:08PM -0700, Guillermo A. Amaral wrote:
> On Thu, Jul 11, 2013 at 08:33:59AM +0300, Baruch Siach wrote:
> > On Wed, Jul 10, 2013 at 10:19:20PM -0700, Guillermo A. Amaral wrote:
> > > From: "Guillermo A. Amaral" <g@maral.me>
> > >
> > >
> > > Signed-off-by: Guillermo A. Amaral <g@maral.me>
> > > ---
[...]
> > > ++#ifndef O_CLOEXEC
> > > ++#define O_CLOEXEC 0
> >
> > Are you sure? I see
> >
> > #define O_CLOEXEC 02000000
> >
> > in include/uapi/asm-generic/fcntl.h.
> >
>
> Hi baruch,
>
> Usage of O_CLOEXEC in wiringPi was added very recently, it started failing
> after that. I hear it still works if you're using glibc though (I haven't
> tested it).
>
> Here's the output if you remove the patch:
>
> /development/test/build/wiringpi-02a3bd8d8f2ae5c873e63875a8faef5b627f9db6/wiringPi/wiringPi.c: In function ?wiringPiSetup?:
> /development/test/build/wiringpi-02a3bd8d8f2ae5c873e63875a8faef5b627f9db6/wiringPi/wiringPi.c:1544:49: error: ?O_CLOEXEC? undeclared (first use in this function)
> /development/test/build/wiringpi-02a3bd8d8f2ae5c873e63875a8faef5b627f9db6/wiringPi/wiringPi.c:1544:49: note: each undeclared identifier is reported only once for each function it appears in
> make[2]: *** [wiringPi/CMakeFiles/wiringPi.dir/wiringPi.c.o] Error 1
> make[1]: *** [wiringPi/CMakeFiles/wiringPi.dir/all] Error 2
> make: *** [all] Error 2
I didn't say you should remove this patch, just use the correct value. Setting
O_CLOEXEC to 0 makes it effectively a no-op. Is this intended?
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-11 6:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPeEpDpMY2sRjGdd+TgPz5S--Pws+5hUNrV8jpiznxBqFZ7zDg@mail.gmail.com>
2013-07-11 5:17 ` [Buildroot] [PATCH] Raspberry Pi - WiringPi Library Package Guillermo A. Amaral
2013-07-11 5:19 ` Guillermo A. Amaral
2013-07-11 5:33 ` Baruch Siach
2013-07-11 6:00 ` Guillermo A. Amaral
2013-07-11 6:04 ` Baruch Siach [this message]
2013-07-11 6:38 ` Guillermo A. Amaral
2013-07-11 7:42 ` Carsten Schoenert
2013-07-11 17:55 ` Guillermo Amaral
2013-07-11 18:06 ` Baruch Siach
2013-07-11 18:22 ` Guillermo Amaral
2013-07-12 3:24 ` Baruch Siach
2013-07-12 4:30 ` Guillermo Amaral
2013-07-12 6:47 ` Baruch Siach
2013-07-12 6:54 ` Guillermo A. Amaral
2013-07-10 7:12 Guillermo A. Amaral
2013-07-10 9:26 ` Thomas Petazzoni
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=20130711060419.GD4338@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 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.