|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 12397 (0x306d)
Types: TextFile
Notes: R1k Text-file segment
└─⟦8527c1e9b⟧ Bits:30000544 8mm tape, Rational 1000, Arrival backup of disks in PAM's R1000
└─⟦5a81ac88f⟧ »Space Info Vol 1«
└─⟦8e314f9b0⟧
└─⟦this⟧
Rational Compilation Integrator:
Alsys i386 LynxOS Extension
Release Information
Release 2_0_2
\f
Copyright 1992 by Rational
Part Number: 508-003289-002
December 1992 (Software Release 2_0_2)
Alsys is a registered trademark of Alsys.
Intel is a registered trademark of Intel Corporation.
Rational and R1000 are registered trademarks and Rational
Environment is a trademark of Rational.
UNIX is a registered trademark of AT&T.
Rational
3320 Scott Boulevard
Santa Clara, California 95054-3197
\f
Release 2_0_2
1. Overview
This release note describes Release 2_0_2 of the Rational
Compilation Integrator: Alsys i386 LynxOS Extension (Alsys i386
LynxOS RCI). This Alsys i386 LynxOS RCI release is compatible
with Release 2_0 of the Rational Compilation Integrator, referred
to as the Customizable RCI.
This note covers Alsys UNIX Ada RCI extensions issues in general,
and specifically I386_Unix_Als_Xt-specific release issues. Refer
to the Rational Compilation Integrator Release Note for general
product information.
2. RCI Components
The following Alsys i386 LynxOS RCI components are installed as
part of the release:
!Targets.Implementation.Release_I386_Unix_Als_Xt2_0_2
-- I386_Unix_Als_Xt release world
!Targets.I386_Unix_Als_Xt -- I386_Unix_Als_Xt Predefined Units
!Targets.Implementation.Rci_Customization.I386_Unix_Als_Xt
Rev2_0_Spec -- Customization views
Rev2_0_2 -- Includes templates, and
-- extensions.
For more information on installation of this product, refer to
the installation instructions delivered with this release. For
user information, refer to the RCI User's Manual and RCI Alsys
i386 LynxOS User's Guide.
3. Prerequisites
You can use this RCI extension product with the Alsys compiler on
most UNIX operating systems (with modifications to the
customization templates and extensions). The prerequisites
defined in this section are for LynxOS. Other platforms may have
different requirements.
Before you use the Alsys i386 LynxOS RCI, confirm the following
prerequisite conditions:
* LynxOS Version 2.0, Release 15 (or later) is running on the
remote Intel i386 system.
* The Alsys 386 UNIX Ada compilation system, Version 5.1 (or
later), is installed on the remote i386 system and you can
access it through your search path under the LynxOS system.
RATIONAL December 1992 1\f
Alsys i386 LynxOS RCI Release Information
* The host R1000 and remote i386 system are on the same network
and can communicate using Telnet and FTP.
* FTP and Telnet servers are running on the remote i386. If not,
the RCI cannot execute remote commands from the host.
Consult your system administrator for instructions on checking
the servers.
* The RCI is running. (After installation, the RCI starts
automatically at machine initialization.)
To start the RCI:
1. Run Start_Rci_Main to start the Rci compiler job.
2. Use I386_Unix_Als_Xt.Register to register your extension.
3. Use What.Users to list the jobs and check for the
following:
- FTP Server
- Rci_Compiler Rev2_0_5 (or later)
- Rci_Rev2_0_2_I386_Unix_Als_Xt_FTP
4. Limitations
This section describes limitations in this Alsys i386 LynxOS RCI
release.
4.1. Uploading Executable Files
The Alsys UNIX Ada RCI provides a switch, I386_Unix_Als_Xt-
_Get_Executable_File, to control whether or not the RCI should
upload the executable module to the host after a linking
operation. Set the value of this switch to True if you want to
upload the executable file from the remote compilation platform
to the host. The base RCI also provides a switch, Session_Rci-
.Retrieve_Executable, to control uploading the executable file.
Leave this switch set to its default value (False).
4.2. Compiler and Linker Pre_Options Switches
If you set the Rci.Compiler_Pre_Options (or Rci.Linker_Pre-
_Options) library switch to a non-null and non-blank value, the
RCI generates a malformed compile (or link) command for the
target compiler. This command fails when you execute it on the
remote compilation platform.
2 December 1992 RATIONAL\f
Release 2_0_2
You can, however, set the desired options in the Rci.Compiler-
_Post_Options (or Rci.Linker_Post_Options) switch. The RCI then
generates the correct form of the command from this value.
4.3. Executable Filename Length Limits
The Alsys UNIX Ada compiler and linker place certain restrictions
on executable filenames. These conditions include the following:
* If you specify an executable name to Rci.Link with an
extension, for example, "foo.exe", the Alsys linker ignores
the extension. This is not a problem during linking; the
Rci.Link command should still succeed. However, when you
execute your compiled program or retrieve the executable
module from the remote compilation platform, you must execute
or retrieve a file named "foo", rather than "foo.exe", because
the Alsys linker did not create the filename with the
extension.
The Alsys UNIX Ada linker fails if a specified executable name
contains more than 14 characters.
* If you don't specify an executable name in the Rci.Link
command parameters when linking "bar", the RCI chooses the
unit name "bar" as the default executable name. If the unit
name contains more than 10 characters, the default executable
name is truncated by the Alsys linker to 10 characters, but
the Alsys i386 LynxOS RCI will rename the generated remote
files, so after an Rci.Link operation, the name of the
executable module will be the unit name. Note, however, that
main unit names must be unique within their first 10
characters.
To avoid these conditions, always specify a short executable name
(14 characters or less) without an extension for your executable
name when you call Rci.Link. If the condition occurs when using
pragma Main, you can either rename your main unit to a shorter
name (10 characters or less) or remove pragma Main completely.
4.4. Destroying Families
The Alsys i386 LynxOS RCI extension never destroys families nor
deletes family directories. If you need to remove a family, log
on to the remote machine or use Rci.Execute_Remote_Command from
the host to remove it manually using the ada family_manager.erase
<family> command).
4.5. Maximum UNIX Command Length
The maximum length of a LynxOS UNIX command is 254 characters. If
your remote directory names are long and/or your pathnames
contain many subdirectories, you may create RCI-generated
RATIONAL December 1992 3\f
Alsys i386 LynxOS RCI Release Information
commands that exceed that maximum length. Since the RCI does not
normally check command length, the remote operating system may
return messages about this. To avoid this problem, keep your
remote directory names short (by using Rci_Cmvc commands) and
minimize the number of subdirectories in your pathnames.
5. Known Problems
Following is a list of problems specific to the Alsys i386 LynxOS
RCI known at the time of this release.
5.1. Replacing Imported Libraries and Cmvc.Import
If a remote imported view is in a different family than its
importing view, and if you need to replace one imported view of a
subsystem with another, first call Cmvc.Remove_Import to remove
the old view, and then call Cmvc.Import to import the new view.
Cmvc.Import alone does not delete the original remote imported
view.
5.2. Retrieving Rci.Link Failure Information
If an Rci.Link command fails on the remote compilation platform,
the message describing the reason for the failure is usually
written into the .map file which the Alsys Binder generates.
However, the RCI will not always retrieve the .map file when the
link fails. In that case, you must retrieve it manually from the
remote platform, using Ftp.Get or the Rci.Upload_Unit command, to
find out what caused the failure.
6. Troubleshooting
This section describes troubleshooting techniques for situations
with the Alsys i386 LynxOS RCI.
If the Alsys UNIX Ada compiler fails, your output display may not
include enough information for you to determine what is wrong. To
get more information, set the enclosing view's Rci.Trace_Command-
_Output library switch to True and recompile the offending unit.
7. Documentation
The Rational Compilation Integrator: Alsys i386 LynxOS User's
Guide, PN 4000-00580, is available.
Refer to the Customizable RCI Release Notes for information on
RCI documentation.
4 December 1992 RATIONAL\f
Release 2_0_2
8. Training
Refer to the Customizable RCI Release Notes for training
information.
RATIONAL December 1992 5\f
Release 2_0_2
Contents
1. Overview 1
2. RCI Components 1
3. Prerequisites 1
4. Limitations 2
4.1. Uploading Executable Files 2
4.2. Compiler and Linker Pre_Options Switches 2
4.3. Executable Filename Length Limits 3
4.4. Destroying Families 3
4.5. Maximum UNIX Command Length 3
5. Known Problems 4
5.1. Replacing Imported Libraries and Cmvc.Import 4
5.2. Retrieving Rci.Link Failure Information 4
6. Troubleshooting 4
7. Documentation 4
8. Training 5
RATIONAL December 1992 iii\f
Alsys i386 LynxOS RCI Release Information
iv December 1992 RATIONAL