AT&T UNIX™PC Unix System V Users Manual - tenox
AT&T UNIX™PC Unix System V Users Manual - tenox AT&T UNIX™PC Unix System V Users Manual - tenox
Important Information, Version 3.51 ---- -- -- -- - 4. hfc_ctl(l) Hardware flow control is now available on the serial ports of the UNIX PC. See the manual page for more information. 5. ktune(l) ktune(l) provides a flag, -r, that will reset all tunable parameters to their default values. See the manual page for more information. 6. UNIX Windowing Utilities (XT/Layers) UNIX System V Release 3 Windowing Utilites are provided with version 3.5 1. For complete information, refer to "AT&T UNIX PC Windowing Software XT/Layers- Version 3.51" in this section. 7. Documentation Preparation Set The Documentation Preparation package has been extensively revised with version 3.51. For complete information, refer to the "AT&T UNIX PC Documentation Preparation Set - Version 3.51" in this section. 2 Important Information
---- -- -- -- - Important Information, Version 3.51 TECHNICAL TI PS: 1. mas and mcc If a language or application needs mas or mcc, the commands may be accessed as follows: a. Log in as root b. cd to !bin c. type: In as mas and In cc mcc d. There is no guarantee that mas or mcc will work exactly as before. 2. Shared Library In order to use the shared library, the user program must be linked with a special ifile and runtime startoff. Typically, the command line is written as: ld llib/crtOs.o llib/shlib.ifile -o target usrprog -Ix where -lx may be any library other than libc.a. The shared library is intended to contain all of the routines loaded by -lc, -ltam, and -ltermlib. With the delivery of new system software, libc.a is contained in the shared library. The user should note that the packaging of the software has the shared library in the Foundation Set and libc.a in the Development Set If for any reason, the user believes that the contents of the shared library and libc .a do not correspond, such as might result from loading different releases of the software or from deliberate modifications to either of the libraries, then the shared library may be used by invoking a two step link edit process as follows: Step 1: Step 2: ld -r -o output /Iib/crtOs.o /Iib/shlib.ifile object_files ld -o target output -Ix -Ic It is recommended that the user create private libraries rather than modify libc.a or the shared library. A user-modified libc.a or shared library will not be supported. Important Information 3
- Page 2 and 3: ©1986, 1985 AT&T All Rights Reserv
- Page 6 and 7: Important Information, Version 3.51
- Page 8 and 9: Important Information, Version 3.51
- Page 10 and 11: Important Information, Version 3.51
- Page 12 and 13: Windowing Software, Version 3.51 --
- Page 14 and 15: Windowing Software, Version 3.51 --
- Page 16 and 17: Document Preparation, Version 3.51
- Page 18 and 19: Document Preparation, Version 3.51
- Page 20 and 21: Document Preparation, Version 3.51
- Page 22 and 23: Document Preparation, Version 3.51
- Page 24 and 25: Document Preparation, Version 3.51
- Page 26 and 27: APPENDIX A: Document Preparation, V
- Page 28 and 29: APPENDIX A: Document Preparation, V
- Page 30: APPENDIX B: Document Preparation, V
- Page 35 and 36: 470(1) 470( 1) NAME 470 - filters n
- Page 37 and 38: 478(1) ESC-s ESC-U ESC-u ESC-W ESC-
- Page 39 and 40: BRK(2) BRK(2) NAME brk, sbrk - chan
- Page 41 and 42: COL( l) COL( l) NAME col - filter r
- Page 43 and 44: CONVERT( I) CONVERT( I) NAME conver
- Page 45 and 46: EQNCHAR(S) EQNCHAR(S) NAME eqnchar
- Page 47 and 48: FX (1) FX(l) NAME fx - filters nrof
- Page 49 and 50: HPU(l) HPU( 1) NAME hplj -filters n
- Page 51 and 52: ISMPX(l) ISMPX(l) NAME ismpx - retu
- Page 53 and 54: JWIN( l) NAME SYNOPSIS jwin jwin -p
---- -- -- -- - Important Information, Version 3.51<br />
TECHNICAL TI PS:<br />
1. mas and mcc<br />
If a language or application needs mas or mcc, the commands may<br />
be accessed as follows:<br />
a. Log in as root<br />
b. cd to !bin<br />
c. type: In as mas and In cc mcc<br />
d. There is no guarantee that mas or mcc will work exactly as<br />
before.<br />
2. Shared Library<br />
In order to use the shared library, the user program must be linked<br />
with a special ifile and runtime startoff. Typically, the command line<br />
is written as:<br />
ld llib/crtOs.o llib/shlib.ifile -o target usrprog -Ix<br />
where -lx may be any library other than libc.a.<br />
The shared library is intended to contain all of the routines loaded by<br />
-lc, -ltam, and -ltermlib. With the delivery of new system software,<br />
libc.a is contained in the shared library. The user should note that the<br />
packaging of the software has the shared library in the Foundation<br />
Set and libc.a in the Development Set If for any reason, the user<br />
believes that the contents of the shared library and libc .a do not<br />
correspond, such as might result from loading different releases of<br />
the software or from deliberate modifications to either of the<br />
libraries, then the shared library may be used by invoking a two step<br />
link edit process as follows:<br />
Step 1:<br />
Step 2:<br />
ld -r -o output /Iib/crtOs.o /Iib/shlib.ifile object_files<br />
<br />
ld -o target output -Ix -Ic <br />
It is recommended that the user create private libraries rather than<br />
modify libc.a or the shared library. A user-modified libc.a or shared<br />
library will not be supported.<br />
Important Information 3
Change language