On Tue, Oct 02, 2007 at 12:21:31AM +0100, Ben Hutchings wrote: > diff -u <(c++filt <libskstream-0.3-4_i386 | sort) <(c++filt > <libskstream-0.3-4_amd64 | sort) > --- /dev/fd/63 2007-10-02 00:19:14.445928644 +0100 > +++ /dev/fd/62 2007-10-02 00:19:14.445928644 +0100 > @@ -102,7 +102,7 @@ > raw_socket_stream::raw_socket_stream(FreeSockets::IP_Protocol)@Base 0.3.6-2 > raw_socket_stream::setBroadcast(bool)@Base 0.3.6-2 > raw_socket_stream::setProtocol(FreeSockets::IP_Protocol)@Base 0.3.6-2 > - socketbuf::setbuf(char*, int)@Base 0.3.6-2 > + socketbuf::setbuf(char*, long)@Base 0.3.6-2 > socketbuf::setSocket(int)@Base 0.3.6-2 > socketbuf::~socketbuf()@Base 0.3.6-2 > socketbuf::~socketbuf()@Base 0.3.6-2
That was exactly what I was referring to. Sorry for being unclear. Is it a common problem that APIs use some 32-bit data types on 32-bit archs/userland and 64-bit data types on 64-bit archs? Cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]