Operating System - OpenVMS
1827854 Members
1702 Online
109969 Solutions
New Discussion

Re: Problem with Linker Options file on Alpha

 
SOLVED
Go to solution
John McL
Trusted Contributor

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.
John McL
Trusted Contributor

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.
John McL
Trusted Contributor

Re: Problem with Linker Options file on Alpha

Closed.