From: chrubis@suse.cz
To: "zenglg.jy" <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] dup3/dup3_02.c: fix O_CLOEXEC undeclared
Date: Wed, 8 Jan 2014 13:57:35 +0100 [thread overview]
Message-ID: <20140108125734.GA1203@rei.Home> (raw)
In-Reply-To: <1388746143.1609.19.camel@G08JYZSD130126>
Hi!
> O_CLOEXEC is not defined in RHEL5. When execute make,
> "dup3_02.c:55: error: ???O_CLOEXEC??? undeclared here (not in a function)"
> will be outputed.
>
> Signed-off-by: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
I've pushed a sligtly different patch that moves all the O_CLOEXEC
definitions that were scattered around the sources into lapi/fcntl.h
header. Thanks.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-01-08 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 10:49 [LTP] [PATCH] dup3/dup3_02.c: fix O_CLOEXEC undeclared zenglg.jy
2014-01-07 13:54 ` Jan Stancek
2014-01-08 12:57 ` chrubis [this message]
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=20140108125734.GA1203@rei.Home \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.jy@cn.fujitsu.com \
/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