On Wed, Feb 28, 2001 at 12:36:45PM -0500, Tim Peters wrote:
I checked that patch in already, about 15 minutes after you uploaded it. Is this service, or what?! <wink>
Yes! Thanks again.
That patch seems fine -- except that I'd like /F to have a quick look since it changes _sre.c.
Too late and no need. What Jason did to _sre.c is *undo* some Cygwin special-casing;
Not really -- I was trying to get rid of WIN32 #ifdefs. My solution was to attempt to reuse the DL_EXPORT macro. Now I realize that I should have done the following instead:
#if defined(WIN32) || defined(__CYGWIN__) __declspec(dllexport) #endif
/F will like that.
It's trivial anyway.
I thought so too.
Jason, about this:
However, using the next Cygwin gcc (i.e., 2.95.2-8 or later) will require one to configure with: CC='gcc -mwin32' configure ...
How can we make that info *useful* to people?
I have posted to the Cygwin mailing list and C.L.P regarding my original 2.0 patches. I have also continue to post to Cygwin regarding 2.1a1 and 2.1a2. I intended to do likewise for 2.1b1, etc.
The target audience for the Cygwin port probably doesn't search Python-Dev or the Python patches database.
Agreed -- the above was only offered to the curious Python-Dev person and not for archival purposes.
So it would be good if you thought about uploading an informational patch to README and Misc/NEWS briefly telling Cygwin folks what they need to know. If you do, I'll look for it and check it in.
I will submit a patch to README to add a Cygwin section to "Platform specific notes". Unfortunately, I don't think that I can squeeze it in by 2.1b1. If not, then I will submit it for the next release (2.1b2 or 2.1 final). I also don't mind waiting for the Cygwin gcc stuff to settle down too. I know...excuses, excuses...