On Thu, Oct 04, 2007 at 12:43:53PM -0400, Mark Johnson wrote: > > Yes. The wire protocol is 32/64 invariant. > > > > > The reason I ask is because I saw some references to longs.. > > > For example, in xdr_remote_node_get_info_ret() > > > > I must admit to being puzzelled as to why rpcgen decided to use > > IXDR_GET_LONG there. All the rest of the code in that function is > > using int, and the protocol is defined to be int. > > I'll have to go back and check which one I was compiling > at the time.. Maybe it uses that for 32-bit only which should't > be a problem... The remote_protocol.c/h files are generated from remote_protocol.x using rpcgen. That said, we actually distribute the generated files and keep them in CVS, since the protocol doesn't change & we prefer to have known tested code, rather than whatever rpcgen decides to generate per OS. If you do see problems it could of course be a bug in the rpcgen tool we used, so may be worth deleting the .c/h files and seeing if the Solaris rpcgen does a better job. Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list