From: Davis Herring <herring@lanl.gov>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, kbrown@cornell.edu,
Angelo Graziosi <angelo.graziosi@alice.it>
Subject: Re: Too many warnings building Emacs with GCC 6 on MSYS2-MinGW64
Date: Thu, 1 Sep 2016 10:17:36 -0600 [thread overview]
Message-ID: <3d9a7a28-d82c-2ad6-f4b0-adfebe6b6544@lanl.gov> (raw)
In-Reply-To: <83a8frfvxe.fsf@gnu.org>
> On Unix, execve indeed returns an int, because it's a process ID. On
> Windows, the return value can be a process handle, which is a 64-bit
> data type on 64-bit Windows. That is why the return value must be
> intptr_t, not an int.
No, it's an error code. (You said as much for POSIX in your following
message, but it's an error code on all systems.) If it succeeds, the
process image has been replaced and it doesn't return at all.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2016-09-01 16:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:01 Too many warnings building Emacs with GCC 6 on MSYS2-MinGW64 Angelo Graziosi
2016-08-31 14:27 ` Eli Zaretskii
2016-08-31 15:01 ` Angelo Graziosi
2016-08-31 15:42 ` Eli Zaretskii
2016-08-31 17:40 ` Angelo Graziosi
2016-08-31 18:11 ` Ken Brown
2016-08-31 18:47 ` Eli Zaretskii
2016-08-31 19:56 ` Angelo Graziosi
2016-09-01 2:37 ` Eli Zaretskii
2016-09-01 7:44 ` Angelo Graziosi
2016-09-01 14:17 ` Eli Zaretskii
2016-09-01 15:42 ` Angelo Graziosi
2016-09-01 16:04 ` Eli Zaretskii
2016-09-01 16:12 ` Eli Zaretskii
2016-09-01 16:14 ` Angelo Graziosi
2016-09-01 16:17 ` Davis Herring [this message]
2016-09-01 16:24 ` Ken Brown
2016-09-01 17:43 ` Davis Herring
2016-09-01 16:29 ` Eli Zaretskii
2016-09-01 16:32 ` Andreas Schwab
2016-09-01 16:49 ` Eli Zaretskii
2016-09-01 16:25 ` Angelo Graziosi
2016-09-01 16:30 ` Eli Zaretskii
2016-09-01 19:44 ` Angelo Graziosi
2016-09-01 17:19 ` Eli Zaretskii
2016-08-31 18:18 ` Eli Zaretskii
2016-09-01 18:50 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d9a7a28-d82c-2ad6-f4b0-adfebe6b6544@lanl.gov \
--to=herring@lanl.gov \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).