lynx-dev
[Top][All Lists]
Advanced

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

Re: LYNX-DEV Newbie(installing)


From: Larry W. Virden, x2487
Subject: Re: LYNX-DEV Newbie(installing)
Date: Thu, 13 Feb 1997 07:40:24 -0500

Re: user is 'new to this' and has been assigned the task of setting up lynx
Re: for a library.

1. Check out from interlibrary loan the book "The UNIX Programming Environment"
and read it.  This will give you an intro to Unix from a programming
perspective.

2. Check out from interlibrary loan the book "Porting UNIX Software" and
read it.  This will discuss using zip, make, etc.

3. You will need the following tools:  unzip, editor of some sort,
make, cc, /bin/sh, ranlib (possibly), cp, install (possibly), compress,
gunzip, uudecode, gzcat, gzip, zip, mkdir, mv, rm, tar, touch, cp, and
chmod.  Also, you may need the slang, ncurses, and/or SOCKS library.
Also, you will need the helper applications tn3270 and xloadimage.

3. Create a directory where you have space to build the softare.  You will
need approximately 15-30 meg of disk.  Decide where you are going to install
lynx.  You will likely need up to 4 meg or so for this (depends on the compile
options, options chosen, etc.)  If you can get permission to install in the
/usr/local set of directories, your job will become _MUCH_ easier...

You will need a structure that looks like this:

PREFIX = /usr/local

PREFIX/bin/             <- lynx gets installed here
PREFIX/lib/             <- lynx.cfg gets installed here
PREFIX/man/man1/        <- lynx.1 man page

PREFIX/lib/lynx_help/   <- lynx help files should be installed here
PREFIX/lib/mosaic/      <- mime.types and mailcap should be installed here

4. put the .zip file in this directory.  unzip it.  You now have 2 files in
your directory - the .zip file, and a directory called lynx2-7 (or something
like that).

5. cd lynx2-7

6. Read the README file.  Read it again.

7. Read the INSTALLATION file.  Read it again.

8. Read the PROBLEMS file.  See if the version of your HP/UX matches any
of the HP/UX versions mentioned.

9. Make a copy of the userdefs.h (call it userdefs.h.orig).

10. Make a copy of the Makefile (call it Makefile.orig perhaps).

11. Make a copy of the lynx.cfg file (call it lynx.cfg.orig).

12. Read, and then edit, the userdefs.h file.  Decide what, if any, of
the options you would like, or need, to change.   If you are NOT
installing into /usr/local, there are various directory names you will
need to change.  Also, you should specify a default STARTFILE url where
users will start if they do not have a web home page, your LOCAL_DOMAIN
needs to be set, and at the bottom of the file, check the pathnames to
ensure that your utilities are all where you expect them to be.

13. Read, and then edit, the Makefile.  The primary lines you might have to edit
are the exec, doc and cfg lines.  For certain systems, or options, you will
have to uncomment some of the Makefile comments - there are comments to let
you know which ones to uncomment.  The tricky part is to determine which
ones you will eventually want to mess with.

Be sure to read all the references to HP/UX.  There are 3 different HP/UX
environments in the Makefile.  They appear to relate to the version of the
OS.  I don't know how to determine which one you need to use, unless using
uname -a tells you what version of HP/UX you are using.

14.  At this step, I recommend trying the compile.  From the lynx2-7
directory, type

nohup make > make.out 2>&1

if you are using a Bourne/Korn shell.  This captures all of the output
from the make into a file.  This will come in handy since you will want
to look for warnings, errors, etc. after the make completes.

If there are problems, the most likely places they occur are:

a. You need some directory in your PATH variable so that you can find
make, cc, or some other piece during the process.

b. You have a typo in userdefs.h or the Makefile.

c. You tried to turn on an option but the accompanying library is not present.

d. Your version of the OS is different from the ones currently supported.

If you have case 4, drop a line to lynx-dev to see if anyone else has
the fixes for this.

15. When the compilation succeeds, type

./lynx http://lynx.browser.org/

and you should see the lynx home page.  I would show you a sample, but
it appears to be down right now.


Okay - that's the general build process (perhaps it belongs in a beginner
file somewhere on the web?).

Someone want to do something this simple for the person that covers the
security issues?
-- 
Larry W. Virden                 INET: address@hidden
<URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

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