From owner-freebsd-hackers  Fri Apr 14 14: 6: 7 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from dmz.visiontech-dml.com (dmz.visiontech-dml.com [199.203.103.41])
	by hub.freebsd.org (Postfix) with ESMTP id F2EE437B564
	for <freebsd-hackers@freebsd.org>; Fri, 14 Apr 2000 14:05:55 -0700 (PDT)
	(envelope-from nobody@visiontech-dml.com)
Received: (from nobody@localhost)
	by dmz.visiontech-dml.com (8.9.3/8.9.3) id XAA12255;
	Fri, 14 Apr 2000 23:04:02 +0200 (IST)
Date: Fri, 14 Apr 2000 23:04:02 +0200 (IST)
Message-Id: <200004142104.XAA12255@dmz.visiontech-dml.com>
To: Nick Sayer <nsayer@quack.kfu.com>
Subject: Re: XDR porting problems
From: vns@visiontech-dml.com
Reply-To: vns@visiontech-dml.com
Cc: freebsd-hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP3 Imap webMail Program 2.0.11
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi!

Just try to use the next hack:
#define xdrproc_t hack_xdrproc_t
#include <rpc/xdr.h>
#undef xdrproc_t
typedef bool_t (*xdrproc_t) __P((XDR *, void *, ...));

But probably it's better to fix this problem in the  
/usr/src/include/rpc/xdr.h file.

With best regards, 
Vladimir Silyaev

--------------------------------------------------

in RELENG_4, /usr/src/include/rpc/xdr.h, there is...

#ifdef _KERNEL
typedef bool_t (*xdrproc_t) __P((XDR *, void *, u_int));
#else
/*
 * XXX can't actually prototype it, because some take 
two args!!!
 */
typedef bool_t (*xdrproc_t) __P((/* XDR *, void *, u_int 
*/));
#endif

This causes heartburn for a program I'm trying to port. 
Specifically,
compiling a .cxx says that I am using too many 
arguments.

Changing the 2nd typedef to

typedef bool_t (*xdrproc_t) __P((XDR *, void *, ...));

fixes this. I am not enough of a language pedant to 
understand all
possible ramifications of this change. Can anyone 
suggest any
alternatives? I dug around quite a bit and could find no 
way
to compile the code in question without changing the 
system include
files. If this is the right thing to do, I would like to 
commit it.
If there is a better thing to do, I'd like to hear about 
it.





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message