Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!cbosgd!ucbvax!CSNET-RELAY.ARPA!egisin%watmath.waterloo.edu
From: egisin%watmath.waterloo.edu@CSNET-RELAY.ARPA (Eric Gisin)
Newsgroups: mod.computers.vax
Subject: Re: VAX C .OLB Files missing in MicroVMS 4.4
Message-ID: <8607092354.AA08886@ucbvax.Berkeley.EDU>
Date: Wed, 9-Jul-86 09:25:09 EDT
Article-I.D.: ucbvax.8607092354.AA08886
Posted: Wed Jul  9 09:25:09 1986
Date-Received: Thu, 10-Jul-86 22:57:54 EDT
References: <8607081432.AA10312@ngp.UTEXAS.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 25
Approved: info-vax@sri-kl.arpa

> Recently I installed MicroVMS 4.4 and VAX C 2.2 on our MicroVAX II.
> I retained the definitions for LNK$LIBRARY and LNK$LIBRARY_1, etc, so
> that the linker could find any unresolved function references in the
> VAX C object libraries.  According to the installation guide for VAX C
> these object libraries are new shipped with VMS, not VAX C.  However
> Mike O'Donnell @ LCRA

The LNK$LIBRARY names refer to object libraries (.OLB files).
What is distributed with VMS are the sharable image librarys,
SYS$LIBRARY:VAXCRTL.EXE and VAXCRTLG.EXE.  I don't know what you get with micro VMS,
but I think the C installation can build the sharable images from the object libraries.

You can link with either the C object libraries or a C sharable image library.
The latter results in much faster LINKing and smaller image files
(by about 60 blocks). A typical link with the sharable library follows:
$ Link test,sys$input:/opt
sys$library:vaxcrtl/share

Does anyone know of any reason to use the C object libraries over
the C sharable library? The C installation says you don't need the
sharable libraries and can therefor save space, but on the other
hand you can delete the object libraries and save just as much space.
(I'm not recommending that anyone actually delete sys$library:vaxc*.olb).

	Eric Gisin, egisin@waterloo.{csnet|edu}