Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Thu, Dec 9, 2021 at 02:43 PM, Dave Wade wrote:
Ok they appear to work, but I can remember how to re-direct stdout (duh?). You need to use dotted file names so
type hello c
#include <stdio.h>
int main(int argc, char * argv[]) {
printf("Good morning... from HELLO!\n");
}
Ready; T=0.01/0.01 15:41:49
type hella c
#include <stdio.h>
int main(int argc, char * argv[]) {
printf("Good afternoon. from HELLO!\n");
}
Ready; T=0.01/0.01 15:42:02
diff hello.c hella.c
3c3
< printf("Good morning... from HELLO!\n");
---
printf("Good afternoon. from HELLO!\n");
Ready(00001); T=0.01/0.03 15:39:46
Dave
The diff program seems to be a complete unix port. By just typing 'diff --help' it dumps the help, just like it does on *nix. diff --helpUsage: diff [OPTION]... FILESCompare files line by line.?? -i? --ignore-case? Ignore case differences in file contents.
...Patch is expecting filenames rather than file redirection. I've worked with this stuff before. Just have to remember how.patch --helpUsage: patch [OPTION]... [ORIGFILE [PATCHFILE]]?Input options:?? -p NUM? --strip=NUM? Strip NUM leading components from file names....
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark, Ok they appear to work, but I can remember how to re-direct stdout (duh?). You need to use dotted file names so type hello c #include <stdio.h> int main(int argc, char * argv[]) { printf("Good morning... from HELLO!\n"); } Ready; T=0.01/0.01 15:41:49 type hella c #include <stdio.h> int main(int argc, char * argv[]) { printf("Good afternoon. from HELLO!\n"); } Ready; T=0.01/0.01 15:42:02 diff hello.c hella.c 3c3 < printf("Good morning... from HELLO!\n"); --- printf("Good afternoon. from HELLO!\n"); Ready(00001); T=0.01/0.03 15:39:46 Dave -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Wade
via groups.io
Sent: 09 December 2021 20:22
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark,
OK "diff" and "patch" exist so you can use those to maintain "c" files (possibly
I haven't tested them).
Thinking about it, I probably didn't do anything about "sys" as I don't think it
existed in "C90" so you may have to patch it.
Dave
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Wade via
groups.io
Sent: 09 December 2021 20:10
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
I think that is correct. I can't remember if I did anything special
for "sys" when I tweaked the code for "sys". Let me have a look.
By the way GMAIL seems to block this. Might be better to upload files
to the group files store.
I think Paul also ported DIFF and PATCH so you don't have to use
sequence numbers for "C" programs.
Dave
On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-D
Within the attached file, zlib-1.2.11.tar.gz, is the program,
adler32.c, which I am trying to compile, using GCCLIB. Screen
scraping is in
adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.
No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.
For this one:
types.h:25:22: features.h: An error has occurred
I am guessing that it is complaining about not finding the sys
directory. I can remove this, and make it read # define "types.h"
but that means I'm altering the original code, which bothers me no end.
That takes me to XCOMPARE and trying to create CNTRL and AUX files,
for a language that has no understanding of sequence numbers. Yuck.
File: ZCONF H C1 RECFM: F LRECL: 80(80) Lines: 534
Current: 440
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif
=====
===== #ifdef STDC
===== # ifndef Z_SOLO
===== # include <sys/types.h> /* for off_t */
===== # endif
===== #endif
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage
class
File: TYPES H C1 RECFM: F LRECL: 80(80) Lines: 232
Current: 45
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined
===== # ifndef __USE_FILE_OFFSET64
===== typedef __ino_t ino_t;
===== # else
===== typedef __ino64_t ino_t;
===== # endif
I believe it is complaining that ino_t is not defined, prior to
being defined as itself. I discovered that it is supposed to be of
type inode, but that definition escapes me so far. I know what it
should be, in that it is a block of data in a Unix filesystem, but
its definition, size, & structure, I have not found.
I haven't gotten beyond, this, yet. I also realize this isn't
directly related to VM/370 CE, so if we need to continue this
elsewhere, let me
know.
... Mark S.
On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-D
Within the attached file, zlib-1.2.11.tar.gz, is the program,
adler32.c, which I am trying to compile, using GCCLIB. Screen
scraping is in
adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.
No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.
For this one:
types.h:25:22: features.h: An error has occurred
I am guessing that it is complaining about not finding the sys
directory. I can remove this, and make it read # define "types.h"
but that means I'm altering the original code, which bothers me no end.
That takes me to XCOMPARE and trying to create CNTRL and AUX files,
for a language that has no understanding of sequence numbers. Yuck.
File: ZCONF H C1 RECFM: F LRECL: 80(80) Lines: 534
Current: 440
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif
=====
===== #ifdef STDC
===== # ifndef Z_SOLO
===== # include <sys/types.h> /* for off_t */
===== # endif
===== #endif
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage
class
File: TYPES H C1 RECFM: F LRECL: 80(80) Lines: 232
Current: 45
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined
===== # ifndef __USE_FILE_OFFSET64
===== typedef __ino_t ino_t;
===== # else
===== typedef __ino64_t ino_t;
===== # endif
I believe it is complaining that ino_t is not defined, prior to
being defined as itself. I discovered that it is supposed to be of
type inode, but that definition escapes me so far. I know what it
should be, in that it is a block of data in a Unix filesystem, but
its definition, size, & structure, I have not found.
I haven't gotten beyond, this, yet. I also realize this isn't
directly related to VM/370 CE, so if we need to continue this
elsewhere, let me
know.
... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark,
OK "diff" and "patch" exist so you can use those to maintain "c" files (possibly I haven't tested them).
Thinking about it, I probably didn't do anything about "sys" as I don't think it existed in "C90" so you may have to patch it.
Dave
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Wade
via groups.io
Sent: 09 December 2021 20:10
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
I think that is correct. I can't remember if I did anything special for "sys" when
I tweaked the code for "sys". Let me have a look.
By the way GMAIL seems to block this. Might be better to upload files to the
group files store.
I think Paul also ported DIFF and PATCH so you don't have to use sequence
numbers for "C" programs.
Dave
On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-D
Within the attached file, zlib-1.2.11.tar.gz, is the program,
adler32.c, which I am trying to compile, using GCCLIB. Screen scraping is in
adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.
No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.
For this one:
types.h:25:22: features.h: An error has occurred
I am guessing that it is complaining about not finding the sys
directory. I can remove this, and make it read # define "types.h" but
that means I'm altering the original code, which bothers me no end.
That takes me to XCOMPARE and trying to create CNTRL and AUX files,
for a language that has no understanding of sequence numbers. Yuck.
File: ZCONF H C1 RECFM: F LRECL: 80(80) Lines: 534
Current: 440
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif
=====
===== #ifdef STDC
===== # ifndef Z_SOLO
===== # include <sys/types.h> /* for off_t */
===== # endif
===== #endif
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage
class
File: TYPES H C1 RECFM: F LRECL: 80(80) Lines: 232
Current: 45
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined
===== # ifndef __USE_FILE_OFFSET64
===== typedef __ino_t ino_t;
===== # else
===== typedef __ino64_t ino_t;
===== # endif
I believe it is complaining that ino_t is not defined, prior to being
defined as itself. I discovered that it is supposed to be of type
inode, but that definition escapes me so far. I know what it should
be, in that it is a block of data in a Unix filesystem, but its
definition, size, & structure, I have not found.
I haven't gotten beyond, this, yet. I also realize this isn't directly
related to VM/370 CE, so if we need to continue this elsewhere, let me
know.
... Mark S.
On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-D
Within the attached file, zlib-1.2.11.tar.gz, is the program,
adler32.c, which I am trying to compile, using GCCLIB. Screen scraping is in
adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.
No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.
For this one:
types.h:25:22: features.h: An error has occurred
I am guessing that it is complaining about not finding the sys
directory. I can remove this, and make it read # define "types.h" but
that means I'm altering the original code, which bothers me no end.
That takes me to XCOMPARE and trying to create CNTRL and AUX files,
for a language that has no understanding of sequence numbers. Yuck.
File: ZCONF H C1 RECFM: F LRECL: 80(80) Lines: 534
Current: 440
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif
=====
===== #ifdef STDC
===== # ifndef Z_SOLO
===== # include <sys/types.h> /* for off_t */
===== # endif
===== #endif
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage
class
File: TYPES H C1 RECFM: F LRECL: 80(80) Lines: 232
Current: 45
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined
===== # ifndef __USE_FILE_OFFSET64
===== typedef __ino_t ino_t;
===== # else
===== typedef __ino64_t ino_t;
===== # endif
I believe it is complaining that ino_t is not defined, prior to being
defined as itself. I discovered that it is supposed to be of type
inode, but that definition escapes me so far. I know what it should
be, in that it is a block of data in a Unix filesystem, but its
definition, size, & structure, I have not found.
I haven't gotten beyond, this, yet. I also realize this isn't directly
related to VM/370 CE, so if we need to continue this elsewhere, let me
know.
... Mark S.
|
Folks,
I have disabled attachments as GMAIL seems to block anything any one attaches.
If you want to distribute files please use the files section on the groups.io web site. Create a folder and store the files in it.
There is also a photos section for your pictures.
Thanks,
Dave
G4UGM
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
I think that is correct. I can't remember if I did anything special for "sys" when I tweaked the code for "sys". Let me have a look. By the way GMAIL seems to block this. Might be better to upload files to the group files store. I think Paul also ported DIFF and PATCH so you don't have to use sequence numbers for "C" programs. Dave On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-D
Within the attached file, zlib-1.2.11.tar.gz, is the program, adler32.c, which
I am trying to compile, using GCCLIB. Screen scraping is in adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.
No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.
For this one:
types.h:25:22: features.h: An error has occurred
I am guessing that it is complaining about not finding the sys directory. I
can remove this, and make it read # define "types.h" but that means I'm
altering the original code, which bothers me no end. That takes me to XCOMPARE
and trying to create CNTRL and AUX files, for a language that has no
understanding of sequence numbers. Yuck.
File: ZCONF??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 534
Current:?? 440
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif
=====
===== #ifdef STDC
===== #? ifndef Z_SOLO
===== #??? include <sys/types.h>????? /* for off_t */
===== #? endif
===== #endif
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage class
File: TYPES??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 232
Current:??? 45
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined
===== # ifndef __USE_FILE_OFFSET64
===== typedef __ino_t ino_t;
===== # else
===== typedef __ino64_t ino_t;
===== # endif
I believe it is complaining that ino_t is not defined, prior to being defined
as itself. I discovered that it is supposed to be of type inode, but that
definition escapes me so far. I know what it should be, in that it is a block
of data in a Unix filesystem, but its definition, size, & structure, I have
not found.
I haven't gotten beyond, this, yet. I also realize this isn't directly related
to VM/370 CE, so if we need to continue this elsewhere, let me know.
... Mark S.
On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-D
Within the attached file, zlib-1.2.11.tar.gz, is the program, adler32.c, which
I am trying to compile, using GCCLIB. Screen scraping is in adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.
No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.
For this one:
types.h:25:22: features.h: An error has occurred
I am guessing that it is complaining about not finding the sys directory. I
can remove this, and make it read # define "types.h" but that means I'm
altering the original code, which bothers me no end. That takes me to XCOMPARE
and trying to create CNTRL and AUX files, for a language that has no
understanding of sequence numbers. Yuck.
File: ZCONF??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 534
Current:?? 440
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif
=====
===== #ifdef STDC
===== #? ifndef Z_SOLO
===== #??? include <sys/types.h>????? /* for off_t */
===== #? endif
===== #endif
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage class
File: TYPES??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 232
Current:??? 45
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined
===== # ifndef __USE_FILE_OFFSET64
===== typedef __ino_t ino_t;
===== # else
===== typedef __ino64_t ino_t;
===== # endif
I believe it is complaining that ino_t is not defined, prior to being defined
as itself. I discovered that it is supposed to be of type inode, but that
definition escapes me so far. I know what it should be, in that it is a block
of data in a Unix filesystem, but its definition, size, & structure, I have
not found.
I haven't gotten beyond, this, yet. I also realize this isn't directly related
to VM/370 CE, so if we need to continue this elsewhere, let me know.
... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:
Which file do you need? Always prepared to have look
Now here's someone just asking for pain :-DWithin the attached file, zlib-1.2.11.tar.gz, is the program, adler32.c, which I am trying to compile, using GCCLIB. Screen scraping is in adler32.listing.
I found /usr/include/sys/types.h and added it to minidisk accessed as C.No clue why I'm getting the following error:OPEN ERROR CODE '04' ON 'PDP001HD'.For this one: types.h:25:22: features.h: An error has occurredI am guessing that it is complaining about not finding the sys directory. I can remove this, and make it read # define "types.h" but that means I'm altering the original code, which bothers me no end. That takes me to XCOMPARE and trying to create CNTRL and AUX files, for a language that has no understanding of sequence numbers. Yuck. File: ZCONF??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 534 Current:?? 440????? ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8===== #endif?????????????????????????????????????????????????????????????????? ????? ?=====????????????????????????????????????????????????????????????????????????? ????? ?===== #ifdef STDC????????????????????????????????????????????????????????????? ????? ?===== #? ifndef Z_SOLO???????????????????????????????????????????????????????? ????? ?===== #??? include <sys/types.h>????? /* for off_t */????????????????????????? ????? ?===== #? endif???????????????????????????????????????????????????????????????? ????? ?===== #endif?????????????????????????????????????????????????????????????????? ?????? For the following error: types.h:47: syntax error before "typedef"types.h:47: ISO C forbids data definition with no type or storage classFile: TYPES??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 232 Current:??? 45????? ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8===== #ifndef __ino_t_defined????????????????????????????????????????????????? ????? ?===== # ifndef __USE_FILE_OFFSET64???????????????????????????????????????????? ????? ?===== typedef __ino_t ino_t;?????????????????????????????????????????????????? ????? ?===== # else?????????????????????????????????????????????????????????????????? ????? ?===== typedef __ino64_t ino_t;???????????????????????????????????????????????? ????? ?===== # endif????????????????????????????????????????????????????????????????? ?????? I believe it is complaining that ino_t is not defined, prior to being defined as itself. I discovered that it is supposed to be of type inode, but that definition escapes me so far. I know what it should be, in that it is a block of data in a Unix filesystem, but its definition, size, & structure, I have not found.
I haven't gotten beyond, this, yet. I also realize this isn't directly related to VM/370 CE, so if we need to continue this elsewhere, let me know.
?... Mark S.
|
Re: vm370 Load command in exec file
I went with your suggestion of TXTLIB concept and it worked great!!!! Thank you so much.
Bob B, thank your for plan b, will keep it on file.
Again Thank you for the responses...? Moving forward.
Cheers Tom c
On Wed, Dec 8, 2021 at 5:17 PM Jean-Pierre Cabani¨¦ < jean-pierre@...> wrote: Quick and dirty : create a TXTLIB with 13 parts and then use it in your
GLOBAL before loading the last one and issue the genmod command
Other way would be to use a variable to hold the sequence of names and
then issue LOAD &ALLNAMES. Not sure it will work...
Good luck
Jean-Pierre
Le 09/12/2021 ¨¤ 00:06, Tom Chandler a ¨¦crit?:
> Most likely really dumb question, but I have a LOAD command that has14
> modules to load before
> I do a GENMOD.? It appears after col 72, the system drops the
> remaining names.
>
> Is there a way to have a "continuation" when using the load command in
> an exec file.
>
> Thank You
> Tom c.
|
Re: vm370 Load command in exec file
LOAD NAME1
INCLUDE NAME2 INCLUDE NAME3 INCLUDE NAME4 ---- GENMOD MYMOD
I will never be able to type on a phone.
What I use is: LOAD NAME INCLUDE NAME2 INCLUDE NAME Etc--------- GENMOD MYMOD
Most likely really dumb question, but I have a LOAD command that has14 modules to load before
I do a GENMOD.? It appears after col 72, the system drops the remaining names.
Is there a way to have a "continuation" when using the load command in an exec file.
Thank You
Tom c.
|
Re: vm370 Load command in exec file
What I use is: LOAD NAME INCLUDE NAME2 INCLUDE NAME Etc--------- GENMOD MYMOD
Most likely really dumb question, but I have a LOAD command that has14 modules to load before
I do a GENMOD.? It appears after col 72, the system drops the remaining names.
Is there a way to have a "continuation" when using the load command in an exec file.
Thank You
Tom c.
|
Re: vm370 Load command in exec file
Quick and dirty : create a TXTLIB with 13 parts and then use it in your GLOBAL before loading the last one and issue the genmod command
Other way would be to use a variable to hold the sequence of names and then issue LOAD &ALLNAMES. Not sure it will work...
Good luck
Jean-Pierre
toggle quoted message
Show quoted text
Le 09/12/2021 ¨¤ 00:06, Tom Chandler a ¨¦crit?: Most likely really dumb question, but I have a LOAD command that has14 modules to load before
I do a GENMOD.? It appears after col 72, the system drops the remaining names.
Is there a way to have a "continuation" when using the load command in an exec file.
Thank You
Tom c.
|
vm370 Load command in exec file
Most likely really dumb question, but I have a LOAD command that has14 modules to load before
I do a GENMOD.? It appears after col 72, the system drops the remaining names.
Is there a way to have a "continuation" when using the load command in an exec file.
Thank You
Tom c.
|
|
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark, Which file do you need? Always prepared to have look Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 07 December 2021 17:36
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk? #VMCE? On Tue, Dec 7, 2021 at 11:06 AM, Bob Bolch wrote: Compile a C program that includes something from this disk, with the CMS option, and you will see that the include files are processed.
Bob,
I am missing a header, which started this entire journey. Plus side, I know more than I started with. Minus side, I need to port the missing header file to CMS.
Thank you!
?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Tue, Dec 7, 2021 at 11:05 AM, Dave Wade wrote:
The CMS headers are the ones on GCCCMS 202 disk. These are what are used when you compile something with GCC and specify the CMS library option.
(well assuming you are not logged on to maint and have the 394 accessed)
Dave, The minidisk is released, after my attempted compile, and I didn't know what was, or was not available. This kicked off the search, which turned into this chain of messages. Thanks for your help. ?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Tue, Dec 7, 2021 at 11:06 AM, Bob Bolch wrote:
Compile a C program that includes something from this disk, with the CMS option, and you will see that the include files are processed.
Bob, I am missing a header, which started this entire journey. Plus side, I know more than I started with. Minus side, I need to port the missing header file to CMS. Thank you! ?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Hi Mark, I setup the MAINTC disks for the purpose of building the C runtime, and BREXX.
You should use the GCC user disks which the compiler accesses during the compilation. When the CMS option is specified, the GCCCMS 202 is used for the compilation. You do not need to manually access it.?
Compile a C program that includes something from this disk, with the CMS option, and you will see that the include files are processed.
Bob
On Tue, Dec 7, 2021, 11:40 AM Mark A. Stevens via <marXtevens= [email protected]> wrote: On Tue, Dec 7, 2021 at 05:19 AM, Bob Bolch wrote:
GCCCMS 201 minidisk is accessed when the OS parameter is specified.
GCCCMS 202 minidisk is accessed when the CMS parameter is specified.
?
Do those disks contain the H files you are looking for?
Bob,
I am more interested in the CMS emulation/headers than OS, at this instant.
It seems that MAINTC 394 (see the reply to Dave) and GCCCMS 202 contain same/similar files.
I will make time to compare and see if they are identical, and report back, if you wish.
q disk f
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
Ready; T=0.01/0.01 16:24:53
l * h f ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
ASSERT?? H??????? F2? V??? 71???? 25????? 2? 04/14/21?? 11:40
CMSRUNTM H??????? F2? V?? 106??? 218???? 16? 03/23/21??? 8:13
CMSSYS?? H??????? F2? V?? 108??? 862???? 89? 04/14/21?? 11:40
CTYPE??? H??????? F2? V?? 100???? 62????? 3? 04/14/21?? 11:40
ERRNO??? H??????? F2? V??? 71???? 64????? 3? 04/14/21?? 11:40
FLOAT??? H??????? F2? V??? 75??? 127????? 5? 04/14/21?? 11:40
GCCCRAB? H??????? F2? V?? 100???? 68????? 4? 03/23/21??? 7:07
LIMITS?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40
LOCALE?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40
MATH???? H??????? F2? V??? 71??? 113????? 4? 04/14/21?? 11:40
REXXSAA? H??????? F2? V??? 81??? 162???? 11? 04/14/21?? 11:40
SETJMP?? H??????? F2? V?? 100???? 42????? 5? 04/14/21?? 11:40
SIGNAL?? H??????? F2? V??? 71???? 33????? 2? 04/14/21?? 11:40
STDARG?? H??????? F2? V??? 73???? 22????? 2? 04/14/21?? 11:40
STDDEF?? H??????? F2? V??? 71???? 38????? 2? 04/14/21?? 11:40
STDIO??? H??????? F2? V?? 100??? 782???? 81? 04/14/21?? 11:40
STDLIB?? H??????? F2? V?? 100??? 381???? 20? 04/14/21?? 11:40
STRING?? H??????? F2? V??? 73??? 173????? 9? 04/14/21?? 11:40
TIME???? H??????? F2? V??? 71???? 65????? 3? 04/14/21?? 11:40
TSTS???? H??????? F2? V?? 125???? 98????? 5? 04/14/21?? 11:40
Ready; T=0.01/0.01 16:25:00
Again, if I can help, please let me know.
?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark, ? The CMS headers are the ones on GCCCMS 202 disk. These are what are used when you compile something with GCC and specify the CMS library option. (well assuming you are not logged on to maint and have the 394 accessed) ? Harold, ? I don¡¯t think there is comprehensive documentation anywhere. Paul keeps everything on windows and copies it to VM when he wants to do a compile hence all the stuff in the batch directory. The fact that we have two totally independent C libraries makes a mess of things. ? Dave ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 07 December 2021 16:41
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk? #VMCE? On Tue, Dec 7, 2021 at 05:19 AM, Bob Bolch wrote: GCCCMS 201 minidisk is accessed when the OS parameter is specified. GCCCMS 202 minidisk is accessed when the CMS parameter is specified. Do those disks contain the H files you are looking for?
Bob,
I am more interested in the CMS emulation/headers than OS, at this instant.
It seems that MAINTC 394 (see the reply to Dave) and GCCCMS 202 contain same/similar files.
I will make time to compare and see if they are identical, and report back, if you wish.
q disk f
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
Ready; T=0.01/0.01 16:24:53
l * h f ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
ASSERT?? H??????? F2? V??? 71???? 25????? 2? 04/14/21?? 11:40
CMSRUNTM H??????? F2? V?? 106??? 218???? 16? 03/23/21??? 8:13
CMSSYS?? H??????? F2? V?? 108??? 862???? 89? 04/14/21?? 11:40
CTYPE??? H??????? F2? V?? 100???? 62????? 3? 04/14/21?? 11:40
ERRNO??? H??????? F2? V??? 71???? 64????? 3? 04/14/21?? 11:40
FLOAT??? H??????? F2? V??? 75??? 127????? 5? 04/14/21?? 11:40
GCCCRAB? H??????? F2? V?? 100???? 68????? 4? 03/23/21??? 7:07
LIMITS?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40
LOCALE?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40
MATH???? H??????? F2? V??? 71??? 113????? 4? 04/14/21?? 11:40
REXXSAA? H??????? F2? V??? 81??? 162???? 11? 04/14/21?? 11:40
SETJMP?? H??????? F2? V?? 100???? 42????? 5? 04/14/21?? 11:40
SIGNAL?? H??????? F2? V??? 71???? 33????? 2? 04/14/21?? 11:40
STDARG?? H??????? F2? V??? 73???? 22????? 2? 04/14/21?? 11:40
STDDEF?? H??????? F2? V??? 71???? 38????? 2? 04/14/21?? 11:40
STDIO??? H??????? F2? V?? 100??? 782???? 81? 04/14/21?? 11:40
STDLIB?? H??????? F2? V?? 100??? 381???? 20? 04/14/21?? 11:40
STRING?? H??????? F2? V??? 73??? 173????? 9? 04/14/21?? 11:40
TIME???? H??????? F2? V??? 71???? 65????? 3? 04/14/21?? 11:40
TSTS???? H??????? F2? V?? 125???? 98????? 5? 04/14/21?? 11:40
Ready; T=0.01/0.01 16:25:00
Again, if I can help, please let me know.
?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Tue, Dec 7, 2021 at 05:19 AM, Bob Bolch wrote:
GCCCMS 201 minidisk is accessed when the OS parameter is specified.
GCCCMS 202 minidisk is accessed when the CMS parameter is specified.
?
Do those disks contain the H files you are looking for?
Bob,I am more interested in the CMS emulation/headers than OS, at this instant.It seems that MAINTC 394 (see the reply to Dave) and GCCCMS 202 contain same/similar files.I will make time to compare and see if they are identical, and report back, if you wish.q disk fLabel? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk TotalGCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700Ready; T=0.01/0.01 16:24:53l * h f ( dateFilename Filetype Fm? Format??? Recs Blocks???? Date??? TimeASSERT?? H??????? F2? V??? 71???? 25????? 2? 04/14/21?? 11:40CMSRUNTM H??????? F2? V?? 106??? 218???? 16? 03/23/21??? 8:13CMSSYS?? H??????? F2? V?? 108??? 862???? 89? 04/14/21?? 11:40CTYPE??? H??????? F2? V?? 100???? 62????? 3? 04/14/21?? 11:40ERRNO??? H??????? F2? V??? 71???? 64????? 3? 04/14/21?? 11:40FLOAT??? H??????? F2? V??? 75??? 127????? 5? 04/14/21?? 11:40GCCCRAB? H??????? F2? V?? 100???? 68????? 4? 03/23/21??? 7:07LIMITS?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40LOCALE?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40MATH???? H??????? F2? V??? 71??? 113????? 4? 04/14/21?? 11:40REXXSAA? H??????? F2? V??? 81??? 162???? 11? 04/14/21?? 11:40SETJMP?? H??????? F2? V?? 100???? 42????? 5? 04/14/21?? 11:40SIGNAL?? H??????? F2? V??? 71???? 33????? 2? 04/14/21?? 11:40STDARG?? H??????? F2? V??? 73???? 22????? 2? 04/14/21?? 11:40STDDEF?? H??????? F2? V??? 71???? 38????? 2? 04/14/21?? 11:40STDIO??? H??????? F2? V?? 100??? 782???? 81? 04/14/21?? 11:40STDLIB?? H??????? F2? V?? 100??? 381???? 20? 04/14/21?? 11:40STRING?? H??????? F2? V??? 73??? 173????? 9? 04/14/21?? 11:40TIME???? H??????? F2? V??? 71???? 65????? 3? 04/14/21?? 11:40TSTS???? H??????? F2? V?? 125???? 98????? 5? 04/14/21?? 11:40Ready; T=0.01/0.01 16:25:00Again, if I can help, please let me know.?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
There seems to be a lot of confusion about how various header files are
included in compiles. I am certainly not an expert in GCC on VM, C
library options, or CMS itself.
But, the discussion begs the question: Is there a complete list of
which disks / modules / etc that documents the _present_ structure?
Everyone seems to see a piece of the problem not the entire structure.
Such a list might point to how it could be improved.
Just a thought,
Harold Grovesteen
toggle quoted message
Show quoted text
On Tue, 2021-12-07 at 10:06 +0000, Dave Wade wrote: Mark,
Well the mess is there BECAUSE there are two sets of ¡°.h¡± files and
CMS does not have a directory structure.
So the production GCC EXEC accesses the GCCCMS disks that contain the
¡°.h¡± files that match the library you have selected PDPCLIB or GCCLIB
There are two ways to fix this. One would be to change the GCC
compiler so you could specify which disks it searched for ¡°.h¡± files.
The other would be to modify the compiler so it could read ¡°.h¡± files
from emulated OS Partitioned Data Sets as I think the IBM compiler
does.
Neither seem attractive, but what I would think could be done is to
fix the help that¡¯s returned by ¡°HELP GCC (MORE¡± to explain what is
happening and why.
Its needs fixing anyway, its also wrong:-(
Dave
Groups.io Links:
You receive all messages sent to this group.
View/Reply Online (#3680) | Reply To Group | Reply To Sender | Mute
This Topic | New Topic
Mute #vmce
Your Subscription | Contact Group Owner | Unsubscribe [
h.grovsteen@...]
_._,_._,_
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Tue, Dec 7, 2021 at 04:06 AM, Dave Wade wrote:
There are two ways to fix this. One would be to change the GCC compiler so you could specify which disks it searched for ¡°.h¡± files.
The other would be to modify the compiler so it could read ¡°.h¡± files from emulated OS Partitioned Data Sets as I think the IBM compiler does.
?
Neither seem attractive, but what I would think could be done is to fix the help that¡¯s returned by ¡°HELP GCC (MORE¡± to explain what is happening and why.
?
Its needs fixing anyway, its also wrong:-(
Dave,Thanks for the additional explanation. I did find *.h files which seem to emulate/imitate/replace those from /usr/include/*.h files on MAINTC 394.My two cents on minidisk vs MACLIB would be minidisk, until we can get OS PDS emulation/management. The lack of a directory structure does make this a challenge, either way.q disk fLabel? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk TotalMNT394 122 F/C R/O?? 50 3350? 800???????? 87?????? 1998-07????? 26502????? 28500Ready; T=0.01/0.01 16:17:40l * h f ( dateFilename Filetype Fm? Format??? Recs Blocks???? Date??? TimeASSERT?? H??????? F1? V??? 71???? 25????? 2? 04/14/21?? 11:40CMSRUNTM H??????? F1? V?? 106??? 218???? 16? 03/23/21??? 8:13CMSSYS?? H??????? F1? V?? 108??? 862???? 89? 04/14/21?? 11:40CTYPE??? H??????? F1? V?? 100???? 62????? 3? 04/14/21?? 11:40ERRNO??? H??????? F1? V??? 71???? 64????? 3? 04/14/21?? 11:40FLOAT??? H??????? F1? V??? 75??? 127????? 5? 04/14/21?? 11:40GCCCRAB? H??????? F1? V?? 100???? 68????? 4? 03/23/21??? 7:07LIMITS?? H??????? F1? V??? 71???? 49????? 3? 04/14/21?? 11:40LOCALE?? H??????? F1? V??? 71???? 49????? 3? 04/14/21?? 11:40MATH???? H??????? F1? V??? 71??? 113????? 4? 04/14/21?? 11:40REXXSAA? H??????? F1? V??? 81??? 162???? 11? 04/14/21?? 11:40SETJMP?? H??????? F1? V?? 100???? 42????? 5? 04/14/21?? 11:40SIGNAL?? H??????? F1? V??? 71???? 33????? 2? 04/14/21?? 11:40STDARG?? H??????? F1? V??? 73???? 22????? 2? 04/14/21?? 11:40STDDEF?? H??????? F1? V??? 71???? 38????? 2? 04/14/21?? 11:40STDIO??? H??????? F1? V?? 100??? 782???? 81? 04/14/21?? 11:40STDLIB?? H??????? F1? V?? 100??? 381???? 20? 04/14/21?? 11:40STRING?? H??????? F1? V??? 73??? 173????? 9? 04/14/21?? 11:40TIME???? H??????? F1? V??? 71???? 65????? 3? 04/14/21?? 11:40TSTS???? H??????? F1? V?? 125???? 98????? 5? 04/14/21?? 11:40Ready; T=0.01/0.01 16:17:49If I can help, let me know, and I will do what I can.
?... Mark S.
|
Mark A. Stevens
Jean-Pierre Cabani¨¦
Marco Antoniotti