sockserv and servsock should be able to run on different platforms. 

But up to now they should not run on machines with different endians.

It should not be a problem to fix this but I did not find the time
yet. Therefore one has to change the startup of the connection to
transmit the endian type. This would loose the backward compatibility. 

NEW: The check is added and we refuse connections from clients
     with other endianess.

And finally you have to call some routines to fix the endians of 
the variables. Some are already in network byte order and some
were changed by snort to the endianess of the sensor.

Note: For the packet itself (pcap format) we don't need to
      change anything. This format is already in network
      byte order.

Thus the real time consuming part is to find these variables.

(Ok, more precisely you need a big endian and a little endian
machine. You have to setup the database and configure sockserv
and servsock so that they can communicate. Finally you have to
generate the alerts and sniff them with something like tcpdump
and then compare the results with the entries in the database.)