This patch adds a #define for BYTE_ORDER to win32.h if it's not pulled
in elsewhere, as needed by msvc build of pgcrypto. Seems several other
platforms define it in their port file already, but not win32.

//Magnus


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

"Magnus Hagander" <mha@sollentuna.net> writes:
> This patch adds a #define for BYTE_ORDER to win32.h if it's not pulled
> in elsewhere, as needed by msvc build of pgcrypto. Seems several other
> platforms define it in their port file already, but not win32.

Done, but I think you forgot the defs for LITTLE_ENDIAN and friends
.... it seems unlikely that a platform would provide those and then
forget BYTE_ORDER.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

> > This patch adds a #define for BYTE_ORDER to win32.h if it's
> not pulled
> > in elsewhere, as needed by msvc build of pgcrypto. Seems
> several other
> > platforms define it in their port file already, but not win32.
>
> Done, but I think you forgot the defs for LITTLE_ENDIAN and
> friends ... it seems unlikely that a platform would provide
> those and then forget BYTE_ORDER.

Well, it compiled just fine, so it must've found it somewhere :-)

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

"Magnus Hagander" <mha@sollentuna.net> writes:
>> Done, but I think you forgot the defs for LITTLE_ENDIAN and
>> friends ... it seems unlikely that a platform would provide
>> those and then forget BYTE_ORDER.

> Well, it compiled just fine, so it must've found it somewhere :-)

I think the #if tests probably reduced to 0 == 0 ... so my bet is
it compiled but didn't work.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly