Re: Cleaning up DEC-C includes
- From: huber@xxxxxxxxxxxxxxxxxxxx (Joseph Huber)
- Date: 14 Jul 2006 10:33:49 +0200
In article <44B73507.F0203037@xxxxxxxxxxxx>, JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx> writes:
I seem to have mismatched version of the C compiler includes on my nodes.
This is on a node that used to have VAXC. But I have eliminated the
VAXC$COMPILER as well as changed the CC command to one which was on a
node which never had VAXC (to eliminate the VAXC option).
But I find out that I still have some vaxC stuff:
$ dir/nohead $disk1:[vms$common...]starlet.h
$DISK1:[VMS$COMMON.DECC$LIB.REFERENCE.DECC$RTLDEF]STARLET.H;1
$DISK1:[VMS$COMMON.DECC$LIB.REFERENCE.SYS$STARLET_C]STARLET.H;1
$DISK1:[VMS$COMMON.SYSLIB.VAXC$INCLUDE]STARLET.H;1
(this, on top of all the .TLBs which have copies too).
Is it OK to delete the whole SYSLIB.VAXC$INCLUDE directory and all the
files in it ? They seem to be very old ???
The DECC$LIB.REFERENCE files are the files extracted from the *.TLB files at
compiler installation time, optional, and for reference only.
DECC never uses them unless explicitly asked to (via /INCLUDE or some
DECC$*INCLUDE* logical).
You can safely delete all of them (and re-install with a newer compiler version
if You wish).
The VAXC$INCLUDE files can probably also be deleted since You removed the VAX C
compiler (but I no longer have a VAX to test it ).
--
Joseph Huber , Muenchen,Germany: http://www.huber-joseph.de/
.
- References:
- Cleaning up DEC-C includes
- From: JF Mezei
- Cleaning up DEC-C includes
- Prev by Date: Re: Parsec webinar (2006-07-12) OpenVMS Licensing
- Next by Date: Re: The possibility of vms opening up?
- Previous by thread: Cleaning up DEC-C includes
- Next by thread: bypass ds20e OCP faulty module
- Index(es):
Relevant Pages
|