lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev [PATCH][dev22] Fix --disable-trace, #includes


From: Henry Nelson
Subject: Re: lynx-dev [PATCH][dev22] Fix --disable-trace, #includes
Date: Mon, 19 Apr 1999 11:31:56 +0900 (JST)

> we'll have to rephrase all of the CTRACE macros.  (I'd rather concentrate
> on finishing off the dangling stuff for 2.8.2 than change 1400 lines of code)

Recommended the following actions previously.  Especially, since manual
configuration on Un*x is no longer supported, and the fact that the docs/
*.old files are so out of date that they are useless, I hope they will be
removed.  Mention of them is removed from INSTALLATION with the following
patch.  The following patch also makes in addition to cosmetic changes:
    1) rewording of the sentences concerning NLS
    2) a better description of how to test Lynx before installing it (Un*x).

__Henry

Perhaps not this time around, but eventually:
mv lynx2-8-2/LYMessages_en.h lynx2-8-2/src/LYMessages_en.h

Definitely before a release:
rm lynx2-8-2/docs/*.old

Hopefully before a release, apply this patch:
*** lynx2-8-2/INSTALLATION.dist Mon Apr 19 10:06:41 1999
--- lynx2-8-2/INSTALLATION      Mon Apr 19 11:01:29 1999
***************
*** 2,27 ****
                        Lynx Installation Guide
  
  This file describes how to compile and install Lynx.  A description of Lynx
! can be found in the README file.  Lynx has been ported to UN*X, VMS,
! Win32 and 386DOS.  The procedures for compiling these ports are quite
! divergent and are detailed respectively in Sections II, III, IV and V.
! General installation, problem solving and environment variables are covered
! in Sections VI and VII.  There is also a PROBLEMS file in the same directory
! as this INSTALLATION: it contains advice for a lot of special problems
! people have encountered, esp for particular machines & operating systems.
  
  If you don't understand what one of the defines means, try the README.defines
  and *.announce files in the docs subdirectory.  The docs/CHANGES* files record
  the entire development history of Lynx and are an invaluable resource for
  understanding how Lynx should perform.
  
- If you still have difficulties, send an e-mail message to the Lynx-Dev mailing
- list address@hidden (see the README file).  Try to include information about
- your system, the name and version of your compiler, which curses library you
- are using and the compile-time errors.  Be sure to say what version and
- image-number of Lynx you are trying to build (alternately the top date of the
- CHANGES file).
- 
  First, you must configure Lynx for your system regardless of the port you will
  be using.  Follow the instructions given immediately below to configure for
  your system, and then go to the respective section concerning the port you 
wish
--- 2,26 ----
                        Lynx Installation Guide
  
  This file describes how to compile and install Lynx.  A description of Lynx
! can be found in the README file.  Lynx has been ported to UN*X, VMS, Win32
! and 386DOS.  The procedures for compiling these ports are quite divergent
! and are detailed respectively in Sections II, III, IV and V.  General
! installation, problem solving and environment variables are covered in
! Sections VI and VII.  There is also a PROBLEMS file in the same directory
! as INSTALLATION which contains advice for special problems people have
! encountered, especially for particular machines and operating systems.
  
+ If you still have difficulties, send an e-mail message to the Lynx-Dev mailing
+ list (see the README file).  Try to include information about your system,
+ the name and version of your compiler, which curses library you are using
+ and the compile-time errors.  Be sure to say what version and image-number
+ of Lynx you are trying to build (alternately the top date of the CHANGES 
file).
+ 
  If you don't understand what one of the defines means, try the README.defines
  and *.announce files in the docs subdirectory.  The docs/CHANGES* files record
  the entire development history of Lynx and are an invaluable resource for
  understanding how Lynx should perform.
  
  First, you must configure Lynx for your system regardless of the port you will
  be using.  Follow the instructions given immediately below to configure for
  your system, and then go to the respective section concerning the port you 
wish
***************
*** 30,47 ****
  
  I. General configuration instructions (all ports).
  
! Step 1. (define compile-time variables -- See the userdefs.h file.)
      There are a few variables that MUST be defined, or Lynx will not build.
      There are a few more that you will probably want to change.  The variables
      that must be changed are marked as such in the userdefs.h file.  Just edit
!     this file, and the changes should be straight forward.  Many of the
!     variables in "userdefs.h" are now configurable in the lynx.cfg file, so
!     you may set them at run-time if you wish.  If you compile using auto-
!     configure, you would not absolutely need to edit "userdefs.h".  Check
!     LYMessages_en.h for tailoring the Lynx statusline prompts, messages and
!     warnings to the requirements of your site.  Lynx implements Native
!     Language Support.  Read "ABOUT-NLS" if you are interested in building an
!     international version of Lynx.
  
  Step 2. (define run-time variables -- See the lynx.cfg file for details.)
      Set up local printers, downloaders, assumed character set, key mapping,
--- 29,45 ----
  
  I. General configuration instructions (all ports).
  
! Step 1. (define compile-time variables)
      There are a few variables that MUST be defined, or Lynx will not build.
      There are a few more that you will probably want to change.  The variables
      that must be changed are marked as such in the userdefs.h file.  Just edit
!     this file, and the changes should be straight forward.  If you compile
!     using autoconfigure, you should set defines with option switches and not
!     edit userdefs.h directly.  Many of the variables in userdefs.h are now
!     configurable in the lynx.cfg file, so you may set them at run-time if you
!     wish.  Lynx implements Native Language Support.  Read "ABOUT-NLS" if you
!     want to build an international version of Lynx or tailor the statusline
!     prompts, messages and warnings to the requirements of your site.
  
  Step 2. (define run-time variables -- See the lynx.cfg file for details.)
      Set up local printers, downloaders, assumed character set, key mapping,
***************
*** 54,69 ****
      section below), specified with an environment variable, LYNX_CFG, or
      specified with the "-cfg" command line option.
  
! Step 3. (You may skip this step if you only use English and are not
!     interested in any special characters, or if your display and local files
!     will all use the ISO-8859-1 "ISO Latin 1" Western European character set.)
!     People who will be running Lynx in an environment with different and
!     incompatible character sets should configure CHARACTER_SET (the Display
!     character set) and ASSUME_LOCAL_CHARSET to work correctly for them before
!     creating bookmark files et cetera.  Please read "lynx.cfg" for detailed
!     instructions.  Additional character sets and their properties may be
!     defined with tables in the src/chrtrans directory, see the README.* files
!     therein.
  
  Step 4. (optional -- news for UNIX and VMS)
      Set NNTPSERVER in "lynx.cfg" to your site's NNTP server, or set the
--- 52,66 ----
      section below), specified with an environment variable, LYNX_CFG, or
      specified with the "-cfg" command line option.
  
! Step 3. (You may skip this step if you use only English and are not interested
!     in any special characters, or if your display and local files will all use
!     the ISO-8859-1 "ISO Latin 1" Western European character set.) People who
!     will be running Lynx in an environment with different and incompatible
!     character sets should configure CHARACTER_SET (the Display character set)
!     and ASSUME_LOCAL_CHARSET to work correctly for them before creating
!     bookmark files et cetera.  Read "lynx.cfg" for detailed instructions.
!     Additional character sets and their properties may be defined with tables
!     in the src/chrtrans directory, see the README.* files therein.
  
  Step 4. (optional -- news for UNIX and VMS)
      Set NNTPSERVER in "lynx.cfg" to your site's NNTP server, or set the
***************
*** 469,476 ****
  
      I personally use the following csh shell script to set environment
      variables and configure options rather than type them each time.
-       setenv RESOLVLIB -lbind
- 
        #!/bin/csh -f
        setenv CPPFLAGS "-I$HOME/slang -I$HOME/.usr/include"
        setenv LIBS "-L$HOME/.slang/lib -L$HOME/.usr/lib"
--- 466,471 ----
***************
*** 478,503 ****
                --mandir=$HOME/.usr/man --libdir=$HOME/.usr/lib \
                --with-screen=slang --with-zlib
  
!     The syntax for setting environment variables depends upon your shell.  I
!     use the libbind.a resolver library, not libresolv.a.  Setting RESOLVLIB to
!     -lbind defines this environment variable for `make', and thus must be set
!     in the same shell that `make' will be run.  CPPFLAGS in this example
!     defines the full path to the slang and zlib header files, which are not
!     kept in standard directories.  Likewise, LIBS defines the nonstandard
!     locations of libslang.a and libz.a.  Setting the option --bindir tells
!     the configure script where I want to install the lynx binary; setting
!     --mandir tells it where to put the lynx.1 man page, and setting --libdir
!     tells it (while at the same time defining LYNX_CFG_FILE) where to put the
!     configuration file "lynx.cfg", when I type "make install".  The
!     --with-screen=slang and --with-zlib options are explained above.
  
! 2. Manual compile
!     If auto-configure does not work for you, or you prefer to compile
!     Lynx manually, "docs/Makefile.old" will serve as a template for the
!     top-level Makefile, and instructions on how to compile are given in
!     "docs/INSTALLATION.old".
! 
! 3. Wais support (optional)
      To add direct WAIS support, get the freeWAIS distribution from
      "ftp://ftp.cnidr.org/pub/NIDR.tools/freewais";, and compile it.  The 
compile
      process will create the libraries you will need, wais.a and client.a.  
Edit
--- 473,488 ----
                --mandir=$HOME/.usr/man --libdir=$HOME/.usr/lib \
                --with-screen=slang --with-zlib
  
!     CPPFLAGS in this example defines the full path to the slang and zlib 
header
!     files, which are not kept in standard directories.  Likewise, LIBS defines
!     the nonstandard locations of libslang.a and libz.a.  Setting the option
!     --bindir tells the configure script where I want to install the lynx
!     binary; setting --mandir tells it where to put the lynx.1 man page, and
!     setting --libdir tells it (while at the same time defining LYNX_CFG_FILE)
!     where to put the configuration file "lynx.cfg", when I type "make 
install".
!     The --with-screen=slang and --with-zlib options are explained above.
  
! 2. Wais support (optional)
      To add direct WAIS support, get the freeWAIS distribution from
      "ftp://ftp.cnidr.org/pub/NIDR.tools/freewais";, and compile it.  The 
compile
      process will create the libraries you will need, wais.a and client.a.  
Edit
***************
*** 703,710 ****
    #define getmaxx(w)              (w)->_maxx
    #define getmaxy(w)              (w)->_maxy
  
!     If you have trouble applying the patch, we recommend that you use the
!     "patch" program,
      ("http://www.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/pat25b.zip";).  The
      WATTCP TCPLIB sources must also be patched prior to compilation.  See
      "http://www.flora.org/lynx-dev/html/month1197/msg00403.html";.
--- 688,694 ----
    #define getmaxx(w)              (w)->_maxx
    #define getmaxy(w)              (w)->_maxy
  
!     If you have trouble applying the patch, try using the "patch" program,
      ("http://www.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/pat25b.zip";).  The
      WATTCP TCPLIB sources must also be patched prior to compilation.  See
      "http://www.flora.org/lynx-dev/html/month1197/msg00403.html";.
***************
*** 768,774 ****
      "ftp://ftp.agate.net/users/01935/internet/dosppp06.zip";;
      "ftp://ftp.klos.com/demo/pppshare.exe";.)
  
- 
      File access looks like this:
  
      file:///c:/
--- 752,757 ----
***************
*** 810,818 ****
  
  VI. General installation instructions
  
!     Once you have compiled Lynx, test it out on "lynx_help/about_lynx.html".
!     You shouldn't need to install Lynx to test it.  Once you are satisfied
!     that it works, go ahead and install Lynx.  For Unix, type "make install".
  
      For VMS, you need to have the executable in a public place, make it
      accessible, define it as a foreign command, and copy lynx.cfg to
--- 793,802 ----
  
  VI. General installation instructions
  
!     Once you have compiled Lynx, test it out first on a local file.  Be sure
!     Lynx can find lynx.cfg.  A _sample_ test command line would be:
!     `lynx -cfg=/usr/local/lib/lynx.cfg .`  Once you are satisfied that
!     Lynx works, go ahead and install it.  For Unix, type "make install".
  
      For VMS, you need to have the executable in a public place, make it
      accessible, define it as a foreign command, and copy lynx.cfg to
***************
*** 850,859 ****
     after you have installed Lynx.
  
  2. Win32 (95/NT) and 386 DOS
-    These ports cannot start before setting certain environment variables
  
!    (adapted from "readme.txt" by Wayne Buttles and "readme.dos" by Doug 
Kaufman)
! 
      Here are some environment variables that should be set, usually in a
      batch file that runs the lynx executable.  Make sure that you have enough
      room left in your environment.  You may need to change your "SHELL="
--- 834,841 ----
     after you have installed Lynx.
  
  2. Win32 (95/NT) and 386 DOS
  
!     These ports cannot start before setting certain environment variables.
      Here are some environment variables that should be set, usually in a
      batch file that runs the lynx executable.  Make sure that you have enough
      room left in your environment.  You may need to change your "SHELL="
***************
*** 860,866 ****
      setting in config.sys.  In addition, lynx looks for a "SHELL" environment
      variable when shelling to DOS.  If  you wish to preserve the environment
      space when shelling, put a line like this in your AUTOEXEC.BAT file also
!     "SET SHELL=C:\COMMAND.COM /E:2048". It should match CONFIG.SYS.
  
      HOME         Where to keep the bookmark file and personal config files.
      TEMP or TMP  Bookmarks are kept here with no HOME.  Temp files here.
--- 842,848 ----
      setting in config.sys.  In addition, lynx looks for a "SHELL" environment
      variable when shelling to DOS.  If  you wish to preserve the environment
      space when shelling, put a line like this in your AUTOEXEC.BAT file also
!     "SET SHELL=C:\COMMAND.COM /E:2048".  It should match CONFIG.SYS.
  
      HOME         Where to keep the bookmark file and personal config files.
      TEMP or TMP  Bookmarks are kept here with no HOME.  Temp files here.
***************
*** 879,885 ****
        set lynx_cfg=d:\win32\lynx.cfg
        d:\win32\lynx.exe %1 %2 %3 %4 %5
  
!     In lynx_386, a typical batch file might look like:
  
        @echo off
        set HOME=f:/lynx2-8
--- 861,867 ----
        set lynx_cfg=d:\win32\lynx.cfg
        d:\win32\lynx.exe %1 %2 %3 %4 %5
  
!     For lynx_386, a typical batch file might look like:
  
        @echo off
        set HOME=f:/lynx2-8
***************
*** 888,897 ****
        set WATTCP.CFG=%HOME%
        f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9
  
!     You will also need to make sure that the WATTCP.CFG file has the
!     correct information for IP number, Gateway, Netmask, and Domain Name
!     Server.  This can also be automated in the batch file.
  
  
  VIII. Acknowledgment
  
--- 870,880 ----
        set WATTCP.CFG=%HOME%
        f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9
  
!     You need to make sure that the WATTCP.CFG file has the correct information
!     for IP number, Gateway, Netmask, and Domain Name Server.  This can also be
!     automated in the batch file.
  
+     Adapted from "readme.txt" by Wayne Buttles and "readme.dos" by Doug 
Kaufman.
  
  VIII. Acknowledgment
  

reply via email to

[Prev in Thread] Current Thread [Next in Thread]