Mark, on the "make" I get the following output : [EMAIL PROTECTED] mvs-client]# make cc -c -I. gfsawsha.c gfsawsha.c: In function `getsite_1': gfsawsha.c:641: warning: passing arg 3 of pointer to function from incompatible pointer type gfsawsha.c:641: warning: passing arg 4 of pointer to function from incompatible pointer type gfsawsha.c:641: warning: passing arg 5 of pointer to function from incompatible pointer type gfsawsha.c:641: warning: passing arg 6 of pointer to function from incompatible pointer type cc -c -I. gfsawaxd.c gfsawaxd.c: In function `xdr_rtnattr': gfsawaxd.c:231: warning: passing arg 4 of `xdr_pointer' from incompatible pointer type cc -o showattr gfsawsha.o gfsawaxd.o cc -c -I. gfsawlin.c cc -c -I. gfsawclt.c gfsawclt.c: In function `mvsnfsproc_login_1': gfsawclt.c:164: warning: passing arg 3 of pointer to function from incompatible pointer type gfsawclt.c:164: warning: passing arg 4 of pointer to function from incompatible pointer type gfsawclt.c:164: warning: passing arg 5 of pointer to function from incompatible pointer type gfsawclt.c:164: warning: passing arg 6 of pointer to function from incompatible pointer type gfsawclt.c: In function `mvsnfsproc_logout_1': gfsawclt.c:207: warning: passing arg 3 of pointer to function from incompatible pointer type gfsawclt.c:207: warning: passing arg 4 of pointer to function from incompatible pointer type gfsawclt.c:207: warning: passing arg 5 of pointer to function from incompatible pointer type gfsawclt.c:207: warning: passing arg 6 of pointer to function from incompatible pointer type cc -c -I. gfsawmcl.c cc -c -I. gfsawmou.c cc -o mvslogin gfsawlin.o gfsawclt.o gfsawmcl.o gfsawmou.o gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1
--Harold -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 08:31 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to support/use? Harold, I got them to compile with no problem on an Intel Linux system. What problems are you having? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kubannek, Harold Sent: Friday, February 06, 2004 10:26 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to support/use? We are running Red Hat 7.2 with the 2.4.21 kernel (with the patches from the June Stream 2003 applied) and have been able to implement hipersockets with no problems - in preparation to test David's backup solution. If I can just get the mvslogin/mvslogout to compile on Linux!! Anyone been able to do this? --Harold -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 07:42 To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1.
