On Fri, Sep 05, 2008 at 12:40:13PM +0900, Jun Koi wrote:
> On Wed, Sep 3, 2008 at 8:41 PM, Richard W.M. Jones <[EMAIL PROTECTED]> wrote:
> > On Wed, Sep 03, 2008 at 01:00:52PM +0900, Jun Koi wrote:
> >> Is it really true that qemud/remote_protocol.{c,h} are created by
> >> rpcgen? If so, why dont w
On Wed, Sep 3, 2008 at 8:41 PM, Richard W.M. Jones <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 03, 2008 at 01:00:52PM +0900, Jun Koi wrote:
>> Is it really true that qemud/remote_protocol.{c,h} are created by
>> rpcgen? If so, why dont we have them created at compile time? I still
>> see them in the s
On Wed, Sep 03, 2008 at 01:00:52PM +0900, Jun Koi wrote:
> Is it really true that qemud/remote_protocol.{c,h} are created by
> rpcgen? If so, why dont we have them created at compile time? I still
> see them in the source code.
The reason is that only Linux glibc rpcgen can generate them
correctly
Hi,
Is it really true that qemud/remote_protocol.{c,h} are created by
rpcgen? If so, why dont we have them created at compile time? I still
see them in the source code.
I modified remote_protocol.x a bit, and when recompiling,
remote_protocol.{c,h} are not reflected at all. So it is expected that
