Patch 200801251-1 - Rational Apex Embedded 4.0 for any UNIX O/S ----------------------------------------------------------- To install this patch, download these 3 files and run the install script: install_200801251_1 any.patch.200801251-1.inventory any.patch.200801251-1.tar.Z Description IMPORTANT NOTE: See WARNING associated with defect PEBU00007889 before installing this patch. REQUIRED PATCH SERIES IDs: Starting with Apex 4.0.0, most Native and Embedded patches have a SeriesID associated with them. Specifying a SeriesID as a prerequisite for installation as opposed to a PatchID prevents prerequisites from becoming obsolete as new patches are created. SeriesIDs are text strings -- eg runtimes, views, etc -- and are listed next to the PatchIDs at ftp://ftp.rational.com/patch_info/index.html Before installing this patch, you must install a patch from each of the following product-series: Apex Native: series sun4_solaris2 [patchID 20010710 or later]. Apex Native: series share [patchID 20011211 or later]. ---------------------------------------------------------- It is suggested that all users install this patch. ---------------------------------------------------------- This patch fixes the following: Defect RATLC00151031: The Applied Micro Circuits Corporation (AMCC) 440EP variant of the PowerPC processor has an instruction set similar to the PowerPC 603 supported by Rational Ada Embedded Developer. However, it does not implement recording floating point instructions such as fadd. (note the '.' in the mnemonic, which is what distinguishes this from the non-recording fadd). The Apex PowerPC code generator makes extensive use of recording operations to simplify floating point code. This patch provides scripts compatible with the new lx_ppc440ep views and runtimes. ---------------------------------------------------------- The following were fixed in earlier patches. The fixes are included in this patch as well. Defect PEBU00007160: NFS mode was not working for LynxOS targets. Defect PEBU00007346: Tools:Convert (aka apex_convert) failed when target architecture was ppc_eabi_sfp. Defect PEBU00007348: The apex_execute.ash script referenced an undefined variable when debugging a C program with the GUI debugger. Defect PEBU00007356: The Tools > Convert dialog now uses a file selected in the Directory Viewer as default value for the Input File field. Also, the conversion format is remembered after user selects OK or Apply, and is used as the default value for the remainder of the Apex Session. Defect PEBU00007360: Tornado 2.0.2 was not being recognized by apex_execute or apex_debug as a supported version of Tornado. Defect PEBU00007513: Tools > Tornado Launch could sometimes compute incorrect value for WIND_REGISTRY, resulting in failure to start Tornado Launch dialog. Defect PEBU00007519: When run in ClearCase mode, File > New > BSP needs to alter the Link.des files to properly locate other subsystems. Defect PEBU00007520: The File > New > BSP command must do the CODE VIEWS stage in the same order the COPY VIEWS stage is done. This insures that object files will exist in view A when they're needed to link in view B. Defect PEBU00007555: The tools->convert dialog comes up with a conversion mode selected but no formats shown for that mode. Defect PEBU00007567: If a new physical target is created using the Targets dialog (Tools:Target Control menu selection), the new target does not appear in the dialog's target selection list. The dialog must be refreshed, as by closing and reopening it, for the target to appear. Defect PEBU00007572: Tools > Symbol Info dialog now processes *.o file when *.C file is specified. Defect PEBU00007575: Tools > Symbol Info. Tabs in this dialog were not correctly initialized to match context. Defect PEBU00007588: File > New > Source Release: Specifying a relative path name for the destination library could cause errors. Relative path names now work correctly. Defect PEBU00007605: If a customer sets APEX_LYNX_ROOT before starting Apex, their value would be overwritten by apexinit (assuming the Apex LynxOS product was installed). This patch fixes this defect by providing a new apexlx.init.sh (the template for apexlx.init), and also by automatically running the included script.PEBU00007605 to correct the existing apexlx.init. If apexlx.init has already been fixed by a previous installation of this or another patch it will not be altered. Defect PEBU00007652: Tools > Convert dialog. Converting from foreign relocatable to vox relocatable did not work because the -format option passed to the apex_convert script was incorrect. Defect PEBU00007657: Tools > Symbol Info dialog did not allow user to show Relocation Information for VxWorks executables. Defect PEBU00007689: Downloading the kernel to a simulator failed if the following three conditions were met: a) the kernel was specified explicitly (rather than via the -default_kernel switch); b) the simulator needed to be restarted; c) the download took place in a view that did not have the KERNEL_VOX switch set. Defect PEBU00007780: Help options for the command apex_create_kernel_interface did not agree with documentation. Defect PEBU00007813: File > New > New BSP could process views in incorrect order, resulting in errors when trying to link the kernel. Defect PEBU00007843: File > New > Physical Target's Reserve Target toggle not always correctly greyed out for simulators Defect PEBU00007889: Fix Target Control implementation so that it works under ClearCase. This patch corrects the installation of the Target Control component of Apex Embedded. Earlier versions of Apex Embedded (3.2.0 thru early 4.2.0 releases) used a APEX_PHYSICAL_TARGETS location incompatible with ClearCase (CMVC-controlled files were stored in $APEX_EMBEDDED_HOME/physical_targets.ss/main.wrk). The Target Control Implementation provided (referenced via the APEX_TARGET_CONTROL environment variable) was also incompatible with ClearCase. Apex Embedded now stores Physical Target Files as uncontrolled files in a plain directory ($APEX_EMBEDDED_HOME/physical_targets). It also uses a Target Control Implementation compatible with ClearCase. If this patch finds an existing old-style Physical Targets repository it will copy Physical Target Files from the old location to the new location. The old view will then be renamed main.wrk.old. The APEX_PHYSICAL_TARGETS and APEX_TARGET_CONTROL variables are set in $APEX_EMBEDDED_HOME/bin/common/apex_embedded.init. This script will update it to reflect the new Apex Target Control structure. !!! WARNING !!! Relocating APEX_PHYSICAL_TARGETS effects other Apex Embedded installations that shared the old APEX_PHYSICAL_TARGETS or APEX_TARGET_CONTROL locations. To update other Apex Embedded installations, download and run the following patches: 3.2.? : Contact Rational Customer Service to determine the patch for Defect PEBU00007889. 4.0.? : Any patch from the 4.0 share series dated 20020816 or later. 4.2.? : Any patch from the 4.2 share series dated 20020816 or later. This change does not effect Apex Embedded 3.0.0 and earlier. Defect PEBU00007955: Allow user to override default values for APEX_WIND_* environment variables (used in the VxWorks Apex products). The values for these variables are originally obtained from the user during installation of the Apex Embedded VxWorks product. The environment variables are then set during apexinit. This patch alters the script sourced during apexinit so that it does not override existing values for the variables. The list of variables effected are: APEX_WIND_BASE_INTEL APEX_WIND_BASE_MIPS APEX_WIND_BASE_PPC APEX_WIND_BASE_SIXTYEIGHT APEX_WIND_REGISTRY_INTEL APEX_WIND_REGISTRY_MIPS APEX_WIND_REGISTRY_PPC APEX_WIND_REGISTRY_SIXTYEIGHT Defect PEBU00007970: GUI Debugger failed to start under Solaris 2.8 if /usr/ucb was not on the users path (because printenv is no longer a built-in command in 2.8). Defect PEBU00007982: Correctly display Embedded-specific Initialization messages during apexinit so that customers can see which Apex Embedded layered products have been installed. Defect PEBU00007997: The Tools > Kernel Services > Configure dialog could generate errors relating to settings.iterate not being set. Defect PEBU00008004: The File > New > Physical Target dialog could generate a false error when creating simulator. The error read: 'targetName not set. Unable to return value to' Defect PEBU00008259: The File > New > New BSP command could have problems resulting in unwanted double quotes being added to invocations of copy_view. Defect PEBU00008323: File: New: BSP or File: New: Source Release now only set SUBSYSTEM_NAME in the destination subsystem if the destination subsystem was just created. In such cases, if the source subsystem had a null value for SUBSYSTEM_NAME, the destination subsystem will receive the default SUBSYSTEM_NAME (eg rts_interface.apex.rational.com). Defect PEBU00008565: The patching linker scripts (apex_pl_*.ash) did not work. This patch fixes them. Defect PEBU00008768: The Patching Linker scripts (apex_pl_diff, etc) died when invoked. Enhancement #1: Update Target Control Dialogs to handle the E5900 probe for Rational Exec (PowerPC and I386). In order to use the E5900 probe, you must also install a patch from the Tools series for the appropriate target architecture (PowerPC or I386) containing the target interface executables (a.run_e5900 and a.db_iface_e5900). ---------------------------------------------------------- It is suggested that all users install this patch.