From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: ignore O_CLOEXEC when the operating system doesn't provide it;
Date: Sat, 7 Feb 2015 02:53:31 -0500 (EST) [thread overview]
Message-ID: <14965342121932928181.enqueue@fantadrom.bsd.lv> (raw)
Log Message:
-----------
ignore O_CLOEXEC when the operating system doesn't provide it;
needed for some older versions of SunOS;
from jperkin@ via wiz@, both at NetBSD
Modified Files:
--------------
mdocml:
compat_fts.c
Revision Data
-------------
Index: compat_fts.c
===================================================================
RCS file: /home/cvs/mdocml/mdocml/compat_fts.c,v
retrieving revision 1.7
retrieving revision 1.8
diff -Lcompat_fts.c -Lcompat_fts.c -u -p -r1.7 -r1.8
--- compat_fts.c
+++ compat_fts.c
@@ -66,6 +66,9 @@ static int fts_safe_changedir(FTS *, FT
#ifndef O_DIRECTORY
#define O_DIRECTORY 0
#endif
+#ifndef O_CLOEXEC
+#define O_CLOEXEC 0
+#endif
#define CLR(opt) (sp->fts_options &= ~(opt))
#define ISSET(opt) (sp->fts_options & (opt))
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2015-02-07 7:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14965342121932928181.enqueue@fantadrom.bsd.lv \
--to=schwarze@mdocml.bsd.lv \
--cc=source@mdocml.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).