Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbvax!RED.RUTGERS.EDU!AWalker
From: AWalker@RED.RUTGERS.EDU.UUCP
Newsgroups: comp.os.vms
Subject: Y'all don't get it
Message-ID: <12322949899.25.AWALKER@RED.RUTGERS.EDU>
Date: Sat, 1-Aug-87 03:45:32 EDT
Article-I.D.: RED.12322949899.25.AWALKER
Posted: Sat Aug  1 03:45:32 1987
Date-Received: Wed, 5-Aug-87 03:07:32 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 20

/NOSYSSHR does *not* do what I want.  I want to *include the code from the
shareable library*, not simply exclude it.

Say I have something that calls lib$put_output, which I want to build on
a 4.5 system and then run on a 4.1 box.  [Or have somebody *else* run it,
more to the point.]  Link/nosysshr complains about undefined symbols
like lib$put_output; if I link my thing together with imagelib I *still*
get the mismatches at the 4.1 end.

Sorry if my original query wasn't clear enough.  Please understand that I'm
trying to do something that "I shouldn't"; I see no reason, however, why
I am being *prevented* from generating a downward-compatible image.  I further
don't want to hear about this being a marketing ploy for upgrading my VMS;
whether it is or not there are some people who simply don't, and I refuse
to let something as dumb as this disallow my shipping them an executable.

Short of diddling the 4.1 gsmatch flags, how do I do this?!?!

_H*
-------