User manual APOGEE SOFTWARE APOGEE COMPILERS C & C++ & FORTRAN 77 & FORTRAN 90

[. . . ] USER'S MANUAL rs FOR e COMPILERS VAPOGEE APOGEE-CTM APOGEE-C++TM n io HIGHLY OPTIMIZING COMPILERS WITH INTRODUCTION TO KAPTM & VASTTM PREPROCESSORS & FLEXLMTM LICENSE MANAGER 4. 0 APOGEE-FORTRAN 77TM APOGEE-FORTRAN 90TM © 1990-1996 -- Apogee Software, Inc. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the express written permission of Apogee Software, Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of Apogee Software, Inc. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. [. . . ] It also places restrictions on movement of object files, which is to say that you cannot move the source file between when you compile it and when you link it. -Xtmpl=used -Xtmpl=all -Xtmpl=local -Xtmpl=retry -Xtmpl=x+noautoincl The tmpl mode names can be augmented by adding the name noautoincl. By default, if a referenced template definition has not been found, then the compiler will automatically include a source file with the same basename, if available, to try to find a template definition. For example, if "tplate. h" contains a declaration of a needed template, the compiler will try to include a source file named, say, "tplate. c" to find the template definition. This automatic inclusion mechanism may be disabled by adding the name noautoincl to the tmpl control-variable name. Page 88 Apogee User's Manual Chapter 4: Control-Variable Definitions C++ Compilation The automatic instantiation mechanism invoked with the -Xtmpl=retry switch is a "linker feedback'' mechanism. It works by providing additional information in the object file that is used by a "prelinker'' to determine which template entities require instantiation so that the program can be linked successfully. The prelinker is a separate program that detects any missing instantiations just before linking and reinvokes the compiler to create those instantiations. The linker feedback mechanism has implications for users and the 'make' process, as described below. When a program is compiled, the compiler generates a set of uniquely named symbols in the generated object file. These symbols inform the prelinker: 1) which instantiations can be done by this compilation unit, if needed, and 2) which instantiations are required by this compilation unit. The compiler also generates a . ii file (instantiation information file), whose prefix is the same as that of the source file and whose suffix is . ii. This file is generated in the same directory where the . o file is created. Neither the . ii file nor the . o file can be moved to any other directory. The . ii file contains the set of options passed to the compiler and the directory where the compiler was invoked. This file is used by the prelinker to reinvoke the compiler on the corresponding source file, if needed. Once a complete set of object files has been generated, apCC invokes the prelinker to determine whether any new instantiations are required or if any existing instantiations are no longer required. The prelinker works by looking for . ii files for each of the object files. If any instantiations are missing, the prelinker reinvokes the compiler on source files that can supply those instantiations. This process is repeated as long as more instantiations are needed and as long as the prelinker can determine a source to supply each missing instantiation. Note that instantiation of one template may create the need for other instantiations, thus requiring multiple compilations of the same source file. When no more needed instantiations can be created, the prelinker stops. Once the link process has finished (successfully or unsuccessfully), the . ii files are left behind. From then on, any recompilation of those source files (whether by the user or by the prelinker) uses the corresponding . ii files to determine which set of instantiations will be needed for the final link. [. . . ] Run lmstat -a from the host machine to verify the connection to the vendor daemon across the network. Try using telnet hostname portnum where hostname and portnum are the same as on the Server line in your licensefile. Symptom: The application program (or lmstat) gets the error "can't read data" when attempting to connect to the license-server. Page 208 Apogee User's Manual Appendix E: Installation and License Management The FLEXlm License Manager Cause: The program is able to find the license server, but it is not getting the expected data. The most likely cause for this is that you are running a v2. 1 application program (or lmstat) and a v1. 5 daemon program. [. . . ]