Re: Complier warnings on mingw gcc 4.5.0
От | Andrew Dunstan |
---|---|
Тема | Re: Complier warnings on mingw gcc 4.5.0 |
Дата | |
Msg-id | 4D08EC82.9020307@dunslane.net обсуждение исходный текст |
Ответ на | Re: Complier warnings on mingw gcc 4.5.0 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Complier warnings on mingw gcc 4.5.0
|
Список | pgsql-hackers |
On 12/15/2010 11:12 AM, Tom Lane wrote: > Alvaro Herrera<alvherre@commandprompt.com> writes: >> This bug seems closely related to process_postgres_switches. I guess >> it'd be useful to add some debugging printouts there to figure out >> what's being passed the second time around. > It strikes me that the most obvious source for a platform dependency > there would be getopt(), in particular the arrangements to cause getopt > to behave sanely when we invoke it on a different argc array the second > time around. If that were failing for some reason, you could imagine > getopt seeing 'postgres' as the next switch to parse, which could lead > to the reported failure. > > Hence: > > 1. Is that build using src/port/getopt.c, or a library-supplied getopt? > What about getopt_long.c? > > 2. Is HAVE_INT_OPTRESET getting defined? Should it be? > > I had the same thought. I did try forcing use of our getopt and getopt_long, without success, but didn't look at optreset. cheers andrew
В списке pgsql-hackers по дате отправления: