- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Get "Pointers are not assignment-compatible" w...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 03:33 PM
01-22-2006 03:33 PM
Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
Here's my "log":
=================================
$ ll
-rw-r--r-- 1 kwang users 210 Jan 19 18:31 rpc.x
$ cat rpc.x
const MAXNAMELEN = 2048;
typedef string x_string
program X_RPC_FUNCTION_NUMBER
{ version X_RPC_FUNCTION_VERSION
{ x_string X_TEST(string) = 1;
} = 1;
} = 0x20000001;
$ rpcgen rpc.x
$ ll
-rw-r--r-- 1 kwang users 503 Jan 19 18:32 rpc.h
-rw-r--r-- 1 kwang users 210 Jan 19 18:31 rpc.x
-rw-r--r-- 1 kwang users 532 Jan 19 18:32 rpc_clnt.c
-rw-r--r-- 1 kwang users 4543 Jan 19 18:32 rpc_svc.c
-rw-r--r-- 1 kwang users 266 Jan 19 18:32 rpc_xdr.c
$ cc rpc_svc.c
cc: "rpc_svc.c", line 95: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 95: warning 563: Argument #2 is not the correct type.
cc: "rpc_svc.c", line 114: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 114: warning 563: Argument #3 is not the correct type.
cc: "rpc_svc.c", line 124: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 124: warning 563: Argument #3 is not the correct type.
/usr/ccs/bin/ld: Unsatisfied symbols:
...
=================================
There are unsatisfied symbols which I've taken out for this thread. My concern and surprise is 'rpc_svc.c' is generated by 'rpcgen' but shows "warning 604" error when being compiled by 'cc'. Is there something wrong in 'rpc.x' (RPC Protocol Specification File) which thus results in this error?
Attached 'rpc_svc.c' is for reference. Thanks.
@@ Kwang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 03:40 PM
01-22-2006 03:40 PM
Re: Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
@@ Kwang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 03:44 PM
01-22-2006 03:44 PM
Re: Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
Which version of "cc" compiler you are using ? #>what `which cc`
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 06:49 PM
01-22-2006 06:49 PM
Re: Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
$ what `which cc`
/usr/bin/cc:
$Revision: 92453-07 linker linker crt0.o B.11.37 040218 $
LINT B.11.11.12 CXREF B.11.11.12
HP92453-01 B.11.11.12 HP C Compiler
$ PATCH/11.00:PHCO_27774 Oct 3 2002 09:45:59 $
@@ Kwang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 06:59 PM
01-22-2006 06:59 PM
Re: Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
cc: "rpc_svc.c", line 95: warning 563: Argument #2 is not the correct type.
cc: "rpc_svc.c", line 114: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 114: warning 563: Argument #3 is not the correct type.
cc: "rpc_svc.c", line 124: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 124: warning 563: Argument #3 is not the correct type.
are related with compiler compatible warnings. Which will not effect the binary.
/usr/ccs/bin/ld: Unsatisfied symbols:
...
May be some library has to be linked during run time with SHLIB_PATH or LD_LIBRARY_PATH
--
Muthu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 07:06 PM
01-22-2006 07:06 PM
Re: Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
What are the Unsatisfied symbols you got? You can trun off warning while compiling rpc_svc.c by -w
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2006 09:13 PM
01-22-2006 09:13 PM
Re: Get "Pointers are not assignment-compatible" when compiling server skeleton generated by rpcgen
Here is the output:
=================================
$ cc rpc_svc.c
cc: "rpc_svc.c", line 95: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 95: warning 563: Argument #2 is not the correct type.
cc: "rpc_svc.c", line 114: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 114: warning 563: Argument #3 is not the correct type.
cc: "rpc_svc.c", line 124: warning 604: Pointers are not assignment-compatible.
cc: "rpc_svc.c", line 124: warning 563: Argument #3 is not the correct type.
/usr/ccs/bin/ld: Unsatisfied symbols:
svcerr_decode (first referenced in rpc_svc.o) (code)
x_test_1 (first referenced in rpc_svc.o) (code)
xdr_wrapstring (first referenced in rpc_svc.o) (code)
t_errno (first referenced in rpc_svc.o) (data)
svcerr_systemerr (first referenced in rpc_svc.o) (code)
t_getinfo (first referenced in rpc_svc.o) (code)
svc_reg (first referenced in rpc_svc.o) (code)
t_getstate (first referenced in rpc_svc.o) (code)
svc_run (first referenced in rpc_svc.o) (code)
svc_fdset (first referenced in rpc_svc.o) (data)
svc_tli_create (first referenced in rpc_svc.o) (code)
getnetconfigent (first referenced in rpc_svc.o) (code)
freenetconfigent (first referenced in rpc_svc.o) (code)
svcerr_noproc (first referenced in rpc_svc.o) (code)
xdr_x_string (first referenced in rpc_svc.o) (code)
svc_sendreply (first referenced in rpc_svc.o) (code)
xdr_void (first referenced in rpc_svc.o) (code)
svc_create (first referenced in rpc_svc.o) (code)
$
=================================
But I am much concerned about the warning error "warning 604: Pointers are not assignment-compatible" than about the unsatisfied symbols this time. From your experience, does it mean we can ignore the warning error?
@@ Kwang