Andrew Dunstan <and...@dunslane.net> writes: > On 12/15/2010 06:42 PM, Tom Lane wrote: >> Hm, where did you get this?
> I downloaded > <http://softlayer.dl.sourceforge.net/project/mingw/MinGW/BaseSystem/RuntimeLibrary/MinGW-RT/mingwrt-3.18/mingwrt-3.18-mingw32-src.tar.gz> > > which is allegedly the source for the latest released runtime. Huh, I wonder why it doesn't match what's in sourceforge CVS? Anyway, the short answer is that this code has got no visible commonality with glibc's getopt(), so we need not fear that what it's doing is likely to start happening elsewhere. I didn't take the time to trace through the glibc code exactly; I figure the lack of trouble reports is sufficient proof that we're not doing anything that it won't cope with. So I concur with the previous suggestions: 1. Make this problem go away by forcing use of our getopt code on mingw. 2. Make sure we reset optreset when using our code. (Probably not really necessary, but let's just be careful.) Should we backpatch either of these things? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
