"SfR Fresh" - the SfR Freeware/Shareware Archive 
Member "Lynx/lynx_doc/PROBLEMS" of archive lynx.zip:
As a special service "SfR Fresh" has tried to format the requested source page into HTML format using source code syntax highlighting with prefixed line numbers.
Alternatively you can here view or download the uninterpreted source code file.
That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field.
1 Lynx PROBLEMS file.
2
3 Ideally you would never have to read this, but inevitably problems
4 do arise. As implementation and installation problems become known
5 they will be outlined in this file.
6
7 ---------
8
9 The install script will attempt to preserve your current settings in the
10 lynx.cfg file. You should review these (at the end of lynx.cfg) after
11 install. For instance references to lynx.browser.org for a startfile can
12 be removed, since that site is no longer maintained.
13
14 ---------
15
16 Some customized installs of OpenSSL are not detected by the configure
17 script. For example, with Redhat9, we did this to work around:
18
19 #!/bin/sh
20 KRB=/usr/kerberos
21 export LIBS="-L$KRB/lib -lssl -lcrypto -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err"
22 export CPPFLAGS="-I$KRB/include -I/usr/include/openssl"
23 export CFLAGS="-O -g $CPPFLAGS"
24 ./configure --with-ssl $*
25
26 ---------
27
28 The configure script check for IPv6 (--enable-ipv6) assumes that your build
29 machine can listen for IPv6 connections. It cannot determine if you want
30 to use it only for outgoing connections. If the configure script is
31 otherwise successful, it will warn about a nonfunctioning getaddrinfo()
32 function, and does not define these symbols needed to successfully compile
33 IPv6 support. You can work around this by by editing lynx_cfg.h:
34
35 HAVE_GAI_STRERROR
36 HAVE_GETADDRINFO
37
38 ---------
39
40 Control-Z on Unix can cause aberrant behavior. If you encounter
41 problems, use -restrictions=suspend to disable it, and only '!'
42 for escapes to shell (on VMS control-Z is unconditional 'Q'uit,
43 with no attempt to suspend the Lynx process only temporarily).
44 Control-Z on Unix often works better with slang.
45
46 ---------
47
48 Screen resizing can be a bit funny. If you resize the screen,
49 documents that have been cached will be out of whack. Any further
50 documents will look fine. You can reload documents to the current
51 window size with CTRL-R
52
53 ---------
54
55 If the configure script dies when it discovers that gcc is broken,
56 despite the fact there is a perfectly good ANSI cc in the PATH,
57 try setting the CC environment variable to your working cc compiler
58 before running configure: e.g.
59
60 setenv CC cc (or set CC=cc; export CC , depending on the shell)
61 ./configure
62
63 ---------
64
65 If you run into a problem compiling GridText.c, try omitting -O from the
66 compiler flags; it is a very big file and may not compile successfully
67 if you include optimization.
68
69 ---------
70
71 On a Sun system, the message:
72 "Alert!: Unable to connect to remote host"
73 will be displayed every time an attempt is made to access a host
74 other than localhost if Lynx has been built without the resolv
75 library and needed it, or with it and shouldn't have been.
76 Unfortunately, there's no way to check in the Makefile whether
77 -lresolv should be included in the LIBS="" list. What's necessary
78 depends on how that Sun is configured. To get the build right for
79 your SUN 3 or 4 OS, if you didn't have RESOLVLIB defined in the
80 Makefile define it and build Lynx again, or vice versa. Also, if
81 you have upgraded to the bind-8.1 or later library, you should try
82 changing -lresolv to -lbind.
83
84 ---------
85
86 On Sun systems when accessing sites that use multiple IPs for one URL,
87 you may experience a core dump. It's a bug in the resolver library,
88 which can be fixed by downloading & installing Sun's jumbo patch:
89 search Sun support information, e.g., Solaris newsgroups,
90 or see the following Lynx Archive items:
91
92 http://www.flora.org/lynx-dev/lynx-dev/9606/0422.html
93 http://www.flora.org/lynx-dev/html/month0497/msg01018.html
94 http://www.flora.org/lynx-dev/html/month0497/msg01064.html
95
96 The Sun `shelltool' and `cmdtool' terminals are stupid by default.
97 In order to get bold text to appear differently than inverse video,
98 the user should put this line in ~/.Xdefaults:
99
100 Term*boldStyle: Offset_X
101
102 From the `shelltool' man page, it seems that an analogous line
103 in ~/.defaults
104
105 /Tty/Bold_style "Offset_X"
106
107 ought to work just as well, but you may not get the desired
108 behavior until you modify your .Xdefaults file (and run `xrdb
109 ~/.Xdefaults'). Note also that there are other supported values
110 for the boldStyle resource/Bold_style default, all of which begin
111 with "Offset_". (helpful hint from kevin@traffic.den.mmc.com)
112
113 ---------
114
115 Directory browsing has been implemented for VMS, but there are no
116 plans to port additional DIRED support, because Lynx must handle files
117 as streams, and this precludes "serious" Directory/File Management on
118 VMS. Use a jumps file link to CSwing (sources or executables are
119 available from ftp://narnia.memst.edu), or define CSWING_PATH in
120 userdefs.h or lynx.cfg to invoke CSwing via the DIRED_MENU command.
121
122 ---------
123
124 If one switches between K)eypad "Numbers act as arrows" versus "Links
125 are numbered" in the 'o'ptions menu when the current document is a
126 DIRED menu in which links have been tagged, the tagging can be trashed
127 (so don't switch at such times 8-).
128
129 ---------
130
131 When "Links are numbered" is on, if a line is split on an anchor (to
132 obey right margin restrictions), and there is no space in the bolded
133 string such that the entire "[#]string" must be moved down, the "[#]"
134 becomes bolded, instead on only "string".
135
136 ---------
137
138 The Mosaic v2.5 hostlist uses HTML similar to that of Lynx's bookmark
139 file, but with </UL></HTML> at the bottom, such that it is not fully
140 compatible with Lynx's file. If you try to use the Mosaic file as if
141 it were a Lynx bookmark file, the </UL></HTML> will not be taken into
142 account and new links will be added below rather than above those end
143 tags. Instead, add a link to the Mosaic file in your Lynx file, and
144 to the Lynx file in your Mosaic file, so that you can access both files
145 with both clients.
146
147 ---------
148
149 SOCKSification and the -socks switch have not yet been integrated with
150 the slang library support.
151
152 ---------
153
154 There is an apparently broken version of select() in libcurses.a
155 of HP/UX 10.10. It also breaks tn3270, ncftp, emacs, and xemacs.
156 Using:
157 LIBS="-lc -lcurses -ltermcap \
158 ^^^
159 (i.e, adding -lc *before* the -lcurses) in the snake3 and snake3-slang
160 targets of the top level Makefile yields a usable image, but with
161 inappropriate video attributes on the Lynx displays (reverse video and
162 underscores on everything). Using "-lc -lHcurses" instead fixes the
163 ^^^^^^^^^
164 video attributes but then the arrow keys are messed up. - Donald S.
165 Teiser (dsteis01@homer.louisville.edu)
166 NOTE: If HP fixes the problem or you come up with a better workaround,
167 notify the lynx-dev@nongnu.org list.
168 Updated NOTE (1996-09-02): A patch reportedly is available from HP to
169 fix the select() problem, so that "-lc" is no longer needed, but
170 the curses glitch is not yet fixed, and you should still include
171 "-lHcurses".
172 Updated NOTE (1997-02-03): The problems reportedly are fixed with
173 patches PHCO_8086 and PHCO_8947 from HP.
174 Updated NOTE (1997-12-15): PHCO_8086 & PHCO_8947 are very old and are
175 no longer available. The current patch to install if running
176 under HP-UX 10.20 is PHCO_11342.
177
178 ---------
179
180 Lynx juggles variable abilities of curses packages or emulations to
181 display bolding and underlining simultaneously. This may fail if
182 Lynx thinks that your terminal, in connection with the curses package,
183 supports a capability which the terminal hardware or emulation does not
184 in fact support. Setting the right TERM environment variable, tweaking
185 terminfo or termcap files, or compiling with a newer version of ncurses
186 or slang may solve problems with missing highlighting or strange
187 characters appearing on the screen. Also, for a mono terminal,
188 make sure "show color" is not set to ON in the Options Menu.
189
190 The Wyse 50 and older TeleVideo terminals, among others, are
191 "magic cookie" terminals. This means that display attributes like
192 reverse, blink, underline, etc. work in a bizarre way that makes them
193 difficult to program. You may see extra spaces scattered around your
194 screen (separating different sorts of highlight); or sections of the
195 screen may be unexpectedly highlighted.
196 There is a workaround which works by restricting the terminal to a
197 single standout attribute (e.g., normal and reverse, but no others).
198 Implementing the workaround is specific to your curses implementation.
199 Most versions of curses use one of two terminal databases, called
200 "termcap" and "terminfo". Updating these databases is system-specific.
201 New databases should be available from the vendor or other sources.
202 For the Wyse 50, try
203 <URL: http://www.wyse.com/text/custserv/faq/wy50faq.htm>;
204 extract the "wy50" (NOT "wy50-mc") entry and use that in place of the
205 existing one. See `terminfo', `infocmp', `tic' etc. man pages if
206 necessary.
207 Alternatively, compiling Lynx with the slang library may avoid problems
208 with theses terminals.
209
210 The Sun console driver (aka wscons(7)) implements "reverse" and "bold"
211 as "reverse", causing confusion where Lynx uses the distinction between
212 the two to convey information. Lynx tries to detect this automatically,
213 but if it fails (for instance, you are running under "screen"), try
214 setting the -noreverse commandline option.
215
216 ---------
217
218 On VMS, Lynx, and other TCP-IP software, have been experiencing chronic
219 problems of incompatibilities between DECC and MultiNet headers whenever
220 new versions of either DECC or MultiNet are released. The Lynx build
221 procedure for VMS and a maze of spaghetti #ifdef-ing in tcp.h of the
222 libwww-FM had previously been successful in dealing with this problem
223 across all versions of MultiNet and of DECC, VAXC, and Pat Rankin's
224 VMS port of GNUC, but are now not 100% successful. If you get compiler
225 messages about "struct timeval timeout" having no linkage, add that
226 declaration immediately below the inclusion of ioctl.h for MultiNet in
227 tcp.h (by deleting the "#ifdef NOT_DEFINED" and "#endif /* NOT_DEFINED */"
228 lines):
229 [...]
230 #include "multinet_root:[multinet.include.sys]ioctl.h"
231 struct timeval {
232 long tv_sec; /* seconds since Jan. 1, 1970 */
233 long tv_usec; /* microseconds */
234 };
235 [...]
236 If you get compiler warnings about incompatible multinet_foo()
237 declarations, delete those where indicated in tcp.h. For the most
238 current versions of MultiNet, you can modify tcp.h to use the DECC
239 socket and related headers.
240
241 On VMS, the ftp function does not work with SOCKETSHR 0.9D and NETLIB
242 2 (NETLIB 1 may work). This is because the functions getsockname()
243 and getpeername() within SOCKETSHR make incorrect calls to the NETLIB
244 functions. This results in zeroes being returned for part of the local
245 IP address. Since ftp sends this IP address to the remote end, the
246 remote server ends up sending a file back to a non-existent address.
247 Andy Harper (A.HARPER@kcl.ac.uk) has fixed these problems in the
248 SOCKETSHR 0.9D sources and offers the fixes as:
249 http://alder.cc.kcl.ac.uk/fileserv/zip/socketshr_src_09d-2.zip
250 ftp://ftp2.kcl.ac.uk/zip/socketshr_src_09d-2.zip
251
252 ---------
253
254 On VMS, to build an SSL-capable version, lynx and the ssl library
255 e.g., OpenSSL, must be built using the same network library. If you
256 build OpenSSL without specifying the network library (the 5th parameter
257 of the makevms.com script), it will guess, possibly not the one you
258 intended. We have tested only the UCX configuration -TD (2002/9/15).