[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-devel
Subject:    [postgis-devel] tgl@sss.pgh.pa.us on "Determining Endianess "
From:       strk <strk () keybit ! net>
Date:       2004-02-10 20:02:48
Message-ID: 20040210210248.C41291 () freek ! keybit ! net
[Download RAW message or body]

----- Forwarded message from Tom Lane <tgl@sss.pgh.pa.us> -----

From: Tom Lane <tgl@sss.pgh.pa.us>
To: strk <strk@keybit.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] BYTE_ORDER for contribs 
Date: Mon, 09 Feb 2004 20:21:04 -0500
Message-ID: <21012.1076376064@sss.pgh.pa.us>

strk <strk@keybit.net> writes:
> Is there a quick way to use the BYTE_ORDER define
> as set by pgsql ? I can't find an "entry point"
> include for it. 

BYTE_ORDER isn't actually used anywhere in the backend, and hasn't been
for a long time, so I wouldn't count on it to be right.

> It's needed for postgis (problems with Solaris BYTE_ORDER).

My recommendation is to rethink your code.  There's usually a way to
avoid having a compile-time dependency.

			regards, tom lane

----- End forwarded message -----

[prev in list] [next in list] [prev in thread] [next in thread]