[Top][All Lists]

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

Re: [Lynx-dev] Lynx 2.8.5 build failure on VMS 7.3 with TCPIP

From: Thomas Dickey
Subject: Re: [Lynx-dev] Lynx 2.8.5 build failure on VMS 7.3 with TCPIP
Date: Sat, 30 Jun 2007 08:04:41 -0400 (EDT)

On Sat, 30 Jun 2007, dominic stephens wrote:

Dear Thomas, Thanks for the reply. SYS$COMMON:[SYSLIB]UCX$IPC.OLB doesn't exist hence the origional error but SYS$COMMON:[SYSLIB]TCPIP$IPC.OLB doesnt exist either. There is a file SYS$COMMON:[SYSLIB]TCPIP$IPC_SHR.exe (and a corresponding UCX version SYS$COMMON:[SYSLIB]UCX$IPC_SHR.exe) plus SYS$COMMON:[SYSLIB]TCPIP$INETDEF.H

That's promising.  You can get a listing of the library's module names
(I don't know about entrypoint names) using the library command.

Since VMS lacks a "strings" command, I generally get some information
using the binary mode in flist (on my ftp area).  It's a little rusty,
but very useful for browsing the filesystem.

Some (I could post the full list if req.) of the TCPIP logicals are:

The full list might help (but bear in mind that I'd be guessing). It's been a few months since I used the HP testdrive - that might still work (so I'd guess less - will see if I've time...).

The four variables you're citing are all directory names (ending with "]").

I am currently playing with batch files and their logs but haven't a clue how to re link (or indeed if it's possible) using TCPIP$IPC_SHR.exe rather than UCX$IPC.OLB etc. Would any of the code or compile instructions need changing as well? Thanks again for any advice. Cheers - Dominic

You wouldn't want to  or need to relink the library.

The "shr.exe" files are generally VMS's shared libraries, like M$ dll's.
The ".olb" files are the static libraries (or import libraries if there's
a shared library).

From: Thomas Dickey <address@hidden>
To: dominic stephens <address@hidden>
CC: address@hidden
Subject: Re: [Lynx-dev] Lynx 2.8.5 build failure on VMS 7.3 with TCPIP
Date: Thu, 28 Jun 2007 14:57:08 -0400 (EDT)

On Thu, 28 Jun 2007, dominic stephens wrote:

Dear All, I'm trying to build Lynx 2.8.5 on OpenVMS v7.3 with (DEC/Compaq/HP) TCPIP services v5.1-5 on a simh simulated vax with compaq C v6.4. It fails with the following message:

[-.WWW.Library.Implementation]WWWLib_UCX.olb/library, -
sys$disk:[]UCXOLB.opt/opt, sys$disk:[]VAXC.opt/opt
%LINK-F-OPENIN, error opening SYS$COMMON:[SYSLIB]UCX$IPC.OLB; as input
-RMS-E-FNF, file not found

Presumably this is because I have TCPIP not the older UCX. Has anyone successfully built Lynx with TCPIP? Could anyone give me any pointers as to how I could modify to make it work?

My VMS and C knowledge is limited but I'd like to give it a go and am willing to learn. Thanks in advance. Cheers - Dominic

I guess the first thing to do is to find where the comparable headers
and libraries are.  Editing isn't _that_ simple - probably
the hardest part about working on VMS, since the quoted-strings don't
look much like other systems. I do the hard editing on my home box (Linux) so I can see it in color - haven't implemented that in the VMS port of vile.

The preferred way to make the change is as another case in the first parameter (p1) in the script. By reading it (and tracing - see below),
you should be able to see how to fit it in.

Finding things - usually "show logical *" ("show log *") will show useful
logical symbols.  You want to make the script use those rather
than some fixed device names. You can make DCL scripts "trace" by setting verify to a nonzero value - see

$ v0 = 0
$ v = f$verify(v0)

at the top of

If you haven't done so, learn how to use the batch command.  It's an
easy way to build things, collecting a log of the result.  (I use a
script which makes batch put the logfile in the current directory -
which it won't do by default).

Thomas E. Dickey

The next generation of Hotmail is here!

Thomas E. Dickey

reply via email to

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