Bug 4806 - rpcgen generates garbage
Summary: rpcgen generates garbage
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
URL:
Whiteboard:
Keywords:
: 4807 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-08-31 17:08 UTC by ftaylor
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-09-23 03:21:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description ftaylor 1999-08-31 17:08:53 UTC 
rpcgen -C -M -N -l foo.x -o foo_clnt.c

generates an uncompilable c file with syntax errors

Same file works fine on Solaris 2.6

If you cannot duplicate this, I can send you test data
Comment 1 Jeff Johnson 1999-08-31 17:54:59 UTC 
Please send test data. Note that the rpcgen on solaris has different
syntax because of the dynamic port binding etc.
Comment 2 Jeff Johnson 1999-08-31 17:57:59 UTC 
*** Bug 4807 has been marked as a duplicate of this bug. ***

the header file generated with:

rpcgen -C -M -N -h cc.x -o cc.h

contains function definitions that are inconsistent with

rpcgen -C -M -N -c cc.x -o cc_xdr.c

functions that take 'pointer to foo' as an argument
in the .c file are defined in the .h file as taking 'foo'
as an argument

Same stuff works well on Solaris 2.x, and has for years

I can send a sample if necessary.


------- Additional Comments From jbj@redhat.com  08/31/99 13:56 -------
Please send sample. I'm going to coalesce these two problems.
Comment 3 Cristian Gafton 1999-09-23 03:21:59 UTC 
closed dues to lack of feedback, Please reopen if still have test
data.
Note You need to log in before you can comment on or make changes to this bug.