From: "Maciej W. Rozycki" <macro@mips.com>
To: insight@sourceware.org
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [patch] Only use CW_SYNC_WINENV for Cygwin 1.15.20+
Date: Mon, 14 May 2007 13:49:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0705141344200.12457@perivale.mips.com> (raw)
In-Reply-To: <20070510152950.GA5528@ednor.casa.cgf.cx>
On Thu, 10 May 2007, Christopher Faylor wrote:
> There is no such thing as Cygwin 1.15.20. I don't know exactly when this was
> applied but I would just avoid referring to the exact version of Cygwin in the
> ChangeLog.
Hmm, your own words:
http://www.cygwin.com/ml/cygwin/2006-07/msg00037.html
Or do you mean the missing "-1" suffix? If so, then sorry -- this can
certainly be rectified. I just copied the change including the comment
from elsewhere as is.
> >2007-05-10 Maciej W. Rozycki <macro@mips.com>
> >
> > * win/tclWinPipe.c (TclpCreateProcess): Only use CW_SYNC_WINENV
> > for Cygwin 1.15.20+.
> >
> > OK to apply?
>
> No, sorry. If you are going to be testing versions like this then please
> use CYGWIN_VERSION_USER_API_VERSION_COMBINED.
Well, no such macro as of 1.5.14, but it was introduced before
CW_SYNC_WINENV (at CYGWIN_VERSION_API_MINOR == 147), so it would be OK.
Except it's not going to guard against CW_SYNC_WINENV being undefined
anyway (which is what I am addressing here) as it refers to a "user_data"
structure variable, so it can only be used at the run time (the result is
not a preprocessor constant).
I could use something like:
#if CYGWIN_VERSION_DLL_MAKE_COMBINED(CYGWIN_VERSION_API_MAJOR, \
CYGWIN_VERSION_API_MINOR) >= 154
if you prefer -- does it look better to you? It builds for me. Either is
fine by my standards.
And BTW, where is "user_data" declared? Certainly not in any header
included from <cygwin/version.h>.
Maciej
next prev parent reply other threads:[~2007-05-14 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 11:42 Maciej W. Rozycki
2007-05-10 15:29 ` Christopher Faylor
2007-05-14 13:49 ` Maciej W. Rozycki [this message]
2007-05-14 15:08 ` Christopher Faylor
2007-05-14 16:29 ` Maciej W. Rozycki
2007-05-14 16:54 ` Christopher Faylor
2007-05-14 16:58 ` Keith Seitz
2007-05-14 17:13 ` Christopher Faylor
2007-05-14 17:24 ` Dave Korn
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=Pine.LNX.4.61.0705141344200.12457@perivale.mips.com \
--to=macro@mips.com \
--cc=insight@sourceware.org \
--cc=macro@linux-mips.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.
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).