| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Updated VC++ patch |
| Date: | 2006-06-07 22:23:56 |
| Message-ID: | 200606072223.k57MNuE23497@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Patch applied, adjusted version attached. Thanks.
This still needs the the build script to produce the project files.
---------------------------------------------------------------------------
Magnus Hagander wrote:
> Here's an updated version of the VC++ patch. Changes since last time:
>
>
> * Moved _dosmaperr() to port (from backend/port), and use it in
> dirent.c, per Qingqing. (so backend/port/win32/error.c should be deleted
> now). Please double-check the configure.in change, because my autoconf
> just won't cooperate on win32 :-(
> This also adds a couple of #ifdef FRONTEND for the ereport calls.
>
> * Change definition of NAN, per Tom.
>
> * Change src/port/thread.c so it doesn't pull in pthread.h when building
> the backend, since it doesn't use any thread-specific functions there
> anyway.
>
>
> Tom has already committed a fix for the other float8 problem.
>
> //Magnus
Content-Description: vcbuild.patch
[ Attachment, skipping... ]
Content-Description: vcbuild_newfiles.tar.gz
[ Attachment, skipping... ]
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| Attachment | Content-Type | Size |
|---|---|---|
| /bjm/diff | text/x-diff | 62.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-06-07 22:24:56 | Re: fix minor spelling issues in FAQ |
| Previous Message | Robert Treat | 2006-06-07 21:17:04 | fix minor spelling issues in FAQ |