home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!ukma!asuvax!ncar!uchinews!gsbacd.uchicago.edu!cs_mj
- From: cs_mj@gsbacd.uchicago.edu (Mark Jaeger)
- Subject: Re: Gnu C++ and INGRES
- Message-ID: <1992Nov18.142628.1@gsbacd.uchicago.edu>
- Followup-To: gcc.help
- Lines: 39
- Sender: news@uchinews.uchicago.edu (News System)
- Organization:
- References: <1992Nov17.133746.1439@dct.ac.uk>
- Date: Wed, 18 Nov 1992 20:26:28 GMT
-
- In article <1992Nov17.133746.1439@dct.ac.uk>, mcsmijq@dct.ac.uk writes:
-
- > Does anyone know how to link gnu C++ to INGRES on a VAX cluster. It,s easy
- > enough using the link command with a vaxc obj file but what's the syntax using
- > cxshare?
-
- I don't quite know what cxshare is, but if it is a shareable runtime
- library (similar to the file sys$share:vaxcrtl.exe that is supplied with
- either VMS or VAX C), then you could link your program in either of two
- ways:
-
- $ cc foo.c
- $ link foo.obj,sys$input: /opt
- gnu$lib:cxshare.exe /share
- ^Z
-
- or
-
- $ cc foo.c
- $ link foo.obj,foo.opt /opt
-
- where foo.opt contains this line:
-
- gnu$lib:cxshare.exe /share
-
- You'll have to adjust the name of "gnu$lib" for your site.
-
- Shareable runtime libraries in VMS have the great advantages of (1)
- making your images much, much smaller, thereby saving disk space and
- reducing image activation time; and (2) reducing memory usage at runtime
- since there need be only one copy of the shareable image in physical
- memory for all users.
-
- --Mark Jaeger internet: cs_mj@gsbvax.uchicago.edu
- Graduate School of Business yellnet: (312) 702-0328
- University of Chicago faxnet: (312) 702-0233
- Disclaimer: My opinions are my own and not those of my employer.
- Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.
-
-