I have an rpc file foo.x that uses hyper:
struct foo_timestamp_t {
hyper secs;
hyper seqno;
};
(Yes, hyper really is an XDR type - see
http://www.ietf.org/rfc/rfc4506.txt if like me you thought it must be a
lispm joke in my .x file.)
This results in 'hyper' in the foo.h and xdr_hyper in the foo_types.c.
xdr_hyper seems defined, but it seems that either rpc/xdr.h needs to
define hyper, or the .h file should be in terms of int64_t.
It seems that rpcgen should grok TOK_HYPER, recognize this and emit
int64_t for it. Or perhaps hyper should be in rpc/xdr.h as a typedef.
Has anyone else had troubles with RPC and hyper, or have any comments?
Attachment:
pgpvI9xbsD0NI.pgp
Description: PGP signature