- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DEC C V6.0 vs 6.4 command-lines
Operating System - OpenVMS
1753316
Members
5022
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2003 06:48 AM
тАО05-13-2003 06:48 AM
Hi all,
I'm currently shipping an application, which is distributed as source code and compiled by the end-user as part of the installation process. The code in question has a lot of statements that generate the %CC-W-PTRMISMATCH warning under DEC Cv6.0; to stop this breaking the compile, I've added /WARNINGS=(DISABLE=PTRMISMATCH) to the compiler command line. However, it seems that some time after V6.0 (I've noticed this behaviour on 6.4 at least), the warning in question changed to %CC-W-PTRMISMATCH1, and is no longer disabled by this command line; customers using V6.4 are then not able to build the source.
I've considered a couple of solutions to this; either checking the version of the compiler in the installation DCL procedure, and setting an MMS/MMK variable to change the command line passed to the compiler, or generating a CC.COM before build which includes the correct command line.
However, I'm not sure how to go about either of these; in particular, although CC/VERSION prints the compiler's version number, is there a way to 'catch' this in a DCL symbol to use?
Any hints or other ideas for a solution would be appreciated :).
(Before anyone says "fix the warnings in the code".. yes, I'd like to do that, but the non-VMS parts of the code weren't written by me, and I'd like to avoid changing that; the changes to fix all occurances of this warning would proably require rewriting half the software :(. )
I'm currently shipping an application, which is distributed as source code and compiled by the end-user as part of the installation process. The code in question has a lot of statements that generate the %CC-W-PTRMISMATCH warning under DEC Cv6.0; to stop this breaking the compile, I've added /WARNINGS=(DISABLE=PTRMISMATCH) to the compiler command line. However, it seems that some time after V6.0 (I've noticed this behaviour on 6.4 at least), the warning in question changed to %CC-W-PTRMISMATCH1, and is no longer disabled by this command line; customers using V6.4 are then not able to build the source.
I've considered a couple of solutions to this; either checking the version of the compiler in the installation DCL procedure, and setting an MMS/MMK variable to change the command line passed to the compiler, or generating a CC.COM before build which includes the correct command line.
However, I'm not sure how to go about either of these; in particular, although CC/VERSION prints the compiler's version number, is there a way to 'catch' this in a DCL symbol to use?
Any hints or other ideas for a solution would be appreciated :).
(Before anyone says "fix the warnings in the code".. yes, I'd like to do that, but the non-VMS parts of the code weren't written by me, and I'd like to avoid changing that; the changes to fix all occurances of this warning would proably require rewriting half the software :(. )
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2003 07:18 AM
тАО05-13-2003 07:18 AM
Re: DEC C V6.0 vs 6.4 command-lines
sys$system:decc$show_versions.com
might prove instructive as how to find the version number in a
general way (/version was not
supported on all versions).
Generally speaking I still think
it would be a good idea to fix the code.
might prove instructive as how to find the version number in a
general way (/version was not
supported on all versions).
Generally speaking I still think
it would be a good idea to fix the code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2003 09:24 AM
тАО05-13-2003 09:24 AM
Solution
If there is an include file that will be included in all the affected code, you could put in something like:
#ifdef __VMS
/* FIXME -- Please fix the code so
* this desperate suppression of
* error messages is unnecessary.
*/
#if defined (__DECC_VER) && __DECC_VER >= 60400000
#pragma message disable PTRMISMATCH1
#else
#pragma message disable PTRMISMATCH
#endif
#endif
#ifdef __VMS
/* FIXME -- Please fix the code so
* this desperate suppression of
* error messages is unnecessary.
*/
#if defined (__DECC_VER) && __DECC_VER >= 60400000
#pragma message disable PTRMISMATCH1
#else
#pragma message disable PTRMISMATCH
#endif
#endif
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2003 11:54 AM
тАО05-13-2003 11:54 AM
Re: DEC C V6.0 vs 6.4 command-lines
Thanks, #pragma message disable does exactly what I require :).
(Yes, the code should be fixed, and I've left Craig's comment in the source because of this.
Unfortunately I really don't have time to do it myself, and the author of the code in question doesn't consider it enough of a problem to warrant fixing it when there's other more pressing problems to deal with.
Without being able to change the source, I think this workaround is a reasonable solution.)
Thanks again for the help. :)
(Yes, the code should be fixed, and I've left Craig's comment in the source because of this.
Unfortunately I really don't have time to do it myself, and the author of the code in question doesn't consider it enough of a problem to warrant fixing it when there's other more pressing problems to deal with.
Without being able to change the source, I think this workaround is a reasonable solution.)
Thanks again for the help. :)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP