From: Ken Brown <kbrown@cornell.edu>
To: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>
Cc: Angelo Graziosi <angelo.graziosi@alice.it>
Subject: Re: [Emacs-diffs] master 0c94b84: * nt/inc/ms-w32.h (execve) [MINGW_W64]: Make commentary more accurate.
Date: Thu, 1 Sep 2016 15:57:00 -0400 [thread overview]
Message-ID: <518bc279-ee83-356a-51af-fd348d32aa4f@cornell.edu> (raw)
In-Reply-To: <20160901171604.8DF4D22016A@vcs.savannah.gnu.org>
On 9/1/2016 1:16 PM, Eli Zaretskii wrote:
> + However, using the prototype with intptr_t causes GCC to emit
> + warnings. Fortunately, execve is not used in the MinGW build, but
> + the code that references it is still compiled. */
Wouldn't it be easier to prevent that code from being compiled? Then
you could just remove the prototype. It seems confusing to include a
prototype and several lines of commentary for a function that's not used.
I think the following would suffice:
--- a/src/sysdep.c
+++ b/src/sysdep.c
@@ -146,6 +146,7 @@ disable_address_randomization (void)
}
#endif
+#ifndef WINDOWSNT
/* Execute the program in FILE, with argument vector ARGV and environ
ENVP. Return an error number if unsuccessful. This is like execve
except it reenables ASLR in the executed program if necessary, and
@@ -170,6 +171,7 @@ emacs_exec_file (char const *file, char *const
*argv, char *const *envp)
return err;
}
+#endif /* not WINDOWSNT */
/* If FD is not already open, arrange for it to be open with FLAGS. */
static void
Ken
next parent reply other threads:[~2016-09-01 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160901171604.9042.16589@vcs.savannah.gnu.org>
[not found] ` <20160901171604.8DF4D22016A@vcs.savannah.gnu.org>
2016-09-01 19:57 ` Ken Brown [this message]
2016-09-02 6:53 ` [Emacs-diffs] master 0c94b84: * nt/inc/ms-w32.h (execve) [MINGW_W64]: Make commentary more accurate Eli Zaretskii
2016-09-04 10:34 ` Angelo Graziosi
2016-09-04 18:47 ` Paul Eggert
2016-09-04 19:00 ` Eli Zaretskii
2016-09-04 20:58 ` Angelo Graziosi
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=518bc279-ee83-356a-51af-fd348d32aa4f@cornell.edu \
--to=kbrown@cornell.edu \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.