| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I would like to know the official story on how DECmcc V1.2 installation works with regard to DECthreads, especiallly on VMS 5.5. DECmcc 1.2 does not use the same version of DECthreads that shipped with VMS 5.5. When we installed DECmcc T1.2.4 on VMS 5.5, it seems that the installation replaced the images that came with VMS 5.5 in sys$share. For products that are managed by DECmcc and have components that use VMS 5.5 DECthreads images, there is an incompatability problem, that we for instance, are encountering. I was wondering why MCC does not name its private DECthreads images something like MCC$CMA$*.EXE if they have to be in sys$share or why they don't get placed in some private MCC area. Thanks in advance, Phil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2489.1 | Proposed plan to address the easy problem and avoids the harder problem. | TOOK::BURGESS | Thu Mar 05 1992 15:52 | 44 | |
> I would like to know the official story on how DECmcc V1.2 installation works
> with regard to DECthreads, especiallly on VMS 5.5.
>
> DECmcc 1.2 does not use the same version of DECthreads that shipped with
> VMS 5.5. When we installed DECmcc T1.2.4 on VMS 5.5, it seems that the
> installation replaced the images that came with VMS 5.5 in sys$share.
> For products that are managed by DECmcc and have components that use VMS 5.5
> DECthreads images, there is an incompatability problem, that we for instance,
> are encountering.
>
Since the version of cma .h and .exe files shipped with VMS 5.5
contains lots of mcc-show-stopping-bugs, mcc is developed with
the "best available" version of cma. Tonight we will leave
cma -5e and try out cma bl9. The proposed plan is to ship DECmcc v1.2
built on cma bl9.
Problem 1. How not to replace possibly existing cma files
during the decmcc installation?
a) BMS Kit. The proposed plan is to ship 4 executables names
mcc$cma$...exe which are copied into sys$library.
b) TK Kit- which ships the set of cma .h files.
The proposed plan is copy cma .h files into
mcc_commmon:[include] directory (new directory)
and DECmcc developers on VMS would change their
cc compile commands to search this directory
before searching sys$library for .h files.
Problem 2. Compatibility problems between lp shared libraries
which are built with different and incompatible versions of
CMA.
solution = ????
\Pete
| |||||
| 2489.2 | The Proposed Plan to Problem 1 is exactly what we need ! | BYBLOS::TAMER | Thu Mar 05 1992 17:28 | 23 | |
hi Pete,
Problem 1. How not to replace possibly existing cma files
during the decmcc installation?
a) BMS Kit. The proposed plan is to ship 4 executables names
mcc$cma$...exe which are copied into sys$library.
b) TK Kit- which ships the set of cma .h files.
The proposed plan is copy cma .h files into
mcc_commmon:[include] directory (new directory)
and DECmcc developers on VMS would change their
cc compile commands to search this directory
before searching sys$library for .h files.
The proposed solution to problem 1 is exactly what we need. We think this will
solve our (DECmcc and QMS) incompatibility problems. We strongly hope that
this is the plan that ships with DECmcc V1.2. Thanks.
Phil
| |||||