Mercurial > hg > RemoteEditor > vim7
comparison README_os390.txt @ 39:c16898406ff2
synchorinize version 7.3.081
author | one@zeus.cr.ie.u-ryukyu.ac.jp |
---|---|
date | Fri, 17 Dec 2010 17:43:06 +0900 |
parents | e170173ecb68 |
children |
comparison
equal
deleted
inserted
replaced
38:e06a1cd7230d | 39:c16898406ff2 |
---|---|
1 README_os_390.txt for version 7.2 of Vim: Vi IMproved. | 1 README_zOS.txt for version 7.3 of Vim: Vi IMproved. |
2 | 2 |
3 Welcome to the OS/390 Unix port of VIM. | 3 This readme explains how to build Vim on z/OS. Formerly called OS/390. |
4 See "README.txt" for general information about Vim. | |
4 | 5 |
5 ATTENTION: THIS IS AN _ALPHA_ VERSION!!! | 6 Most likely there are not many users out there using Vim on z/OS. So chances |
6 I expect you to know how to handle alpha software! | 7 are good, that some bugs are still undiscovered. |
7 | 8 |
8 This port was done by Ralf Schandl <schandl@de.ibm.com>. | 9 Getting the source to z/OS: |
9 This port is not maintained or supported by IBM!! | 10 ========================== |
10 | 11 |
12 First get the source code in one big tar file and ftp it a binary to z/OS. If | |
13 the tar file is initially compressed with gzip (tar.gz) or bzip2 (tar.bz2) | |
14 uncompress it on your PC, as this tools are (most likely) not available on the | |
15 mainframe. | |
11 | 16 |
12 For the list of changes see runtime/doc/os_390.txt. | 17 To reduce the size of the tar file you might compress it into a zip file. On |
18 z/OS Unix you might have the command "jar" from java to uncompress a zip. Use: | |
19 jar xvf <zip file name> | |
20 | |
21 Unpack the tar file on z/OS with | |
22 pax -o from=ISO8859-1,to=IBM-1047 -rf vim.tar | |
23 | |
24 Note: The Vim source contains a few bitmaps etc which will be destroyed by | |
25 this command, but these files are not needed on zOS (at least not for the | |
26 console version). | |
13 | 27 |
14 | 28 |
15 Compiling: | 29 Compiling: |
16 ---------- | 30 ========== |
17 | 31 |
18 Note: After the file configure was created via autoconf, it had been | 32 Vim can be compiled with or without GUI support. For 7.3 only the compilation |
19 handedited, to make the test for ICEConnectionNumber work. | 33 without GUI was tested. Below is a section about compiling with X11 but this |
20 DO NOT run autoconf again! | 34 is from an earlier version of Vim. |
21 | 35 |
22 Without X11: | 36 Console only: |
37 ------------- | |
23 | 38 |
24 If you build VIM without X11 support, compiling and building is nearly | 39 If you build VIM without X11 support, compiling and building is nearly |
25 straightforward. The only restriction is, that you can't call make from the | 40 straightforward. |
26 VIM toplevel directory. Change to the src directory first and call make from | 41 |
27 there. Here is a what to do: | 42 Change to the vim directory and do: |
28 | 43 |
29 # Don't use c89! | 44 # Don't use c89! |
30 # Make additional symbols visible. | |
31 # Allow intermixing of compiler options and files. | 45 # Allow intermixing of compiler options and files. |
32 | 46 |
33 $ export CC=cc | 47 $ export CC=cc |
34 $ export CFLAGS=-D_ALL_SOURCE | |
35 $ export _CC_CCMODE=1 | 48 $ export _CC_CCMODE=1 |
36 $./configure --enable-max-features --without-x --enable-gui=no | 49 $./configure --with-features=big --without-x --enable-gui=no |
37 $ cd src | 50 $ cd src |
38 $ make | 51 $ make |
52 | |
53 There may be warnings: | |
54 - include files not found (libc, sys/param.h, ...) | |
55 - Redeclaration of ... differs from ... | |
56 -- just ignore them. | |
57 | |
39 $ make test | 58 $ make test |
40 | 59 |
41 Note: Test 28 will be reported as failed. This is because diff can't | 60 This will produce lots of garbage on your screen (including error |
42 compare files containing '\0' characters. Test 11 will fail if you | 61 messages). Don't worry. |
43 don't have gzip. | 62 |
63 If the test stops at one point in vim (might happen in test 11), just | |
64 press :q! | |
65 | |
66 Expected test failures: | |
67 11: If you don't have gzip installed | |
68 24: test of backslash sequences in regexp are ASCII dependent | |
69 42: Multibyte is not supported on z/OS | |
70 55: ASCII<->EBCDIC sorting | |
71 57: ASCII<->EBCDIC sorting | |
72 58: Spell checking is not supported with EBCDIC | |
73 71: Blowfish encryption doesn't work | |
44 | 74 |
45 $ make install | 75 $ make install |
46 | 76 |
47 | 77 |
48 With X11: | 78 With X11: |
79 --------- | |
80 | |
81 WARNING: This instruction was not tested with Vim 7.3. | |
49 | 82 |
50 There are two ways for building VIM with X11 support. The first way is simple | 83 There are two ways for building VIM with X11 support. The first way is simple |
51 and results in a big executable (~13 Mb), the second needs a few additional | 84 and results in a big executable (~13 Mb), the second needs a few additional |
52 steps and results in a much smaller executable (~4.5 Mb). This examples assume | 85 steps and results in a much smaller executable (~4.5 Mb). This examples assume |
53 you want Motif. | 86 you want Motif. |
54 | 87 |
55 The easy way: | 88 The easy way: |
56 $ export CC=cc | 89 $ export CC=cc |
57 $ export CFLAGS="-D_ALL_SOURCE -W c,dll" | |
58 $ export LDFLAGS="-W l,dll" | |
59 $ export _CC_CCMODE=1 | 90 $ export _CC_CCMODE=1 |
60 $ ./configure --enable-max-features --enable-gui=motif | 91 $ ./configure --enable-max-features --enable-gui=motif |
61 $ cd src | 92 $ cd src |
62 $ make | 93 $ make |
63 | 94 |
64 With this VIM is linked statically with the X11 libraries. | 95 With this VIM is linked statically with the X11 libraries. |
65 | 96 |
66 The smarter way: | 97 The smarter way: |
67 Make VIM as described above. Then create a file named 'link.sed' with the | 98 Make VIM as described above. Then create a file named 'link.sed' with the |
68 following contense: | 99 following content (see src/link.390): |
69 | 100 |
70 s/-lXext *//g | 101 s/-lXext *//g |
71 s/-lXmu *//g | 102 s/-lXmu *//g |
72 s/-lXm */\/usr\/lib\/Xm.x /g | 103 s/-lXm */\/usr\/lib\/Xm.x /g |
73 s/-lX11 */\/usr\/lib\/X11.x /g | 104 s/-lX11 */\/usr\/lib\/X11.x /g |
82 Now Vim is linked with the X11-DLLs. | 113 Now Vim is linked with the X11-DLLs. |
83 | 114 |
84 See the Makefile and the file link.sh on how link.sed is used. | 115 See the Makefile and the file link.sh on how link.sed is used. |
85 | 116 |
86 | 117 |
87 Hint: | |
88 ----- | |
89 Use the online help! (See weaknesses below.) | |
90 | |
91 Example: | |
92 Enter ':help syntax' and then press <TAB> several times, you will switch | |
93 through all help items containing 'syntax'. Press <ENTER> on the one you are | |
94 interested at. Or press <Ctrl-D> and you will get a list of all items printed | |
95 that contain 'syntax'. | |
96 | |
97 The helpfiles contains cross-references. Links are between '|'. Position the | |
98 cursor on them and press <Ctrl-]> to follow this link. Use <Ctrl-T> to jump | |
99 back. | |
100 | |
101 Known weaknesses: | |
102 ----------------- | |
103 | |
104 - You can't call make from the toplevel directory, you have to do a 'cd src' | |
105 first. If you do it, make will call configure again. I don't know why and | |
106 didn't investigate it, there were more important things to do. If you can | |
107 make it work drop me a note. | |
108 | |
109 - The documentation was not updated for this alpha release. It contains lot of | |
110 ASCII dependencies, especially in examples. | |
111 | |
112 - Digraphs are dependent on code page 1047. Digraphs are used to enter | |
113 characters that normally cannot be entered by an ordinary keyboard. | |
114 See ":help digraphs". | |
115 | |
116 - Using 'ga' to show the code of the character under the cursor shows the | |
117 correct dec/hex/oct values, but the other informations might be missing or | |
118 wrong. | |
119 | |
120 - The sed syntax file doesn't work, it is ASCII dependent. | |
121 | |
122 Bugs: | |
123 ----- | |
124 If you find a bug please inform me (schandl@de.ibm.com), don't disturb Bram | |
125 Moolenaar. It's most likely a bug I introduced during porting or some ASCII | |
126 dependency I didn't notice. | |
127 | |
128 Feedback: | |
129 --------- | |
130 Feedback welcome! Just drop me a note. |