Yep I thought so - that's why I didn't think it's really a bug - but the include really ought to be after the define, and if it was I would be able to use the same headers for both cygwin and non-cygwin builds...would just be 'nice to have'.
----- Original Message ----- From: "Peter Eisentraut" <[EMAIL PROTECTED]> To: "Scott" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, August 18, 2002 1:46 AM Subject: Re: [BUGS] bug in config for cygwin > Scott writes: > > > I'm not sure if what I've noticed fully qualifies as a bug...but, I run cygwin and also do a lot of development with vc++ (6)...Using version 7.2.1 I built the libpq++ libs/dll for win32 for use in my vc++ progs, and also ran the 'configure' script under cygwin...the problem occurs in the pg_config_os.h file, where an "#include <cygwin/version.h>" occurs before an "#ifdef __CYGWIN__" - so naturally my vc++ builds fail. By moving the include to after the ifdef the problem goes away...I thought I'd send this here so somwone with knowledge of patching the configure scripts etc. might have a look. > > If you configure under cygwin then you can't build under not-cygwin. If > you want to build the libraries for native Windows you need to follow the > instructions for the native build. > > -- > Peter Eisentraut [EMAIL PROTECTED] > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
