| Lists: | pgsql-cygwin |
|---|
| From: | Jason Tishler <jason(at)tishler(dot)net> |
|---|---|
| To: | Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org> |
| Subject: | PostgreSQL/Win32 sqltypes.h conflict |
| Date: | 2003-12-05 20:07:51 |
| Message-ID: | 20031205200751.GI1492@tishler.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
It appears PostgreSQL's sqltypes.h conflicts with the Win32 version:
http://cygwin.com/ml/cygwin/2003-12/msg00211.html
Does anyone have any ideas on the best way to solve this problem?
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
| From: | Seth Rubin <srubin(at)thoughtprocess(dot)com> |
|---|---|
| To: | Jason Tishler <jason(at)tishler(dot)net>, Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL/Win32 sqltypes.h conflict |
| Date: | 2003-12-05 22:54:13 |
| Message-ID: | CNELLBDHOKALJPHOOBBEMEJDEJAA.srubin@thoughtprocess.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
Maybe I'm being a little simple-minded, but would it be a good idea to
rename postgres's file to pg_sqltypes.h ? A pg_ prefix in front of
generically-named files would probably save a lot of similar future
headaches too (and not just with win32).
-----Original Message-----
From: pgsql-cygwin-owner(at)postgresql(dot)org
[mailto:pgsql-cygwin-owner(at)postgresql(dot)org]On Behalf Of Jason Tishler
Sent: Friday, December 05, 2003 3:08 PM
To: Pgsql-Cygwin
Subject: [CYGWIN] PostgreSQL/Win32 sqltypes.h conflict
It appears PostgreSQL's sqltypes.h conflicts with the Win32 version:
http://cygwin.com/ml/cygwin/2003-12/msg00211.html
Does anyone have any ideas on the best way to solve this problem?
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
| From: | Reshat Sabiq <sabiq(at)purdue(dot)edu> |
|---|---|
| To: | Seth Rubin <srubin(at)thoughtprocess(dot)com> |
| Cc: | Jason Tishler <jason(at)tishler(dot)net>, Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL/Win32 sqltypes.h conflict |
| Date: | 2003-12-06 04:02:23 |
| Message-ID: | 3FD154CF.2040009@purdue.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
This can probably be handled by playing with the path too, although i'm
not sure what's the best approach.
Sincerely,
Reshat.
-------------------------------------------------------------------------------------------
If you see my certificate with this message, you should be able to send me encrypted e-mail.
Please consult your e-mail client for details if you would like to do that.
Seth Rubin wrote:
>Maybe I'm being a little simple-minded, but would it be a good idea to
>rename postgres's file to pg_sqltypes.h ? A pg_ prefix in front of
>generically-named files would probably save a lot of similar future
>headaches too (and not just with win32).
>
>-----Original Message-----
>From: pgsql-cygwin-owner(at)postgresql(dot)org
>[mailto:pgsql-cygwin-owner(at)postgresql(dot)org]On Behalf Of Jason Tishler
>Sent: Friday, December 05, 2003 3:08 PM
>To: Pgsql-Cygwin
>Subject: [CYGWIN] PostgreSQL/Win32 sqltypes.h conflict
>
>
>It appears PostgreSQL's sqltypes.h conflicts with the Win32 version:
>
> http://cygwin.com/ml/cygwin/2003-12/msg00211.html
>
>Does anyone have any ideas on the best way to solve this problem?
>
>Thanks,
>Jason
>
>--
>PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
>Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
>
>