Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!RED.RUTGERS.EDU!AWalker
From: AWalker@RED.RUTGERS.EDU (*Hobbit*)
Newsgroups: comp.os.vms
Subject: linking against RTLs
Message-ID: <12322163796.34.AWALKER@RED.RUTGERS.EDU>
Date: Wed, 29-Jul-87 03:47:20 EDT
Article-I.D.: RED.12322163796.34.AWALKER
Posted: Wed Jul 29 03:47:20 1987
Date-Received: Sun, 2-Aug-87 03:18:20 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 21

[Apparently my first msg about this got lost.]

I want to link images that reference VMSRTL and LIBRTL such that the
code I use from the library winds up *in the image*, not simply mapped
at activation time.  This is so the resultant image can be run on a site
with a lower version of VMS.  [No flames about why you shouldn't do that --
if the image doesn't use newer system calls or the like it'll be fine.]
I've ding near shredded the linker manual trying to find out how to
convince LINK to include the code in my image.  Can it be done, and if
so, how??  The idea here is to generate images that have *no* shared-library
dependencies and can run "anywhere" [in the 4.x universe, I suppose].

Quickie WRT sys$announce and legal issues:  Probably the best idea is
to use sys$announce to tell people which box they're talking to [i.e. just
the name of the facility or something] and use sys$*welcome* for just
that -- once they've legally and properly logged in, *then* welcome them
with open arms and long announcements.  Everyone else can only see a little
bit of writing on the cold wall that keeps them out...

_H*
-------