postgis interface has problems with different wkb data endianness

[bear@…]

WKB geometries that are not in the same endianness as mapserver cannot be used.
For example if we run the SQL server on an intel machine, query a layer with WKB
geometry and use that as layer data on a Macintosh, Mapserver dies.

My guess is this is because of the memcpy() used on floats in force_<shape>
routines, but I might be wrong.

[bear@…]

It turned out that the problem was that the postgis (and opengis simple features
standard in general) DO tako into account the endianness of the mapserver
running machine, problems rise when the machine does not have one of the 2
standard byte orders (like 4-2-3-1 on some old MIPS machines).