Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!rti-sel.UUCP!rcb From: rcb@rti-sel.UUCP (Random) Newsgroups: mod.computers.vax Subject: Re: VAX C Message-ID: <8611261429.AA03264@rti-sel> Date: Wed, 26-Nov-86 09:29:12 EST Article-I.D.: rti-sel.8611261429.AA03264 Posted: Wed Nov 26 09:29:12 1986 Date-Received: Fri, 28-Nov-86 20:24:25 EST References: <8611250928.AA27001@ucbvax.Berkeley.EDU> Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: RandomOrganization: Research Triangle Institute, RTP, NC Lines: 28 Approved: info-vax@sri-kl.arpa In article <8611250928.AA27001@ucbvax.Berkeley.EDU> XSAK@IECMICC.BITNET (Samir Kaleem) writes: > >I installed VAX C, and checked everything was in the proper place. Sure enough, >everything looked fine. However, according to the linking procedure, a file >should exist in SYS$LIBRARY called VAXCRTL.OLB. This file is nowhere to be >found. It isn't mentioned as one of the files to be installed, but only >mentioned in the section that describes Linking. Ofcourse the linker needs >this file to Link any programs. Does anyone know anything about this? I wish >that DEC was a little more clearer in their documentation. Or maybe this is >some file that they forgot to put in the in instalation cartridge. > >Also, in the documenatation, they say that if you don't want to DEFINE the >OLBs, then an option file can be created which has SYS$SHARE:VAXCRTL.EXE/SHARE >in it. Again, there is no such file (VAXCRTL.EXE) in SYS$SHARE. Where the >heck do they come up with this nonsense documentation anyway? I think a call >to them is necessary, but it is not in my place to do this. I've informed my >instructor (I'm only a student working on the VAX for an independent study >class), but he seems to be preoccupied elsewhere to do much about this matter. >Oh well, hopefully I'll get some help from you all again. > The documentation is correct. You installation is not. I assume that you are installing C V2.0 or later. If not, then all bets are off. VAXCRTL.OLB should have been installed in sys$share if the installation succeeded. VAXCRTL.EXE is put in SYS$SHARE by VMS installation. It should therefore, always be there. This applies to VMS V4.2 (i think) and later. You might want to have someone who is more familiar with installing software to check this out.