HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Problem with Linker Options file on Alpha
Operating System - OpenVMS
1827854
Members
1702
Online
109969
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
Forums
Discussions
Discussions
Discussions
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
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
04-14-2009 03:23 PM
04-14-2009 03:23 PM
Re: Problem with Linker Options file on Alpha
Thanks Hartmut but the automated procedures assume that all modules should be listed and while I can create a program-specific Linker options files that gets merged with any other options files (and with a generic options file), using "cluster=" is of no value. I also can't set up an independent .OLB because all code gets processed by this automated procedure.
I've had the okay to modify the automated procedures to allow a Linker options to be specified in an associated file. We already do this for compiler options so I'm just extending that to the Linker. This will rarely be used but at least what it does will be supported rather than a hack. (I must admit though that I like the intellectual challenge of a hack!)
If there's no more postings here that warrant a response I'll close this thread in about 24 hours time.
I've had the okay to modify the automated procedures to allow a Linker options to be specified in an associated file. We already do this for compiler options so I'm just extending that to the Linker. This will rarely be used but at least what it does will be supported rather than a hack. (I must admit though that I like the intellectual challenge of a hack!)
If there's no more postings here that warrant a response I'll close this thread in about 24 hours time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2009 09:52 PM
04-15-2009 09:52 PM
Re: Problem with Linker Options file on Alpha
I've now resolved this problem by modifying our command procedures to accept Linker qualifiers so that /SYSEXE can be added.
I've learnt a lot from this thread. My thanks to all, especially H, H, J & J.
The very brief summary for anyone reading this in the hope that it solves their own problem is ... read the Linker manual very closely, particularly the sections about ensuring correct symbol resolution and how to resolve symbols defined in the system executive.
As at the Linker manual for v8.3, these are section 6.3 and 6.4 if you are dealing with Alpha.
And with reference to the root cause of all this, the problem of logical names that contain non-printable characters, we'll send HP a formal request to cater for these situations.
I've learnt a lot from this thread. My thanks to all, especially H, H, J & J.
The very brief summary for anyone reading this in the hope that it solves their own problem is ... read the Linker manual very closely, particularly the sections about ensuring correct symbol resolution and how to resolve symbols defined in the system executive.
As at the Linker manual for v8.3, these are section 6.3 and 6.4 if you are dealing with Alpha.
And with reference to the root cause of all this, the problem of logical names that contain non-printable characters, we'll send HP a formal request to cater for these situations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2009 09:53 PM
04-15-2009 09:53 PM
Re: Problem with Linker Options file on Alpha
Closed.
- « Previous
-
- 1
- 2
- Next »
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP