Re: Borland c++ compile problems
От | Jeroen T. Vermeulen |
---|---|
Тема | Re: Borland c++ compile problems |
Дата | |
Msg-id | 20041108030747.GA82614@xs4all.nl обсуждение исходный текст |
Ответ на | Borland c++ compile problems (Hans-Günther Röwekamp <HGRoew@gmx.de>) |
Список | pgsql-interfaces |
On Wed, Nov 03, 2004 at 11:51:41PM +0100, Hans-G?nther R?wekamp wrote: > \fe connect.c: > Warning W8017..\..\include\port/win32.h 37: Redefinition of ' DLL IMPORT ' > is not identically > Error E2209 \fe connect.c 23: Include file ' unistd.h ' cannot be opened > Error E2209 \fe connect.c for 32: Include file ' pg_config_paths.h ' cannot > be opened > Error E2451 \fe connect.c for 2399: Undefined symbol ' SYSCONFDIR ' in > function parseServiceInfo > --- > Where can I get the missing file? It would seem that you're hitting several unrelated problems here: 1. The include/port/win32.h header appears to try to set things up in a way that's right for Microsoft's compiler, but thinking that it's right for Microsoft's OS. The company doesn't always make it easy to distinguish between the two; you may need to do some research to find out how DLL importing is handled in Borland C++ Builder as opposed to MS Visual C++. Either that, or look for a suitable "Visual C++ compatibility" option in your compiler. 2. The unistd.h header is something your system/compiler combination would normally provide. You either have it or you don't; it's not likely to be fixable if you don't. *However,* there's a chance that the configuration script actually checks for it and knows how to work around a missing unistd.h, and this is simply a case where the file shouldn't be included. Try commenting out the #include <unistd.h>; if you get lots of errors for undefined Unix types/functions, you're out of luck. 3. Have you tried doing a search for pg_config_paths.h? If it doesn't exist, it's probably generated by the configure script. Did you get any errors when you ran the configure script? Jeroen
В списке pgsql-interfaces по дате отправления: