Wind River Linux Release Notes, 5.0ess-wiki.advantech.com.tw › wiki › images › d › d0 › Wr_linux...Wind River Linux Release Notes, 5.0.1 6 Project-Based Business Model Wind

Wind River Linux

RELEASE NOTES

5.0.1

®

Wind River Linux Release Notes, 5.0.1

Copyright © 2013 Wind River Systems, Inc.

All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means without the prior written permission of Wind River Systems, Inc.

Wind River, Tornado, and VxWorks are registered trademarks of Wind River Systems, Inc. The Wind River logo is a trademark of Wind River Systems, Inc. Any third-party trademarks referenced are the property of their respective owners. For further information regarding Wind River trademarks, please see:

www.windriver.com/company/terms/trademark.html

This product may include software licensed to Wind River by third parties. Relevant notices (if any) are provided in your product installation at one of the following locations:

installDir/product_name/3rd_party_licensor_notice.pdf installDir/legal-notices/

Wind River may refer to third-party documentation by listing publications or providing links to third-party Web sites for informational purposes. Wind River accepts no responsibility for the information provided in such third-party documentation.

Corporate HeadquartersWind River500 Wind River WayAlameda, CA 94501-1153U.S.A.

Toll free (U.S.A.): 800-545-WINDTelephone: 510-748-4100Facsimile: 510-749-2010

For additional contact information, see the Wind River Web site:

www.windriver.com

For information on how to contact Customer Support, see:

www.windriver.com/support

Wind River LinuxRelease Notes5.0.1

4 Apr 13

http://www.windriver.com/company/terms/trademark.html

http://www.windriver.com

http://www.windriver.com/support

iii

Contents

1 Overview ...................................................................................................... 1

1.1 Introduction ...................................................................................................................... 1

1.2 Navigating these Release Notes ................................................................................... 1

1.3 Features ............................................................................................................................. 3

1.4 Installation and Licensing ............................................................................................. 4

1.5 Obtaining BSPs ................................................................................................................ 4

1.6 Migration and Backward Compatibility .................................................................... 7

1.7 Platform Kernel Versions by Product Release ........................................................... 8

1.8 Documentation ................................................................................................................ 8

1.9 Workbench Support ........................................................................................................ 9

1.10 Latest Release Information ............................................................................................ 9

1.11 Software Packages ........................................................................................................... 10

1.12 Patches ............................................................................................................................... 10

2 Changes in This Release ........................................................................... 11

2.1 Introduction ...................................................................................................................... 11

2.2 New or Enhanced Features ............................................................................................ 11

3 System Requirements ................................................................................ 15

3.1 Introduction ...................................................................................................................... 15

3.2 Host System Requirements ........................................................................................... 15

3.3 Target System Requirements ........................................................................................ 17

Wind River LinuxRelease Notes, 5.0.1

iv

3.4 Installation Requirements and Issues ......................................................................... 18

4 Wind River Linux Known Problems .......................................................... 21

4.1 Introduction ...................................................................................................................... 21

4.2 Usage Caveats .................................................................................................................. 21

4.3 Known Problems ............................................................................................................. 23

4.4 Workbench Integration .................................................................................................. 27

4.5 Documentation Updates and Errata ............................................................................ 28

5 Wind River Workbench 3.3 ......................................................................... 31

5.1 Introduction ...................................................................................................................... 31

5.2 Changes in This Release ................................................................................................ 31

5.3 Usage Caveats .................................................................................................................. 33

5.4 Known Problems ............................................................................................................. 37

5.5 Documentation Errata .................................................................................................... 45

6 Wind River Linux Carrier Grade Profile 5.0.1 ........................................... 47

6.1 Introduction ...................................................................................................................... 47

6.2 Carrier Grade Linux Features ........................................................................................ 48

6.3 Supported BSPs and Software ...................................................................................... 49


6.5 Usage Caveats .................................................................................................................. 49

6.6 Known Problems ............................................................................................................. 50

7 The GNU Toolchain ..................................................................................... 53

7.1 Introduction ...................................................................................................................... 53


7.3 Migration and Backward Compatibility .................................................................... 55

7.4 Known Problems ............................................................................................................. 55

Contents

v

A Package List ................................................................................................ 57

A.1 Introduction ...................................................................................................................... 57

A.2 Target Package List for Wind River Linux 5.0.1 ......................................................... 58

B Fixed Defect List ......................................................................................... 83

B.1 Introduction ...................................................................................................................... 83

B.2 Defects Fixed in Wind River Linux 5 ........................................................................... 83

Customer Services ....................................................................................................................... 89


vi

1

1Overview

1.1 Introduction 1

1.2 Navigating these Release Notes 1

1.3 Features 3

1.4 Installation and Licensing 4

1.5 Obtaining BSPs 4

1.6 Migration and Backward Compatibility 7

1.7 Platform Kernel Versions by Product Release 8

1.8 Documentation 8

1.9 Workbench Support 9

1.10 Latest Release Information 9

1.11 Software Packages 10

1.12 Patches 10

1.1 Introduction

These release notes cover Wind River Linux 5.0.1, Workbench for Linux 3.3.4, and the Wind River Linux Carrier Grade Profile, 5.0.1. Additional products may also contain relevant release notes or other information.

1.2 Navigating these Release Notes

This document covers release information for using Wind River Linux 5.0.1, along with the included development tools and toolchain.

Use the following links to get the latest, specific information you require:


2

■ Wind River Linux 5.0.1:

■ 2. Changes in This Release

■ 3. System Requirements

■ 4. Wind River Linux Known Problems

■ 5. Wind River Workbench 3.3

■ 6. Wind River Linux Carrier Grade Profile 5.0.1

■ 7. The GNU Toolchain

1 Overview1.3 Features

3

1.3 Features

Wind River Linux 5.0.1 is a flexible and expandable development environment that allows you to configure, build, and customize Linux target distributions, and then develop applications and packages tailored to your distribution. In addition, an extensive set of debug and analysis tools allow you to optimize your results to produce a quality final product.

1.3.1 Platform Features: Kernels and File Systems

The runtime systems are composed of kernels and file systems validated to work on specific boards.

1.3.2 Kernel Feature Profile Types

All supported boards have been verified to run the standard kernel type, or standard profile. The standard profile provides a robust set of features for your development needs.

Using feature templates, patches, and configuration fragments, you can extend your kernel’s capabilities to meet development needs.

In addition to the standard kernel type, certain boards support one or more enhanced kernel types, including cgl and preempt_rt.

Refer to Wind River Linux User’s Guide for more information on the standard and enhanced profiles.

1.3.3 Supported File Systems

There are five basic file systems:

■ Glibc Core—A smaller footprint version of the Glibc Standard file system, including all packages necessary to create a smaller file system that is not based on BusyBox.

■ Glibc Standard—a full file system, with Glibc but without CGL-relevant packages or extensions.

■ Glibc Small—a much smaller, BusyBox-based file system, with Glibc.

■ Glibc Standard Sato—A full file system with Glibc, optimized for the Sato interface. Sato is part of Poky, the Yocto Project platform builder.

■ EGLIBC—Embedded GLIBC (EGLIBC) is a variant of GLIBC which is designed with embedded systems in mind.

NOTE: Carrier Grade Linux (CGL) kernel types require the Wind River Linux Carrier Grade Profile (CGP) add-on product. See your Wind River representative for additional information.


4

1.4 Installation and Licensing

For information on installing your platform and configuring your product licenses, see the Wind River product installation and licensing guides. These are accessible from the following URL:

http://www.windriver.com/licensing/documents

You can install Wind River Linux as any user, including the root user, and make your installation available to other users, but you should not create or build projects as the root user.

The location you choose to install your software in is referred to as installDir in the documentation.

Refer to 3. System Requirements for information on supported development hosts.

Refer to 3.3 Target System Requirements, p.17 and Wind River Online Support for information on supported targets.

Electronic Software Distribution (ESD)

The installer program can automatically download product updates for you, including BSPs and future releases. To do so, launch the installer in its maintenance mode by running the wrInstaller or wrInstaller.exe application from the installDir/maintenance/wrInstaller/hostType directory. Once in the installer, click to accept any updates to the installer itself (this ensures that you will be able to install the latest product update). You can then select Product Updates and choose the software you want to install.

1.5 Obtaining BSPs

To support customers’ development needs, Wind River continually releases new BSPs for additional boards and processor families. Contact your Wind River representative to learn about newly available architecture support.

You obtain and install Wind River Linux BSPs by electronic software delivery (ESD). (This does not apply to other products such as VxWorks or earlier releases of Wind River Linux.)

NOTE: Before installing the product DVDs, be sure you have installed the host software required for proper product installation as described in 3.2 Host System Requirements, p.15.

NOTE: All installation media should be supplied to the host during installation, and the installation keys will determine which components to install. If all media are not inserted, your installation may be incomplete.

http://www.windriver.com/licensing/documents

1 Overview1.5 Obtaining BSPs

5

Licensing New BSPs for Wind River Linux 5.0.1

Depending on the product(s) you have purchased, you may need new installation keys or license updates for BSPs that become available post-release, referred to as async BSPs.

Existing Installation Keys and Licensing Terms Apply

For the following products, you can use your existing Product Activation File (PAF, also known as the install.txt file):

■ Wind River Linux 5.0.1 Project Type 4, Time Based


No New Installation Keys or Licensing Updates Required

For the following products, no additional install keys or licensing updates are required because these products do not deliver BSPs:

■ Add Wind River Linux 5.0.1 Tools with Wind River Workbench 3.3, Time Based

■ Add Wind River Linux 5.0.1 Tools with Wind River Workbench 3.3, Subscription

■ Add Runtime Open Source Software Disclosure for Wind River Linux 5.0.1, Time Based

■ Add Runtime Open Source Software Disclosure for Wind River Linux 5.0.1, Subscription

Updates Based on Processor Family (ProcFam) Licensing (Standard Model Only)

Ask your Wind River representative if a new BSP is included in the ProcFam you have licensed. If it is, request an update order to add the keys needed for the New BSP (and go get a new PAF). If it is not, you would need to license the additional ProcFam.

If the new BSP is contained within the ProcFam you have licensed, it would apply to these products:

■ Add Processor Family for Wind River Linux 5.0.1Single Project, Perpetual

■ Add Processor Family for Wind River Linux 5.0.1 with Wind River Workbench 3.3, Platform Developer, Perpetual

If the new BSP is in a different ProcFam than any you have licensed, it would apply to these products:

■ Add Processor Family for Wind River Linux 5.0.1 Single Project, Perpetual

■ Add Processor Family for Wind River Linux 5.0.1 with Wind River Workbench 3.3, Platform Developer, Perpetual

Updates Based on BSP (New Model Only)

Replacing an Existing BSP with a New BSP

If you would like to replace a previously purchased BSP with a new BSP, contact your Wind River representative to inquire about this possibility. The following products are delivered by BSP basis and may be applicable in this scenario:


6

Project-Based Business Model


■ Wind River Linux 5.0.1 Project Type 0, Subscription






■ 535-162190—Wind River Linux 5.0.1 Project Type 3, Subscription

Adding BSPs

To purchase additional BSPs, you must order one of the following products:

■ Add Wind River Linux 5.0.1 Board Support Package, Time Based

■ Add Wind River Linux 5.0.1 Board Support Package, Subscription

Acquiring a New Product Activation File (PAF)

After your update order has been processed and finalized, you can go to the licensing portal and retrieve your new PAF (this is the install.txt file). Alternatively, the Wind River Licensing Support team may help you retrieve a new PAF.

Once you have the PAF you can install the new BSP(s) as described next.

Installing New BSPs

After retrieving your new Product Activation File (the install.txt file) as needed, you can install the async BSP(s) as described in the following procedure.

NOTE: If you replace a BSP with another one on your Customer license, (as opposed to adding a new BSP), you are no longer entitled to support or updates on the replaced BSP(s).

NOTE: Even if your order has been finalized, you will not be able to install new BSP(s) until you acquire the PAF.

NOTE: Each BSP is supported by a toolchain architecture, and if you do not have the corresponding toolchain architecture installed, your new BSP will not be usable. For example, you will not be able to configure a project with the BSP, and it will appear incomplete in the Workbench platform project wizard.

You can install the toolchain before or after installing the BSP. To do so, re-insert each of your Wind River Linux discs in succession. At the activation screen, point the installer to your new Product Activation File and proceed to install the new architecture support.

1 Overview1.6 Migration and Backward Compatibility

7

Step 1: Prepare for installation.

1. Shut down all product processes, including any license servers.

2. If you have altered any Wind River-supplied files in your installation tree (not a recommended practice), archive them manually before installing any updates, as these files may be overwritten during the installation process.

Step 2: Install the BSPs).

1. Launch the installer. Go to installDir/maintenance/wrInstaller/x86-linux2 and run wrInstaller.

2. Select Product updates.

The installer will automatically search all available updates and verify your entitlement. (This may take a few minutes.)

a. Continue through the installer screen selections, until you get to the Choose Activation Type screen.

– If your existing keys are up-to-date, select Use the existing product activation file.

– If you have ordered new BSPs, other products, or received upgrades and have retrieved an updated Product Activation File (PAF), select Permanent install key file and point to your new PAF.

b. Continue your selections through the installation process and complete by clicking Finish.

The installer program automatically finds, downloads, and installs applicable BSPs for you.

Step 3: After installation

Restart any license servers (if applicable).

1.6 Migration and Backward Compatibility

Custom packages from previous releases of Wind River Linux may be imported to Wind River Linux 5.0.1 using the migration tool. This tool converts LDAT makefiles and layers into bitbake recipes and layers. The migration tool may be downloaded from Wind River On Line Support.

Wind River Support may also help you with any questions you have regarding migrating to Wind River Linux 5.0.1.


8

1.7 Platform Kernel Versions by Product Release

The following table provides platform kernel versions as they relate to Wind River Linux releases:

1.8 Documentation

Documentation is available at Wind River Online Support, through Workbench help, and also on the start menu on your installation host.

You can also access the documentation locally with an independent help browser as follows:

■ Linux:

$ installDir/workbench-3.3/x86-linux2/bin/wrhelp.sh &

■ Windows:

$ installDir\workbench-3.x\x86-win32\bin\wrhelp.bat

Or start an infocenter that provides remote access:

$ installDir/workbench-3.3/x86-linux2/bin/wrhelp.sh -start &

Refer to Wind River Workbench by Example, Linux Version: Where to Find Information for details on using wrhelp.sh.

You can also use a web browser and browse to the *.pdf or index.html files in locations under installDir/docs/extensions/eclipse/plugins/.

Product Platform ReleaseKernel Version Release Date

Wind River Linux 1.4 2.6.14 12 Oct 2006

Wind River Linux 1.5 2.6.14 01 May 2007

Wind River Linux 2.0 2.6.21 15 Dec 2007

Wind River Linux 3.0.1 2.6.27.21 14 Sep 2009

Wind River Linux 3.0.2 2.6.27.39 11 Dec 2009

Wind River Linux 3.0.3 2.6.27.47 04 Aug 2010

Wind River Linux 4 2.6.34.6 22 Oct 2010

Wind River Linux 4.1 2.6.34.8 18 Mar 2011

Wind River Linux 4.2 2.6.34.9 20 Jul 2011

Wind River Linux 4.3 2.6.34.10 15 Dec 2011

Wind River Linux 5 3.4.10 28 September 2012

Wind River Linux 5.0.1 3.4.34 20 March 2013

1 Overview1.9 Workbench Support

9

To access GNU toolchain documentation from the command line, see the subdirectories under the share/doc/ directory for your toolchain, for example, under:

installDir/wrlinux-5/layers/wr-toolchain/version/share/doc/architecture

Updating Documentation

You have two options to update your documentation:

Option 1: Update your installation’s documentation to the latest version

You can install the latest documentation using ESD with the Maintenance Tool.

From the Workbench main menu, select Help > Update Wind River Products.

From the command line, run the Maintenance Tool:

installDir/maintenance/wrInstaller/x86-linux2/wrInstaller

Option 2: Get the latest documentation from Wind River Online Support

This option lets you access and download the latest documentation, but does not install it on your host system.

To get the latest documentation, go to the Wind River Online Support site at:


and select Access Online Support to login to Wind River Online Support.

Once there, select Products > Current Products > Wind River Linux 5.0 > Manuals.

1.9 Workbench Support

Wind River Linux Platforms supports user-mode debugging with the ptrace agent, and run-time analysis tools in Wind River Workbench 3.3.4, Linux Version.

If you intend to use Wind River Workbench with Wind River Linux 5.0.1, you must install Wind River Workbench 3.3.4. Wind River Workbench 3.3.3 or earlier is not supported with Wind River Linux 5.0.1.

1.10 Latest Release Information

The latest information on this release can be found in the Wind River Linux area of the Wind River Online Support Web site:

http://www.windriver.com/support/

This site includes links to topics such as known problems, fixed problems, documentation, and patches.




10

For complete details of test results, please contact your Wind River representative.

For information on accessing the Wind River Online Support Web site, see Customer Services, p.89.

1.11 Software Packages

Wind River Linux 5.0.1 includes updated revisions for over 200 user space packages. Refer to A. Package List for a list of the software packages and their version numbers.

1.12 Patches

There are many Wind River patches applied to the architectures, boards, and packages of Wind River Linux. For information on specific patches, refer to the documentation where the patch is located.

To discover and examine BSP kernel specific patches please follow the instructions provided in the BSP README file.

For further information, contact your Wind River representative.

NOTE: Wind River strongly recommends that you visit the Online Support Web site before installing or using this product. The Online Support web site may include some mandatory software patches or other critical information regarding this release.

11

2Changes in This Release

2.1 Introduction 11

2.2 New or Enhanced Features 11

2.1 Introduction

Wind River Linux 5.0.1 represents the first product offering from Wind River to leverage the Yocto Project build system components.The details are highlighted in this section.

For changes related to other products included with your Wind River Linux purchase, see the following sections:

■ 5. Wind River Workbench 3.3

■ 7. The GNU Toolchain

2.2 New or Enhanced Features

This section introduces major new and enhanced features available with Wind River Linux 5.0.1. For details on these and all Wind River Linux features, refer to the online documentation.

BSP Cloning

Support has been added to allow developers to clone BSPs for added testing and development convenience.

New SDK Support

Wind River Linux 5.0.1 now includes an SDK for application development on a Windows host. In addition, a new installer helps simplify the importing of Linux SDKs.


12

Kernel Module Debugging

Wind River Linux 5.0.1 includes a debugging and analysis tools set. Kernel debugging can be done with KGDB using gdb from the command line.

Quilt integration for Patch Management

Wind River Linux uses the quilt program for managing the application of patch files. For each package being patched, quilt keeps the patch files in a specified directory and it keeps a rollback database in another specified directory.

Late Boot-time Optimization

The time from when the init process is launched until the last start-up script is executed has been optimized for faster boot times.

Multiple Platform Project Images from a Single Build

Support has been added to allow developers to create multiple platform project images from a single build project by specifying the image type at project configuration.

Support to Create initramfs-based Project images

Wind River Linux expands on the initramfs support found in the Yocto Project by providing the ability to specify the contents of the image and also bundle the image with a kernel image.

Support to Create and Configure a Preemptible Kernel

Wind River Linux provides a conditional real-time kernel type, preempt-rt, for certain board and file system combinations.

Support to Create ISO images and to Create and Burn Project Images Directly to a USB Device

Using the enable-bootimage option, developers can create a single, bootable image from which to boot a target device.

2.2.1 New Use Cases and Enhanced Procedures

The following new use cases and procedures are included with Wind River Linux 5.0.1:

■ Viewing README Files in Your Installation

■ Creating and Customizing EGLIBC Platform Project Images

■ Exporting the SDK

■ Exporting the SDK for Windows Application Development

■ Creating Alternate Kernels from kernel.org Source

■ Using the preempt-rt Kernel Type

■ Kernel Module Debugging

■ Dynamic Instrumentation of User Applications with uprobes

■ Using Dynamic Probes with ftrace

2 Changes in This Release2.2 New or Enhanced Features

13

■ Adding an RPM Package to a Running Target

■ Creating Bootable USB Images

■ Host-based Installation of Wind River Linux Images

■ Installing a Bootable Image to a Disk

■ Using initramfs to Load System Images

■ Implementing Virtual Routing and Forwarding

■ Debugging Embedded Python Applications

■ Using Workbench Configuration Management Features

■ Developing Qt Applications

■ Exporting a Project BSP as a Layer for Customization

■ Creating a Project from a Package

■ Patching Packages

■ Patching and Exporting Patches to Layers

■ Managing Packages on Live Targets

■ Adding Kernel Modules to the Platform

■ Creating and Exporting Kernel Patches to a Layer

■ Debugging User-Supplied Kernel Modules

2.2.2 BSPs on the Media

The following BSPs are shipped with Wind River Linux 5:

■ qemuarma9

■ qemumips

■ qemuppc

■ qemux86

■ qemux86-64

New to Wind River Linux 5 is that BSPs are now delivered exclusively using electronic software deliver (ESD). Additional BSPs are available for installation once you install the product. This includes:

■ cav_octeon2

■ e500-kvm-guest

■ e500mc-kvm-guest

■ fsl_e500mc

■ fsl-imx53

■ fsl-p10xx

■ fsl_p50xx

■ fsl_p2020


14

■ fsl_p4080

■ intel_atom

■ intel-xeon-core

■ lsi_acp34xx

■ stm_spear13xx

■ ti_omap3

■ x86-64-kvm-guest

■ x86-kvm-guest

■ xilinx_zynq

15

3System Requirements

3.1 Introduction 15

3.2 Host System Requirements 15

3.3 Target System Requirements 17

3.4 Installation Requirements and Issues 18

3.1 Introduction

This chapter lists the minimum requirements for running Wind River Linux where the host and target are separate computers.

3.2 Host System Requirements

The host is the computer on which you do your development work. Wind River Linux 5.0.1 is designed to run on any host that meets the requirements in this section.

While many Linux distributions are capable of running Wind River Linux, Wind River provides a list of recommended host distributions and their required packages at:


Once you log in, select Products > Current Products > Wind River Linux > Wind River Linux 5.0 to access the System Requirements - Recommended hosts list link with information on the recommended host distributions.

Wind River Linux is tested only against recommended hosts to help us identify and correct problems early on through our own Q&A process. Using a recommended host helps speed up your initial development effort while decreasing the possibility of running into unknown host-related problems.



16

However, Wind River Linux is supported on any hosts that meet the requirements listed in the following paragraphs. If your chosen host meets the requirements and you still have issues, Wind River will help you resolve them.

3.2.1 Development Host Requirements

The build system is largely self-hosted, but relies on the host environment for basic functionality. Host system requirements include:

■ The host system must have standard Unix file system semantics, and compatible versions of some basic tools and utilities. See 3.2 Host System Requirements, p.15 for additional information on accessing the System Requirements - Recommended hosts list.

■ At least 50 GB of disk space for the host system distribution, Wind River Linux and required packages, and basic platform development. Up to 500 GB of additional disk space may be required depending on the number of platform projects you plan to develop and their requirements.

■ The host system must be able to run 32-bit binaries.

■ The build system does not require root privileges, though you may need admin access to configure the host to meet host requirements.

■ The exact host tool requirements vary, but the following are the most likely to require additional effort:

■ The /bin/sh shell must be bash. While the build system tries to avoid bash dependencies, many packages have hidden or subtle dependencies on bash behaviors.

■ There must be a Python 2.6 or 2.7 available in path. 2.5 and 3.x are not fully compatible.

■ You must have a working C compiler to build host tools.

■ Builds must take place on file systems which provide stable and consistent file system behavior. The ext2, ext3, and ext4 file system family are known to work with default options. Specific requirements include:

■ Timestamps which consistently reflect the time at which operations occur, and which are monotonically increasing. Networked file systems can produce very strange results if clocks are not synchronized.

■ Reliable locking using flock(2), with persistence into a child process mandatory.

■ Standard permissions behavior. In particular, non-root users must not be able to give away files.

Necessary Development Host Libraries and Executables

Wind River Linux 5.0.1 requires a number of host libraries and executables to be installed into the host Linux distribution (Ubuntu 12.04 for example). As part of the installation process, you will receive a command-line message that lists the required packages, with instructions to run the following script in a console to install packages automatically, after installation completes:

$ installDir/wrlinux-5/scripts/host_package_install.sh --install

3 System Requirements3.3 Target System Requirements

17

In addition, the configure script automatically checks for the required executables and libraries on your host. If you do not have the necessary host executables and binaries installed, you will receive a corresponding message from configure when you try to configure a platform project, which is saved in config.log.

When this happens, it will be necessary for you to install the missing packages identified during the build process manually.

Wind River provides a list of required packages for our recommended hosts. See 3.2 Host System Requirements, p.15.

3.3 Target System Requirements

The target is the computer for which you are developing. This section lists the typical requirements for running Wind River Linux, in the standard configuration, in which the host and target are separate computers.

■ Wind River supported target board.

■ 64MB RAM is a reasonable minimum but requirements vary. More, for example, if a ramdisk is used.

■ Space for file system on hard disk, ramdisk, flash memory, floppy, or hard disk.

■ Ethernet or serial connection.

■ Keyboard and monitor where supported by target (recommended for configuration if using network booting).

Refer to the board-specific README files for details on specific target requirements.

3.3.1 Supported Target Boards

Refer to 2.2.2 BSPs on the Media, p.13 for a list of board support packages (BSPs) shipped with Wind River Linux 5.0.1. Refer to 1.5 Obtaining BSPs, p.4 for details on BSPs made available post-release, and for information on acquiring additional BSP licensing.

3.3.2 Targets Simulated by QEMU

QEMU, an open source machine simulator, allows you to configure the kernel and root file system for particular boards for which Wind River has created board support packages (BSPs). QEMU currently supports the following BSPs:

■ qemuarma9

■ qemumips

NOTE: The example above includes the --install option, for installing required packages. For additional options, run the script with the --help option.


18

■ qemuppc

■ qemux86

■ qemux86-64

Refer to the BSP README file for specific information on the BSP you wish to simulate.

For a list of QEMU BSP names with cross-references to QEMU BSPs from previous releases, see the Wind River Linux User’s Guide: Introduction:

3.3.3 Targets Simulated by Simics

Wind River Simics is a fast, functionally-accurate, full system simulator. Simics creates a high-performance virtual environment in which any electronic system – from a single board to complex, heterogeneous, multi-board, multi-processor, multi-core systems – can be defined, developed and deployed.

Wind River Simics, an optional product offered by Wind River, supports virtually any target platform, and is a fully developed integration layer for Wind River Linux 5.0.1. For your convenience, an evaluation copy is provided for all Wind River Linux 5.0.1 customers.

3.4 Installation Requirements and Issues

Installing Multiple Products Into the Same Location

If you install an additional product into the same location (directory or folder) as an existing product, you must do the following:

1. Run the existing product installer and provide it the new product license key to add necessary base features.

2. Run the installer on the new media and install the desired products

For example, if you are adding the OCD product to an existing Wind River Linux 5.0.1 installation, do the following:

1. Run the existing product installer from the Wind River Linux 5.0.1 media

Follow through all the prompts, supplying the new license key when the license key is requested.

2. Run the installer from the OCD media. Follow through all the prompts. You can re-use the existing key when the license key is requested.

If setup_linux Fails with Permission Error

Note that some Linux distributions either do not automount media, or automount with a noexec option that prevents execution of files found on the media.

3 System Requirements3.4 Installation Requirements and Issues

19

If ./setup_linux fails with a permissions error, you may need to remount the DVD. To do so, use the following steps:

1. Login as root by entering the command su in your terminal and entering the root password.

2. Enter the following command:

umount dvd_mount_point

Where dvd_mount_point is the location of the DVD mount. For example, a typical Red Hat or Fedora DVD mount point might be /media/DVD-12345-67890.

3. Then enter the following command:

mount -t udf /dev/cdrom dvd_mount_point

Where dvd_mount_point is the location of the DVD mount.

4. Exit root mode with the exit command.

5. Set your working directory to the location of the DVD mount:

cd dvd_mount_point

6. Retry the ./setup_linux command.


20

21

4Wind River Linux Known Problems

4.1 Introduction 21

4.2 Usage Caveats 21

4.3 Known Problems 23

4.4 Workbench Integration 27

4.5 Documentation Updates and Errata 28

4.1 Introduction

This chapter lists known problems, integration issues, and documentation errata with Wind River Linux 5.0.1. Where applicable, ClearQuest defect numbers are provided (for example [WIND00123456]) for help in tracking the issue.

4.2 Usage Caveats

■ Enabling commercial Wind River-supplied packages with commercial licenses

Wind River Linux 5.0.1 oe-core contains eight packages with commercial licenses: gst-fluendo-mp3, gst-openmax, gst-plugins-ugly, lame, libmad, libomxil, mpeg2dec, qmmp.

To use these packages in your platform project image, you must add them to your platform project’s projectDir/local.conf file, to the LICENSE_FLAGS_WHITELIST section. The following example adds all of these packages to the whitelist, enabling all packages for your platform project image:

LICENSE_FLAGS_WHITELIST = "commercial_gst-fluendo-mp3 \ commercial_gst-openmax \ commercial_gst-plugins-ugly \ commercial_lame \ commercial_libmad \


22

commercial_libomxil \ commercial_mpeg2dec \ commercial_qmmp"

Add or remove the files to include or exclude them for development.

■ Limitations with BusyBox getty for glib_small rootfs

When using telnet on ttyS0 to connect to a target file system using SSH via dropbear, the expected startup behavior is to first view an intoductory screen, which returns to a command prompt when you press Enter. If the terminal becomes garbled and unresponsive, it may be due to the limited implementation of getty that BusyBox provides. To overcome this limitation, install the util-linux-agetty package on the target. [WIND00356854, WIND00367857]

■ Video encoding and decoding support [WIND00277904]

Due to licensing issues, Wind River Linux 5 does not contain support for video decoding or encoding. Talk to your Wind River account manager if you need help with this feature.

■ You should run /sbin/ldconfig when first booting the target if you have added the mysql package. This is so that the library location information placed under /etc/ld.so.conf.d/ when adding the mysql package gets included.

■ Due to limitations of the ustar format which is forced for compatibility by automake, users performing platform builds must use a uid and gid smaller than 32 bits (less than 2097151).

■ In some new Gnome distributions, menus do not show icons by default, unlike previous releases. If you want to enable menu icons, go to the configuration center, locate gconf-editor, and modify the setting for desktop > gnome > interface > Menus have icons.

■ Using checkpoint_end with git is no longer supported. Use wrs_meta instead. For example, do not use:

$ git show checkpoint_end | filterdiff -i '*common_pc*.scc' | patch -s -p2 \ -d /tmp

Instead, use:

$ git show wrs_meta^^^^..wrs_meta | filterdiff -i '*/common_pc-*.scc' | patch -f -s -p2 -d /tmp/foo

4 Wind River Linux Known Problems4.3 Known Problems

23

4.3 Known Problems

For the most current list of known problems for this release, see the following Web site:


The remainder of this section highlights known issues that may have a significant impact on installation and your initial experience with this product. The current status of these issues is available online.

Note that you are strongly encouraged to read your board’s README file, available in installDir/wrlinux-5/layers/wr-bsps/boardname. These and other README files are automatically copied into your build directory at configure time.

■ Recieving internal compile errors that read:

<arch>-wrs-linux-gnu-gcc: Internal compiler error: Terminated program as

The variable program as in this example may be cc1, or for the arm compiler, it may be wrs-linux-gnueabi-gcc, or even -g++[WIND00396070].

In rare instances, you may receive this warning. If you do, simply rebuild your platform project image to correct it.

■ Cannot start the HOB on a Red Hat Enterprise Edition 6.3 due to lack of Red Hat support for the most recent Gtk, PyGtk, and PyGobject packages [WIND00398074].

The HOB requires Gtk 2.2 and PyGtk2 2.21, but Red Hat provides Gtk 2.18.9-10 and PyGtk2 2.16.0-3.

■ Receiving do_patch failure on platform project build [WIND00375210]

]If you receive the following warning while building a platform project with the util_linux package: ERROR: No valid terminal found, unable to open devshell, you must perform a distclean on the package, and rebuild the file system:

$ make -C build util_linux.distclean$ make

■ Some programs will not build due to missing symbolic constants or functions which are not part of a base POSIX system. Clean-up efforts in glibc have marked a number of extensions and non-standard features to be included only when you have requested them. To re-enable many of these optional features, use -D_GNU_SOURCE when compiling.

■ The version of fop that is shipped with OpenSuSE 11 (and optionally installed) causes a build failure with the pam package. The workaround is to ensure that /usr/bin/fop is not found when pam is in the configure stage.

To accomplish this, remove the fop package using YaST. This may require removing other dependent packages depending on the host configuration.

An alternate solution is to move the file aside with the following command:

# mv /usr/bin/fop /usr/bin/fop.bak

You can move fop back after the pam package has been built. [WIND00159542]

■ By default, RPM in Wind River Linux uses Sqlite as the default database format. If you use BerkleyDB on the host side, you may get warnings or errors



24

about pthread lock failure. If you must use BerkleyDB, the only workaround for this is to rebuild the rpm host-tool for the machine you are running the software on.

■ You cannot statically link busybox with glibc. It is possible to use the configure flag --enable-scalable=mklibs when static linking, though it might be buggy and is probably a bad idea. See http://sources.redhat.com/bugzilla/show_bug.cgi?id=3400.

■ The mtab lock file has been relocated to /var/lock, from /etc. According to the Filesystem Hierarchy Standard, /etc is not guaranteed to be writable.

When /etc is mounted as part of a read-only partition, you may need to pass -n to various mount commands in order to modify the existing mtab file. (Mounting new file systems will always work, modifying mounts may be an issue.) mount attempts to generate a tmp file in /etc, which is read-only, so it should fail. Even if it succeeds, /etc/mtab is bind mounted and can't be overwritten with a "rename".

■ To generate a certificate request with openssl, you should first download a sign.sh signing script (such as the one available at http://www.faqs.org/docs/securing/chap24sec195.html) and place it in /usr/sbin. You should modify it appropriately (for example, /etc/ssl should be changed to /usr/lib/ssl) to work in the Wind River Linux environment.

■ When using rpm on a target, automatic repackage of an erasure or upgrade is disabled. To enable it, set the value %_repackage_all_erasures to a non-zero value in the /usr/lib/rpm/5.0/macros file. You must also create a /var/spool/repackage directory.

■ gdbserver is supported on all target file systems, and gdb is supported on all target file systems with the exception of uclibc file systems. For example, the configure option:

--enable-rootfs=filesystem+debug

enables debugging tools (including gdbserver) and:

--enable-rootfs=filesystem+debug+gdb

enables debugging tools including gdb on the target. If filesystem is uclibc, a warning is issued that it is unsupported.

If other debugging tools are not required, just use:

--enable-rootfs=filesystem+gdb

By default gdbserver (when not used with the +gdb option) is used from the precompiled source. To force it to be built, edit the pkglist "gdbserver" line as follows:

gdbserver BUILD_GDB=yes

■ Using gdb and gdbserver with glibc thread debugging.

gdb is unable to trap some of the signals from threaded programs because the build system strips the binaries when the target filesystem is constructed. gdb needs some of the symbols out of the libpthreads.so to find all of the threading information.

NOTE: If gdb is specified in the pkglist, the gdbserver entry is ignored.

http://sources.redhat.com/bugzilla/show_bug.cgi?id=3400



http://www.faqs.org/docs/securing/chap24sec195.html

http://www.faqs.org/docs/securing/chap24sec195.html

4 Wind River Linux Known Problems4.3 Known Problems

25

The workaround is to install the debuginfo files, or use a debug build of glibc in order to debug threaded applications.

■ Running gdb on the Target

Copy the export/RPMS/arch/glibc-debuginfo-2.5-1.arch.rpm from the host to the target.

On the target run (as root):

cd /rpm2cpio glibc-debuginfo-2.3.6-1.arch.rpm | cpio -id

This will install files into /usr/lib/debug and /usr/src/debug (if there are any associated sources).

When the (target) gdb is run, it will detect that the symbols are stripped from the libpthread_db.so, and automatically look at /usr/lib/debug for the symbols.

■ Cross Debugging (Using gdbserver to attach to a process)

On your host system, extract the debug information:

cd local_debug_path rpm2cpio .../glibc-debuginfo-version.arch.rpm | cpio -id

On the target, setup gdbserver:

gdbserver host_ip:port --attach pid

Back on the host:

./host-cross/bin/i586-wrs-linux-gnu-gdb path_to_app/mthread.outset sysroot target_sysroot_path set debug-file-directory local_debug_path/usr/lib/debugtarget remote target_ip:port

In either case, you can verify that gdb has the proper thread information for debugging available by using the gdb command info threads. You should see a list of all of the threads. If you get either blank or "one" thread (when you should have more) then gdb was unable to load all of the symbols from the debug symbols version.

■ The --cref option to the GNU linker causes the linker to abort. Omit this option to create binaries successfully. [WIND00110868]

■ Some warnings remain when building the kernel, these warnings have been audited for safety and remain due to constraining factors such as upstream compatibility, code stability, compiler requirements and patch stack maintenance.

■ If you run into a case where your pkglist or export/RPMS files get out-of-sync, you can use the new checkconfig build target (make checkconfig) to rebuild the rpm mapping and reference files.

■ The user space ALSA libraries and utilities will only build/run in a glibc rootfs. They are included in glibc_std and feature/demo pkglist.add files.

■ gdb cannot debug threaded applications on a uclibc based system. To use gdb to debug threads on uClibc, you need to ensure that uClibc is built with the PTHREADS_DEBUG_SUPPORT=y option. This is not enabled by default. In order to enable this option, do the following:

$ configure ... --enable-build-libc=yes ...$ make -C build uclibc.configedit build/uClibc-*/.config


26

Change:

# PTHREADS_DEBUG_SUPPORT is not set

To:

PTHREADS_DEBUG_SUPPORT=y

Then build your system.

■ Wind River discourages NFS builds. When doing builds on NFS mounts, the file server and build machine must have synchronized clocks. If not, some package builds may fail. The solution is to use a Network Time Protocol (NTP) server. Red Hat Linux Enterprise WS includes NTPD. In addition to NTP issues, some operations require static inodes to be assigned to files in order to emulate special files, as well as owners/groups/permissions.

■ To ensure proper compilation and runtime behavior, the default optimization levels for production builds is -O2. The optimization flags are:

– -O Some optimizations are enabled.

– -O2 More optimizations are enabled, but none that increase the size of binaries.

– -O3 Maximum optimization.

– -Os Optimize for binary size.

For builds with “--enable-build=debug”, no optimization is specified.

Some packages will not compile or execute properly without optimization turned on: glibc, openssh/ssl and the kernel are examples; for these packages the lowest possible optimization setting will typically be used.

The default optimization level can make debugging user applications difficult due to instruction pointer bouncing. User applications that are not part of the default distribution can be built via workbench or from the command line with lower or no optimization. The system wide optimization level for debug builds can be modified in the CPU template config.sh file by altering/appending to the following variable:

TARGET_CDEBUG_LEVEL="-g -O value"

Similarly the production optimization level is controlled by:

TARGET_COPT_LEVEL="-O value"

where value is replaced by the desired optimization value. Note this value affects all packages and if changed from the default value, the runtime behavior cannot be predicted.

■ It may be necessary, when custom patching a package, to remove old directories, .stamp files, etc. In these cases, use make -C build package.distclean to remove (within the project build directory), the package build directory, the package source directory, and the package’s associated .stamp files.

■ MIPS boards with 32-bit PCI can only access 1GB of DMA memory.

■ There may be MIPS 64-bit kernel DMA problems with 32-bit PCI cards.

4 Wind River Linux Known Problems4.4 Workbench Integration

27

4.4 Workbench Integration

Wind River Linux 5.0.1 is being released with Workbench version 3.3.4.

System Viewer, OCD, and Workbench kernel debugging are supported with Workbench 3.3.4.

If you intend to use Wind River Workbench with Wind River Linux 5.0.1, you must install Wind River Workbench 3.3.4. Wind River Workbench 3.3.3 or earlier is not supported with Wind River Linux 5.0.1.

See 5. Wind River Workbench 3.3 for release information on using Workbench with Wind River Linux.


28

4.5 Documentation Updates and Errata

Documentation may be updated periodically as new features are added or issues are dicovered. This may include updates to the Wind River Linux User’s Guide, Wind River Linux Getting Started Guide, and the Workbench by Example Guide, Linux Version.

To get the latest versions of these guides, as well as the other Wind River Linux documents including a complete set of documentation, see 1.8 Documentation, p.8.

4 Wind River Linux Known Problems4.5 Documentation Updates and Errata

29


30

31

5Wind River Workbench 3.3

5.1 Introduction 31

5.2 Changes in This Release 31



5.5 Documentation Errata 45

5.1 Introduction

Wind River Workbench is a development suite that facilitates creating and building projects, establishing and managing host-target communications, and developing, debugging, and monitoring operating system kernels as well as device software applications running on a real or simulated target.

5.2 Changes in This Release

This release of Workbench includes the following changes. For details on Workbench integration with these changes, see the Wind River Workbench User’s Guide or the Linux version of Wind River Workbench By Example.

Wind River Workbench 3.3.4

Wind River Linux 5.0.1 Support

Wind River Workbench supports Wind River Linux 5.0.1 with the following features:

■ Reports Tool for platform project footprint optimization


32

■ Configuration management features to support CVS, Subversion (SVN), ClearCase, and Git directly from Workbench.

■ Python debugging on the target through support for layer projects and the Web Toolkit.

■ Package projects for managing changes to packages

■ Kernel module import and debugging

■ SDK import wizard

■ Ability to coexist with the Yocto Application Development Toolkit

Workbench support has the following exceptions:

■ Certain limitations for new C++ features in the compiler when using Wind River Workbench Code Coverage Analyzer

Improved Debugger Handling of Inline Functions

Improved capabilities for Step Over, Step Into, and local parameters and variables. The enhanced debug view now shows the [inline] tag.

Simics Debugger Compatibility

Workbench 3.3.4 is compatible with the Simics debugger.

5.2.1 Wind River Run-Time Analysis Tools

This section describes the enhancements and improvements to the Run-Time Analysis Tools (formerly ScopeTools) provided with this release.

Memory Analyzer

New Backtrace Algorhithms

The backend open source component of Memory Analyzer now uses the libunwind backtrace package. This provides more accurate backtraces based on symbol/dwarf information rather than assumptions on frame pointer layout, or function epilogue opcode analysis.

In addition, the libunwind backtrace package now supports ARM Thumb-2 mode. To analyze an application, you must:

■ build the application using Workbench, or

■ build the application using a platform project configured with the --enable-build=profiling configure option, or

■ build the application using a platform project configured with both --enable-build=debug and --enable-debuginfo-split=no configure options.

5.2.2 Fixed Problems

For a list of problems fixed in Wind River Workbench, visit the Online Support Web site (see 1.10 Latest Release Information, p.9).

5 Wind River Workbench 3.35.3 Usage Caveats

33

5.3 Usage Caveats

Workbench Issues

Workbench Fails to Launch on Fedora 18 Hosts

If Workbench fails to launch on a Fedora 18 host due to missing pangox-compat package, you will need to install the package manually (WIND00396584). Run the following command in a terminal to install the package:

$ su -c 'yum update pangox-compat'

Editor Window Popup Windows Dark on Ubuntu 64 Hosts

In the Editor, when you hover over a class or patch, a popup window displays to provide content-specific information. The default Ubuntu theme draws the background color to match the text, making it unreadable.

You have two options to read the information:

■ Select the text using your mouse cursor. The select background color is lighter, which makes the text readable.

■ Change the Ubuntu theme to a brighter color theme.

Workbench Supports US English Language Only

Workbench supports and is tested only with US English. Support for other languages is not available at this time.

Workspace Location

Wind River strongly recommends placing your workspace on a local file system. Remote file systems can cause significant performance problems. If you use ClearCase, place the workspace outside a dynamic view, otherwise you will face significant performance problems. Platform Projects will fail in a dynamic view, because the Clear Case MVFS file system is not a conforming NFS interface.

There is a new configure option that lets you specify the local build directory to help provide NFS conformance in this issue:

-with-local-build-dir=DIR

in this example, DIR refers to the local build directory for split local/NFS builds.

The local build directory will be used for the temporary build directories for host tools andtarget packages, the sysroot directory, databases, locking, and file system assembly. This enables the use of NFS and some similar file systems for the balance of a configured project as long as the minimal required semantics are supported.

Turning off Static Analysis for Large Projects

Static analysis is turned on by default. For large projects (such as kernel build projects) static analysis can slow down Workbench functionality considerably.

To turn off static analysis:


34

For existing projects:

Right-click the project and select Properties, then select C/C++ General > Indexer. From the Select Indexer drop-down list, select No Indexer. Click OK to close the dialog.

For new projects:

Select Window > Preferences and choose C/C++ > Indexer. From the Select Indexer drop-down list, select No Indexer. Click OK to close the dialog.

By project:

If you would prefer not to turn off static analysis for all new projects, you can turn it off for a particular project as you create it. Click Next in the New Project wizard until you reach the Indexer page, then select Enable project specific settings. From the Select Indexer drop-down list, select No Indexer, then click Finish to create the project.

Increasing Virtual Memory

Building large applications can cause Java to run out of memory. To avoid this, increase the size of memory for the Java virtual machine to 512 MB or higher for data, and 160 MB or greater for Java plug-ins and code. (The default values in Workbench 3.3 are 384 MB for data and 128 MB for code, respectively).

From the command line:

On Windows:

From a shell, type the following:

C:\> cd installDir\workbench-3.x\wrwb\platform\x86-win32\eclipse C:\> .\wrwb-x86-win32.exe -vmargs -Xmx512m -XX:MaxPermSize=160m

On Linux:

Use the values as parameters to the startWorkbench.sh script:

% ./startWorkbench.sh -vmargs -Xmx512m -XX:MaxPermSize=160m &

where 512 corresponds to 512 MB of RAM for the virtual machine.

From the Windows Start menu:

1. Select Start > Programs > Wind River > Workbench 3.x, then right-click Wind River Workbench 3.x and select Properties.

2. From the Shortcut tab, move the cursor to the end of the command in the Target text box.

3. After wrwb-x86-win32.exe, type:

-vmargs -Xmx512m -XX:MaxPermSize=160m

4. Click OK.

Each time you launch Workbench using the Start menu, you will allocate the appropriate amount of memory for the Java virtual machine.

From a desktop shortcut:

Right-click the shortcut, select Properties, and edit the Target command line as described above.

5 Wind River Workbench 3.35.3 Usage Caveats

35

Accessing Online Support from the Workbench Welcome Page

On Linux

Workbench opens your default browser. Your regular cookie settings apply.

Project and Build Issues

Running Workbench Remotely

Wind River recommends using Virtual Network Computing (VNC) software (http://www.realvnc.com/) when running Workbench on a remote Linux server. User interface responsiveness is much better compared to the standard remote X access method.

The Remote Workspace Location field of the Remote Connections dialog must contain the absolute path to the root directory of the workspace, as seen on the remote host. Environment variables are not supported in this field.

Wind River Run-Time Analysis Tools Issues

Memory Analyzer and -V Option

When using Memory Analyzer, the usermode agent should not be run with the verbose option, -V. Due to the high number of normal signal message diagnostics that may print, if the agent was started on the target console, /dev/console, then on some targets, the non-blocking nature of that device will significantly slow down the application begin analyzed. Before running Memory Analyzer, either start usermode-agent without -V or else run usermode-agent on an ssh terminal which supports non-blocking output.

Performance Profiler

Performance Profiler and Memory Analysis Configure Requirements

To use Workbench Performance Profiler or the Workbench Memory Analysis tool, you should build your platform project with the configuration option --enable-build=profiling, which enables optimizations, but prevents the split of debugging information into separate object files.

Alternatively, to build with no optimizations (for a better debugging experience) but support the analysis tools above, use:

--enable-build=profiling --enable-debuginfo-split=no

Avoid Using make fs-debug Until Profiling is Complete

When you build the file system with the make fs-debug command, this will split the debug information into a separate file. This will override the configurations above, and then may degrade address-to-symbol lookups in the analysis tools.

NOTE: The same arguments can be applied to headless scripts such as wrws_update.sh.

http://www.realvnc.com/

http://www.realvnc.com/


36

Defer or avoid building the fs-debug make target until your profiling is complete with your platform project build.

Performance Profiler and OProfile

You may need to make adjustments to your target board (for example, you may need to add the boot parameter oprofile.timer=1) in order for OProfile to work with your target architecture. See the README included with your target’s board support package (BSP)

Oprofile is not supported for kernels configured with the --enable-kernel=preempt-rt configure option (WIND00408634).

Performance Profiler on ARM Thumb-2 Architecture

Wind River Linux images compiled in Thumb-2 mode use an ABI that does not allow OProfile to gather call stacks.

Code Coverage Analyzer Issues

Coverage Instrumenter and Unusually Obfuscated C++ Language

The coverage instrumenter may not be able to handle unusually obfuscated C++ language constructs. If so, the instrumenter writes a parse error message to the build console and ignores the corresponding statement. It is not necessary to add the source file to the ignore list, unless the instrumented file is no longer buildable.

Java VM Heap Size

The heap size of the Java VM is a limiting factor when handling a large number of tags. To workaround this issue, you can increase the VM size by appending -vmargs -Xmx2048m to the Workbench command line (2048m stands for 2048 megabytes).

Note that the specified heap size should not be larger than half of the available system memory on Linux.

System Viewer Limitations on MIPS Architecture for Wind River Linux 5

■ The patches that enable a MIPS target running oprofile to perform backtrace have not been ported to Wind River Linux 5.

■ UST is not supported on the qemumips BSP.

Documentation Issues

Two Workbench by Example (Linux Version) Documents in Help System

When you select Help > Help Contents > Wind River Documentation > Wind River Workbench from the Workbench main menu to view Workbench documentation, you will see versions for Wind River Linux 4 and 5.

This occurs because both Wind River Linux versions include the same Workbench version, but offer different build systems and features. The result is that procedures created for a specific version are not compatible with the other. To avoid potential issues, always use the correct documentation for your installed prouct version [WIND00375545].

5 Wind River Workbench 3.35.4 Known Problems

37

Using the Help Browser Independently of Workbench

To run a full-featured help browser that runs independently of a particular instance of Workbench:

1. From a command shell or terminal window (or by double-clicking the executable on Windows), run one of the following scripts, substituting your Wind River product installation directory for installDir and the correct version for 3.x:

■ Windows: installDir\workbench-3.x\x86-win32\bin\wrhelp.bat

■ Linux: installDir/workbench-3.x/x86-linux2/bin/wrhelp.sh

2. When you are finished browsing the documentation, close the browser, then press CTRL+C to close the terminal window.

5.4 Known Problems

This section lists some known problems with Wind River Workbench. For a complete list of known problems in Wind River Workbench, visit the Online Support Web site (see 1.10 Latest Release Information, p.9).

Workbench Issues

Workbench May Crash when Using KDE with BSD Automount Daemon (amd)

When using Workbench on Red Hat Enterprise Linux (RHEL) with KDE, Workbench may crash when you use a native directory dialog to browse to a file system which is mounted by the BSD automount daemon amd. (WIND00069984)

Workspace Locks After an Unexpected Reboot

If your host unexpectedly reboots during a Workbench session, the .lock file may remain in your workspace. This means that when you restart Workbench, your workspace is locked and you cannot access your projects.

To unlock your workspace, use a shell window to navigate to your Workbench install directory, then delete the workspaceDir/.metadata/.lock file.

Workspace in Use Errors

Several issues can cause Workbench to display the error Workspace in use, choose a different one.

Possible reasons are:

■ Workbench or Eclipse does not have write access to the workspace or .metadata folder.

NOTE: You will have similar problems when using any system application, such as gedit. Wind River recommends that you do not use amd with RHEL and KDE since it will crash any standard application.


38

■ Another instance of Workbench is running in the same workspace. Only one instance of Workbench can use a workspace at a time.

■ The workspace may not have unlocked after an abnormal exit. To unlock it, kill the remaining Workbench and Java processes. On Linux, check which process still has an open file handle on the file installDir/workspace/.metadata/.lock by using the command lsof.

■ Your workspace is on a file system that does not support locking. Several issues in Eclipse and Java prevent the locking mechanism from working properly on some NFS-exported file systems such as HP. In such cases, after trying all the suggested fixes, use another Java Virtual Machine (JVM) argument to start Workbench:

./startWorkbench.sh -data /nfs/exported/hp/filesystem -vmargs -Dosgi.locking=none

Workbench Startup Reports “An Error Has Occurred”

If Workbench starts with the message An Error Has Occurred, try starting Workbench with the -clean option. On Windows, modify the shortcut that starts Workbench to wrwb.exe -clean. On Linux, start Workbench with:

$ startWorkbench.sh -clean

If that does not help, remove the Workbench configuration directory $HOME/.workbench-5.build_ID (Linux)

or%USERPROFILE%\.workbench-5.build_ID (Windows).

If neither of these methods works, try using a new workspace.

Workbench Reports Fork Problems on Linux

On Linux, Workbench may report a problem if it fails to execute an external process. For example:

java.io.IOException: Not enough space at java.lang.UNIXProcess.forkAndExec(Native Method)

The Java run time has the limitation that external processes are launched using fork, which requires that enough free memory (including swap space) is available. The fork tries to reserve the same amount of memory as the parent process, in this case, the Workbench process. After the successful launch of the process, only the actual required process memory will be allocated. If the maximum heap size is set too high, the child process cannot be started and Workbench operations will fail.

Make sure that:

■ Your system is configured with enough swap space.

■ Workbench is started with a reasonable heap size, which is not unnecessarily high. Choose a heap size which is always lower than half of the freely available memory (physical and swap). Note that every started process will reduce the available memory.

NOTE: This will allow multiple users to open the same workspace, which may result in potentially unrecoverable data loss.


39

Resetting Workbench to its Default Settings

If Workbench crashes, some of your settings could get corrupted, preventing Workbench from restarting properly.

To reset all your settings to their defaults, delete the .workbench-5.build_ID directory in your home directory. It is recreated when Workbench restarts.

Workbench Font Size Problem with Exceed 8

Although Exceed is not officially supported, running Workbench with Exceed 8 causes font size problems. Workbench appears correctly when running with Exceed 7.1 or Exceed 9.0.

Online Update

It is not possible to use the Help > Software Updates > Find and Install feature of Eclipse to update the Eclipse platform or Workbench itself. However, the feature can still be used to update any third party plug-in that you may have added to the installation.

To update Workbench, please download and install available patches from the Wind River Online Support site (see 1.10 Latest Release Information, p.9).

Printing in Workbench

On Windows, File > Print is enabled only for the Source Editor and the Disassembly view.

Ada Editing is No Longer Supported

Because of the switch from the Workbench Editor to the Eclipse Editor, Ada syntax highlighting is no longer available. Debugging still works, but you must use the default text editor for Ada files.

Linux Host-Related Issues

Debugging on Ubuntu 12.04

On Ubuntu 12.04, you cannot attach the Workbench debugger to a process using self-hosted facilities. This is because security has been reinforced on Ubuntu 12.04.

You can restore the previous behavior by issuing the following command as root:

# echo 0 > /proc/sys/kernel/yama/ptrace_scope

(WIND00365170)

Workbench Crashes on SuSE Running KDE

A problem exists in the gtk-qt-engine system library provided by SuSE/Novell. If this package is present, Workbench may crash on startup. The only workaround is to remove this library. This will have consequences for any program that uses the library.

To remove the library, issue the following command:

$ rpm -e gtk-qt-engine


40

General Licensing

The licensing system for Wind River Workbench assigns a license based on a combination of a unique machine ID and a unique name. If multiple Linux machines share the same name (such as localhost.localdomain), then installation and licensing will only work on the first machine to install it. To correct this problem in Red Hat Linux for example, select Applications > System Settings > Network and select the DNS tab.

In the Hostname field, replace the existing host name with a unique name for your system.

Close the Network Configuration dialog.

Next, add your new host name to the list of host names associated with address 127.0.0.1 in the /etc/hosts file.

Reboot your system so that the new network settings take effect.

Node Locked License Check-outs Fail on Fedora 15 and Above

Due to a bug in the Flexera source, license check-outs fail on Fedora 15 and above for node locked licenses. The problem appears on native hosts, but not in virtualized systems such as VMWare.

The following workarounds are available:

1. Use a license server setup avoiding any host ID problems. (Recommended if a local license server exists already.)

2. Use a virtual setup with Fedora 15 and later versions. (Recommended for environments that already make use of virtualization.)

3. Change the device names back to eth*.

Shared Wind River Linux Installations

You can install a single Workbench plus Wind River Linux installation on a shared NFS drive. Here are the basic rules for this configuration:

■ When you install, use the full NFS path that your users will be using. In other words, install from a remote location and not a local directory. This will allow any absolute paths in the installation to be valid for all users.

■ If you supported multiple hosts (Linux and Windows), be sure to install each of these in separate locations. Also, install using the same host, to insure that the correct host tools and environment is set up.

■ The shared installation can be read-only. If any user needs customization, they can do so within their projects, and/or use the layer feature to overlay the externally installation's contents.

■ Each user should use a local workspace for their projects.

NOTE: You will be prompted to log in as root to view these settings.


41

Project Issues

Rebuilding While Debugging

If you want to rebuild a project after a debugger session has started, you may need to disconnect from the debugger (depending on the type of project).

Non-English Character Restrictions

Workbench does not support the use of spaces (blank characters) or non-English language characters in project names. The usage is not prohibited, but it leads to errors.

Remote Systems View Issues

Update of Display is Slow when Listening to Execution Life Cycle Events

When more than 100 threads are running on the target, selecting Listen to execution context life cycle events can severely delay the update of the Remote Systems display. Do not use this feature when there are more than 100 contexts on the target.

Cannot Connect Registry or Debug Server (All Hosts)

When Workbench cannot connect to the Wind River Registry, or the debug server connection fails (logged as Failed to create Target Control) check your network configuration.

1. Check the error messages for host names and IP addresses, and do a ping at a command prompt to check whether the corresponding host names and addresses are actually reachable. Also, try nslookup with the host names to check if the DNS service is configured properly.

2. Try ping localhost and ping 127.0.0.1 to verify that the loopback interface is up and configured properly.

Drag and Drop is not Supported for Wind River Target Connections

It is not possible to drag images from the Project Explorer to Wind River target connections.

Build Issues

Build Properties Issues

Manual Addition of New Build Macros

New build macros you define in the Build Properties of a managed build project are not automatically added to any of the build tools. You must manually add the macro to the command line of the appropriate build tool(s) where appropriate. An Add to all button is available in the Build Paths settings which allows you to add a new Include Path to all build specs of the project in one step.


42

Debugging Issues

Problem Removing Breakpoint on KGDB Target

When a KGDB target is running and you remove a breakpoint that is installed on the target, the debugger can fail to remove that breakpoint if the target is in process of hitting the breakpoint that is supposed to be removed.

In this situation, the target will continue stopping at this breakpoint even though it is no longer present in the Breakpoints view. The only way to remove the breakpoint is to disconnect from the target and then to re-connect to it.

Casting an Address to a Structure Requires Extra Parenthesis

When passing an expression containing parentheses to the debugger, you must add extra parentheses to the expression. For example, if you place a watch on the following expression and expand it, the members get errors:

*(GRID *)0x20658

However, if you add parentheses around the address, the entry expands correctly.

(*(GRID*)0x20658)

In order to access members, you must also surround the cast with parentheses:

(*(GRID *)0x20658).x

(WIND00016848)

Consecutive Launches Using F11

Issuing multiple launch commands of the same application consecutively (using F11) may cause delays in Workbench view updates. This is due to the network traffic required to fetch stack information for each launched application.

Target Server and ICE Connection Conflicts

Though the Remote Systems view allows you to connect an emulator and a target server to a single board and use both connection types simultaneously, you must set the target server time-outs to longer default values to avoid the target server automatically disconnecting when the OCD connection stops the target.

For information about setting target server time-outs, see the Wind River Workbench User’s Guide.

Debugger Views

Debug View

In GTK+ on Linux, the Debug view icons do not wrap when the view is smaller than the width of the toolbar. So if you do not see all the icons discussed in the Wind River Workbench User’s Guide: Debugging Projects, expand the Debug view horizontally until all the icons appear on the toolbar.

Run Control

Step return is not fully working for recursive functions. For example, consider the following simple recursive function:

int factorial( int x ){

if (x > 1)


43

{int result = x;result *= factorial(x-1);return result;

} elsereturn 1;

}

If the factorial( ) function is called with an argument of 6, then you perform some Step operations until factorial( ) is called with an argument of 5, the call stack now contains two function calls: factorial(6) and factorial(5).

If you step to the statement result *= factorial(x-1); and then request that the debugger perform a Step Out operation, you would expect to end up in the calling function, which is factorial(6).

However, since the debugger sets a breakpoint at the statement return result; and then performs a Go operation, this recursive algorithm actually stops in the factorial(2) call. This is because the breakpoint isn't actually reached until the recursive function has completed calling itself all the way down to factorial(1) and then started returning values (unwinding the call stack).

Data Views

Changing the value of a variable or expression in data views (such as the Expressions view) may return an error, depending on the nature of the variable or expression.

For example, if the expression refers to a WRITE-ONLY register, a write succeeds but a read always fails.

Indexer Issues

Macro Limitations

No macro references appear in the call hierarchy (for MACROs that look like functions).

C++ Limitations

■ Template support is limited.

■ There are no references to constructors, destructors, or implicit type conversions in the symbol list. However, Declarations and Definitions are in the symbol list.

■ An implicit conversion (sequence) is generated when the type of an argument in a function call does not match the type of the parameter. It can make use of constructors to convert the argument to an object of the expected type.

■ Implicit constructor calls may be needed for the initialization of base classes, automatic variables, or returned values.

■ An implicit destructor call is necessary when an automatic variable goes out of scope.


44

Call Tree Limitations

There are no read/write flags for variables, and polymorphic method calls are not honored.

External APIs Cannot Be Configured

The preferences page for configuring external APIs no longer exists, because these APIs can no longer be configured by the user (they are associated with a project depending on the project type). External APIs are supplied for Wind River-specific project types (such as VxWorks project types).

Properties View Issues

Quotes Not Preserved in Parameter Values

In the Properties view, Eclipse does not preserve embedded quotes in parameter values. As a workaround, use \” before and after the parameter.

For example, to include “ppp”, type “\”ppp\”\”.

Run-Time Analysis Tools Issues

Memory Requirements with Valgrind and Certain BSPs

This release of valgrind does not support MIPS targets or e500v2 PowerPC variants. Wind River Workbench includes plugins for some of valgrind's test tools, including memcheck, massif, helgrind, and cachegrind. While testing these individual components, some issues were discovered with certain BSPs. The Workbench dialogs and on-screen instructions will note the problem components.

Valgrind may have large memory requirements as discussed in the valgrind user's manual. Some targets such as the ti-omap3530evm may not ship with enough memory to run valgrind's memcheck tool with the --track-origins=yes option.

Code Coverage Analyzer Issues

Coverage Instrumenter and Unusually Obfuscated C++ Language

The coverage instrumenter may not be able to handle unusually obfuscated C++ language constructs. If so, the instrumenter writes a parse error message to the build console and ignores the corresponding statement. It is not necessary to add the source file to the ignore list, unless the instrumented file is no longer buildable.

Java VM Heap Size

The heap size of the Java VM is a limiting factor when handling a large number of tags. To workaround this issue, you can increase the VM size by appending -vmargs -Xmx2048m to the Workbench command line (2048m stands for 2048 megabytes).

Note that the specified heap size should not be larger than half of the available system memory on Linux.

5 Wind River Workbench 3.35.5 Documentation Errata

45

System Viewer Issues

Continuous Upload from Target not Recommended

Continuous upload from a target with a slow connection link is problematical. It is strongly recommended that you use a different upload method for slow connections.

Out-of-Memory Problems with Large Parameters in the Log

If extremely large parameter payloads are encountered in the log, out-of-memory problems can occur. To prevent this, only the first 1024 bytes of either STRING or BLOB event parameters are now displayed by default. You can increase or decrease this value by setting the environment variable WRSV_PARAM_VALUE_MAXBYTES before you start Workbench; a value of -1 will display all bytes.

5.5 Documentation Errata

For a detailed list of documentation errata for Wind River Workbench, visit the Online Support Web site (see 1.10 Latest Release Information, p.9).


46

47

6Wind River Linux Carrier Grade

Profile 5.0.1

6.1 Introduction 47

6.2 Carrier Grade Linux Features 48

6.3 Supported BSPs and Software 49




6.1 Introduction

This chapter provides release information for the Wind River Linux Carrier Grade Profile (CGP), a new add-on product for use with Wind River Linux 5.0.1. See your Wind River representative for additional information or tu purchase he Wind River Linux CGP.

For information on using the CGP, see the Wind River Linus Carrier Grade Profile User’s Guide.


48

6.2 Carrier Grade Linux Features

The Wind River Linux CGP has implemented version 5.0 of the Linux Foundation's Carrier Grade Linux (CGL) specification. In addition, Wind River has implemented the following enhancements.

6.2.1 Carrier Grade Enhancements

The CGP product add-on extends Wind River Linux functionality with new features for creating and testing CGL target platforms. The resulting platform project image supports the Linux Foundation's Carrier Grade Linux specification, and includes features and performance suitable for use in carrier grade, telecommunications equipment.

Some of these features are:

■ Out of Memory (OOM) Killer Protection■ Persistent Memory Framework (PMEM)■ High Availability Framework■ CGL Test Suite■ Virtual Routing and Forwarding (VRF)

These extensions are described briefly below.

OOM Killer Protection

This is an enhancement to the kernel’s OOM killer. The enhancement protects critical processes from being killed in the event of memory starvation; makes sure that a terminated processes’s threads are also killed; and reduces maximum allowed memory for every process by 6% across the board.

Persistent Memory Framework

This extension allows both applications and the kernel to write debugging information to non-volatile RAM. The information is not overwritten upon reboot. This can be useful for debugging system hangs and interrupt context code. In addition, Wind River Linux supports a “simulated” version of PMEM that reserves a segment of RAM. It can be useful for systems where the bootloader does not reinitialize RAM on reboot, so that what is stored in it can survive a warm boot.

High Availability Framework

This includes integration of new technologies such as pacemaker and corosync to support high availability clusters, a userspace daemon to provide Common Address Redundancy Protocol, and a selection of filesystem technologies including iSCSI, DR:BD, and OCFS2 to ensure reliability throughout the network.

CGL Test Suite

This test suite provides many options for validating your CGL-enabled system agains the CGL 5.0 standards. Tests may be run individually, in groups, or all at once with a single command.

6 Wind River Linux Carrier Grade Profile 5.0.16.3 Supported BSPs and Software

49

Virtual Routing and Forwarding

This feature letsyou configure Linux kernel containers (LXC) to emulate a number of systems on a single host. Essentially, this turns a single system into a number (up to 251) of virtual machines. each with its own netwrk routing table.

6.3 Supported BSPs and Software

Wind River Linux CGP comes complete with pre-built Linux kernels and pre-built run-time file system packages (and will build identical and configurable kernels and file systems from source) for the following boards:

■ x86-based boards—Board names in Wind River Linux: intel_xeon_core, intel_atom, qemux86, qemux86-64

Support for QEMU-based boards is limited to development only. CGL validation requires a system disk that is not on an NFS-mount.

■ PowerPC-based boards—Board name in Wind River Linux: fsl_p2020, fsl_e500mc, fsl_p50xx, lsi_acp34xx


Wind River Linux CGP 5.0.1 is a new product. As a result, there are no changes to report.

6.5 Usage Caveats

Enable or Disable IP Forwarding in a Running VRF

When working with a physical, hardware system, once you create and start a VRF instance, IP forwarding is enabled by default. If you try to disable it, the operation fails (WIND00398393).

In addition, if you beging a physical, hardware system VRF instance with IP forwarding disabled, the system appears as IP forwarding is running, even though it is not.


50

The cause of this is the way grsecurity handles chroot. To disable IP forwarding, enter the following in the VRF instance’s command prompt:

# sysctl kernel.grsecurity.chroot_deny_sysctl=0

6.6 Known Problems

For a complete list of known problems in Wind River Linux CGP, visit the Online Support Web site (see 1.10 Latest Release Information, p.9).

6 Wind River Linux Carrier Grade Profile 5.0.16.6 Known Problems

51


52

53

7The GNU Toolchain

7.1 Introduction 53


7.3 Migration and Backward Compatibility 55


7.1 Introduction

The Wind River Linux toolchain provides C and C++ compilers, as well as a linker, assembler, debugger, and related utilities. The toolchain is produced by Mentor Graphics, and is a release of Wind River Linux Sourcery Codebench version 4.6.

As of the release of Wind River Linux 5, the toolchain versions include: 4.6-60, 4.6-73, and 4.6-82. Each of these contain some local enhancements specific to Wind River Linux. Future toolchain patches will update the number after the hyphen, which identifies a specific toolchain release, or "drop". When submitting bug reports about the toolchain, please be sure to indicate the specific toolchain drop you are using, as issues present in earlier drops may be corrected in later drops.

Users are often curious as to the "exact" versions of various toolchain components. Because Wind River Linux Sourcery Codebench is extensively updated from the upstream versions, the "exact" version is really 4.6-60 for all components. This corresponds roughly to gcc version 4.6, binutils version 2.22, eglibc version 2.15, and gdb version 7.2. When checking for feature availability, be sure to check the features actually provided by the toolchain, rather than looking at upstream project feature checklists; the Wind River Linux Sourcery Codebench toolchain often has enhancements or features that were not in the corresponding upstream tree until later versions.

Source code for the tools is available as part of the Platform Developer package as well as by request from Wind River.


54

This release supports the GNU tools for the host platforms and target architectures listed in chapter 3. System Requirements. Further, Wind River ships and supports only the C and C++ compilers, although other languages are included in the GNU Compiler Collection. The toolchain is installed in installDir/wrlinux-5/layers/wr-toolchain/version/. Within the toolchain, additional documentation is found in share/doc/arch. It is also available through the Workbench help system.

The most extensive information on GCC is available from the Free Software Foundation (FSF) at http://gcc.gnu.org/releases.html, which developers are encouraged to consult. Some of the information on the FSF Web site, however, may not apply to Wind River products, and Wind River does not support all features of GCC.


7.2.1 Enhancements

See http://gcc.gnu.org/gcc-4.6/changes.html for the complete list of changes and enhancements.

7.2.2 Fixed Problems

A list of known issues that have been addressed in toolchain updates may be found by searching Wind River Online Support. Changes were made to address rare code generation issues, prelinker issues, and occasional issues with the debugger.

7.2.3 Rebuilding the Toolchain from Source

While building the toolchain from source is supported, the resulting binaries are not supported—all defects must be reproduced using the prebuilt binary toolchain. The same applies for building glibc/uclibc—for support, all defects must be reproduced using the prebuilt binary glibc/uclibc.

When building a cross-compiler, you should use a 32-bit host. In some cases, a toolchain built on a 64-bit host can generate incorrect code or even fail to generate code successfully for some targets, especially 32-bit targets. Wind River only supports rebuilding the toolchain on 32-bit hosts, and there are known failures when rebuilding the toolchain on a 64-bit host.

Note also that gcc 4 is required to rebuild gcc 4.

http://gcc.gnu.org/releases.html

http://gcc.gnu.org/gcc-4.6/changes.html

7 The GNU Toolchain7.3 Migration and Backward Compatibility

55

7.3 Migration and Backward Compatibility

If you are migrating projects from earlier versions of GCC, you may need to recompile modules because of incompatible binary formats. Also, some nonstandard language constructs allowed by earlier versions of GCC are no longer supported in the most recent releases; the -fpermissive option may provide a short-term workaround for some projects.

The default semantics of inline functions changed from previous releases (such as the Sourcery G++ 4.1 series used in Wind River Linux 2.0). If you have problems with inline functions you may wish to try the -fgnu89-inline compiler flag.

More information on changes between 4.x and 4.6 may be found at http://gcc.gnu.org/gcc-4.4/porting_to.html, and http://gcc.gnu.org/gcc-4.6/porting_to.html.

7.4 Known Problems

See the FSF Web site at http://gcc.gnu.org/releases.html for information about known problems with the GNU tools.

http://gcc.gnu.org/gcc-4.3/porting_to.html




http://gcc.gnu.org/releases.html


56

57

APackage List

A.1 Introduction 57

A.2 Target Package List for Wind River Linux 5.0.1 58

A.1 Introduction

The following table list software packages and their version numbers provided with Wind River Linux 5.0.1:

■ Table A-1—Target Packages

Refer to the package maintainer sites for details on new package features.


58

A.2 Target Package List for Wind River Linux 5.0.1

The packages listed in Table A-1 lists the target packages available with Wind River Linux 5.0.1.

Table A-1 Wind River Linux 5.0.1 Target Packages

Package NameWind River Version Package Name Wind River Version

acl 2.2.51 libxdmcp-nativesdk 1.1.1

acl-native 2.2.51 libxext 1.3.1

acpid 1.0.10 libxext-native 1.3.1

adt-installer 0.1.8+svnr596 libxext-nativesdk 1.3.1

aer-inject git libxfixes 5

agent-proxy 1.96+git1+e6c9d3d996bd55e7ab14dbd74deb7841e0c3a4f1

libxfixes-native 5

agent-proxy-native 1.96+git1+e6c9d3d996bd55e7ab14dbd74deb7841e0c3a4f1

libxfixes-nativesdk 5

agent-proxy-nativesdk 1.96+git1+e6c9d3d996bd55e7ab14dbd74deb7841e0c3a4f1

libxfont 1.4.5

alsa-lib 1.0.25 libxfont-native 1.4.5

alsa-lib-native 1.0.25 libxfontcache 1.0.5

alsa-lib-nativesdk 1.0.25 libxft 2.3.0

alsa-state 0.2.0 libxft-native 2.3.0

alsa-tools 1.0.24.1 libxi 1.4.5

alsa-utils 1.0.25 libxinerama 1.1.2

apache2 2.4.2 libxkbfile 1.0.8

apache2-native 2.4.2 libxkbfile-native 1.0.8

apmd 3.2.2-14 libxml-filter-buffertext-perl 1.01

apr 1.4.6 libxml-filter-buffertext-perl-native

1.01

apr-native 1.4.6 libxml-libxml-perl 1.99

apr-util 1.4.1 libxml-libxml-perl-native 1.99

apr-util-native 1.4.1 libxml-namespacesupport-perl 1.11

A Package ListA.2 Target Package List for Wind River Linux 5.0.1

59

apt 0.7.14 libxml-namespacesupport-perl-native

1.11

apt-native 0.7.14 libxml-parser-perl 2.41

aspell 0.60.6.1 libxml-parser-perl-native 2.41

at 3.1.13 libxml-perl 0.08

atk 2.2.0 libxml-sax-base-perl 1.08

atk-native 2.2.0 libxml-sax-perl 0.99

attr 2.4.46 libxml-sax-perl-native 0.99

attr-native 2.4.46 libxml-sax-writer-perl 0.53

augeas 0.10.0 libxml-sax-writer-perl-native 0.53

autoconf 2.68 libxml-simple-perl 2.18

autoconf-native 2.68 libxml-simple-perl-native 2.18

autoconf-nativesdk 2.68 libxml2 2.7.8

autogen-native 5.12 libxml2-native 2.7.8

automake 1.11.2 libxml2-nativesdk 2.7.8

automake-native 1.11.2 libxmu 1.1.1

automake-nativesdk 1.11.2 libxmu-native 1.1.1

avahi 0.6.31 libxp 1.0.1

avahi-ui 0.6.31 libxpm 3.5.10

babeltrace 0.8+git1+efc5077568403009493d1d72e94f292838825e51

libxpm-native 3.5.10

babeltrace 1.0.0-rc2 libxprintapputil 1.0.1

base-files 3.0.14 libxprintutil 1.0.1

base-passwd 3.5.24 libxrandr 1.3.2

bash 3.2.48 libxrandr-native 1.3.2

bash 4.2 libxrandr-nativesdk 1.3.2

bc 1.06.95 libxrender 0.9.7

bdwgc 20110107 libxrender-native 0.9.7

bdwgc-native 20110107 libxrender-nativesdk 0.9.7

Table A-1 Wind River Linux 5.0.1 Target Packages (cont’d)



60

bdwgc-nativesdk 20110107 libxres 1.0.6

beecrypt 4.2.1 libxscrnsaver 1.2.2

beecrypt-native 4.2.1 libxsettings-client 0.1

benchfft 3.1 libxslt 1.1.26

bigreqsproto 1.1.1 libxslt-native 1.1.26

bigreqsproto-native 1.1.1 libxt 1.1.2

bigreqsproto-nativesdk 1.1.1 libxt-native 1.1.2

bind 9.8.1 libxtrap 1.0.0

binutils 2.22 libxtst 1.2.1

binutils-cross-canadian-arm 2.22 libxv 1.0.7

binutils-cross-native 2.22 libxvmc 1.0.7

binutils-crosssdk 2.22 libxxf86dga 1.1.3

binutils-crosssdk-native 2.22 libxxf86misc 1.0.3

binutils-native 2.22 libxxf86vm 1.1.2

bison 2.5 libyaml 0.1.4

bison-native 2.5 libyaml-native 0.1.4

blktool 6-Apr libzypp 0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433

blktrace 1.0.5+git1+d6918c8832793b4205ed3bfede78c2f915c23385

lighttpd 1.4.30

bluez-hcidump 2.4 linux-dummy 1

bluez4 4.101 linux-firmware 0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a

bonnie++ 1.03e linux-libc-headers-nativesdk 3.2

boost 1.49.0 linux-windriver 3.4

boost-native 1.49.0 linuxdoc-tools-native 0.9.66

boottime 5 lm-sensors 3.3.2

boottime-native 5 lmbench 3.0-a9

bridge-utils 1.5 lockfile-progs 0.1.16




61

btrfs-tools git logcheck 1.3.15

btrfs-tools-native git logrotate 3.8.1

build-appliance-image 1 lrzsz 0.12.20

builder 0.1 lsb 4.1

busybox 1.19.4 lsbinitscripts 9.03

busybox-oe-min 1.19.4 lsbsetup 1

byacc 20120115 lsbtest 1

byacc-native 20120115 lsof 4.85

bzip2 1.0.6 ltp 20120401

bzip2-native 1.0.6 ltrace git

cairo 1.10.2 lttng-control 0.89

calibrateproto 0.0+git1+1da6fd1e2c7a49648245c98481fabea8b9690a8c

lttng-tools 2.0.1

canutils 4.0.6 lttng-ust 0.16

ccache 3.1.7 lttng-viewer 0.12.38

ccache-native 3.1.7 lttng2-ust 2.0.2

cdrtools-native 2.01 lvm2 2.02.95

cfengine 3.4.0b2 lxc 0.7.5

chkconfig 1.3.58 lzo 2.06

chrpath 0.14 lzo-native 2.06

chrpath-native 0.14 lzo-nativesdk 2.06

chrpath-nativesdk 0.14 lzop 1.03

clutter-1.8 1.8.4 lzop-native 1.03

clutter-box2d 0.12.1+git1+de5452e56b537a11fd7f9453d048ff4b4793b5a2

lzop-nativesdk 1.03

clutter-gst-1.8 1.4.6 m4 1.4.16

clutter-gtk-1.8 0.11.4 m4-native 1.4.16

cma-test 0.0.1 m4-nativesdk 1.4.16




62

cmake 2.8.5 mailx 12.5

cmake-native 2.8.5 make 3.82

cmake-nativesdk 2.8.5 make-native 3.82

cogl 1.8.2 make-replacement-native 3.81

collectd 5.1.0 makedepend 1.0.3

compat-wireless 3.6.6-1 makedepend-native 1.0.3

compositeproto 0.4.2 makedevs 1.0.0

compositeproto-native 0.4.2 makedevs-native 1.0.0

connman 0.79 makedumpfile 1.4.4

connman-gnome 0.5 man 1.6f

console-tools 0.3.2 man-pages 3.36

consolekit 0.4.5 matchbox-config-gtk 0.0+git1+3ed74dfb7c57be088a5ab36e446c0ccde9fa1028

contacts 0.12+git1+19853893fdb595de6aa59db0d9dc2f9451ed2933

matchbox-desktop 2.0+git1+71e3e6e04271e9d5a14f1c231ef100c7f320134d

contacts 0.9 matchbox-desktop-sato 0.1+git1+810b0b08eb79e4685202da2ec347b990bb467e07

core-image-base 1 matchbox-keyboard 0.0+git1+b38f24036cff3be6c2fbcf9ca9881803e69003ac

core-image-basic 1 matchbox-panel-2 0.0+git1+cdf7a22716b87468f10573f622d5c7a58a684e35

core-image-clutter 1 matchbox-session 0.1

core-image-core 1 matchbox-session-sato 0.1

core-image-lsb 1 matchbox-stroke 0.0+git1+2b772583b61d2f6e8358e7c80e10293fc27cfcb7

core-image-lsb-dev 1 matchbox-terminal 0.0+git1+3fc25cb811a8ed306de897edf9b930f4402f3852

core-image-lsb-sdk 1 matchbox-theme-sato 0.1




63

core-image-minimal 1 matchbox-theme-sato 0.2+git1+f72cf4ed7d71ad9e47b0f2d3dbc593bc2f3e76f8

core-image-minimal-dev 1 matchbox-theme-sato-2 0.2+git1+e3ccc08d4a680d70fd4891fca966aa6ce503065c

core-image-minimal-initramfs

1 matchbox-wm 1.2+git1+f4394eaed475de6e627d373c5b35ee2cf87072e3

core-image-minimal-mtdutils 1 matchbox-wm-2 0.1+git1+01fa5465743c9ee43d040350f4405d35293e4869

core-image-rt 1 mc 4.8.1

core-image-rt-sdk 1 mce-inject git

core-image-sato 1 mce-test git

core-image-sato-dev 1 mcelog git

core-image-sato-sdk 1 mcstrans 0.2.11

coreutils 8.14 mdadm 3.2.3

coreutils-native 8.14 memstat 0.9

cpio 2.11 menu-cache 0.3.2

cracklib 2.8.18 mesa-demos 8.0.1

crash 6.1.0 mesa-dri 7.11+gitr1+983fa4ad523535debf2e94cf6ac1fd4c5630c0d2

crash-native 6.1.0 mesa-dri-glsl-native 7.11

createrepo 0.4.11 mesa-xlib 7.11+gitr1+983fa4ad523535debf2e94cf6ac1fd4c5630c0d2

createrepo-native 0.4.11 meta-environment-arm 1

cronie 1.4.8 meta-ide-support 1

cross-localedef-native 2.15 meta-toolchain 1

crypto-tools 20120127 meta-toolchain-gmae 1

cups 1.4.6 meta-toolchain-qte 1

curl 7.24.0 metacity 2.30.3

curl-native 7.24.0 mime-construct 1.11




64

curl-nativesdk 7.24.0 mingetty 1.08

cwautomacros 20110201 mini-x-session 0.1

cwautomacros-native 20110201 minicom 2.6.1

cyrus-sasl 2.1.25 mkfontdir 1.0.7

damageproto 1.2.1 mkfontdir-native 1.0.7

damageproto-native 1.2.1 mkfontscale 1.1.0

dates 0.4.11+git1+514185dc1f6588085fda41eb59898b93d0487dd4

mkfontscale-native 1.1.0

db 5.3.15 mktemp 1.7

db-native 5.3.15 mobile-broadband-provider-info

1.0.0+gitr1+d9995ef693cb1ea7237f928df18e03cccba96f16

db-nativesdk 5.3.15 modphp 5.3.14

dbus 1.4.16 module-init-tools 3.16

dbus-glib 0.98 module-init-tools-cross 3.16

dbus-glib-native 0.98 modutils-initscripts 1

dbus-native 1.4.16 mpatrol 1.5.1

dbus-nativesdk 1.4.16 mpfr 3.1.0

dbus-wait 0.1+git1+1a3e1343761b30750bed70e0fd688f6d3c7b3717

mpfr-native 3.1.0

debug-python 5 mpfr-nativesdk 3.1.0

desktop-file-utils-native 0.15 msmtp 1.4.24

device-mapper-multipath 0.4.9+git1+050b24b33d3c60e29f7820d2fb75e84a9edde528

mtd-utils 1.4.9

dhcp 4.2.3-P2 mtd-utils-native 1.4.9

dialog 1.1-20120706 mtools 4.0.17

dialog-static 1.1-20120706 mtools-native 4.0.17




65

diffstat 1.55 mutter 2.29.1+git1+01d3bebe24d2a56bdf2d82c4a71923e1573f7b7c

diffutils 3.2 mx 1.4.2

directfb 1.4.15 mysql-connector-odbc 5.1.6

directfb-examples 1.2.0 mysql5 5.1.40

distcc 2.18.3 mysql5-native 5.1.40

dmidecode 2.11 nasm 2.07

dmxproto 2.3.1 nasm-native 2.07

dnsmasq 2.55 nc6 1

docbook-dsssl-stylesheets-native

1.79 ncurses 5.9

docbook-sgml-dtd-3.1-native 1 ncurses-native 5.9

docbook-sgml-dtd-4.1-native 1 ncurses-nativesdk 5.9

docbook-sgml-dtd-4.5-native 1 neon 0.29.6

docbook-utils-native 0.6.14 neon-native 0.29.6

dosfstools 2.11 net-tools 1.60-23

dosfstools-native 2.11 netbase 4.47

dpkg 1.15.8.7 netcat 0.7.1

dpkg-native 1.15.8.7 nfs-utils 1.2.3

dri2proto 2.6 nspr 4.9.2

dropbear 2012.55 nss 3.13.6

dtc 1.3.0+git1+033089f29099bdfd5c2d6986cdb9fd07b16cfde0

numactl 2.0.8-rc4

dtc-native 1.3.0+git1+033089f29099bdfd5c2d6986cdb9fd07b16cfde0

ocf-linux 20120127

dtc-nativesdk 1.3.0+git1+033089f29099bdfd5c2d6986cdb9fd07b16cfde0

ocf-linux-native 20120127

e2fsprogs 1.42.1 ocf-linux-nativesdk 20120127




66

e2fsprogs-native 1.42.1 ofono 1.6

ecryptfs-utils 100 oh-puzzles 0.2+git1+92f1a20e4b72eed7a35b00984d9793b51dc2fb3b

ed 1.6 omap3-graphics-sdk 4.08.00.01

edac-utils 0.16 openjade-native 1.3.2

eds-dbus 2.30+git1+7337d11aed576e7caaa12b4e881ad8d33668799f

opensp 1.5

eds-tools git opensp-native 1.5

eee-acpi-scripts 1.1.12+git1+9d4cdedca25b396405f8587f9c4fbf8229e041c2

openssh 6.0p1

eggdbus 0.6 openssl 1.0.0i

eggdbus-native 0.6 openssl-native 1.0.0i

eglibc-initial 2.15 openssl-nativesdk 1.0.0i

eglibc-initial-nativesdk 2.15 opkg 0.1.8+svnr633

eglibc-locale 2.15 opkg-collateral 1

eglibc-locale-nativesdk 2.15 opkg-config-base 1

eglibc-nativesdk 2.15 opkg-native 0.1.8+svnr633

eject 2.1.5 opkg-nativesdk 0.1.8+svnr633

elfutils 0.148 opkg-nogpg-native 0.1.8+svnr596

elfutils-native 0.148 opkg-nogpg-nativesdk 0.1.8+svnr596

elfutils-nativesdk 0.148 opkg-utils 0.1.8+git1+49cc783d8e0415059d126ae22c892988717ffda7

enchant 1.6.0 opkg-utils-native 0.1.8+git1+49cc783d8e0415059d126ae22c892988717ffda7

encodings 1.0.4 oprofile 0.9.7+git1+88f43190d412d28ebf5c75a76ba20343d0fe4c41




67

enscript 1.6.6 oprofileui 0.0+git1+82ecf8c6b53b84f80682a8312f9defa83a95f2a3

ethtool 2.6.36 orinoco-conf 1

evieext 1.1.1 ossp-uuid 1.6.2

expat 2.0.1 ossp-uuid-native 1.6.2

expat-native 2.0.1 owl-video 0.1+git1+f133472318970796fae1ea3e98ac062156768baf

expat-nativesdk 2.0.1 package-index 1

expect 5.45 pango 1.28.4

external-csl-toolchain 4.6a-90 parted 3.1

external-csl-toolchain-cross 4.6a-90 parted-native 3.1

external-csl-toolchain-cross-canadian-arm

4.6a-90 passwdqc 1.2.2

fftw 3.2.2 patch 2.6.1

fftwf 3.2.2 pax 3.4

fftwl 3.2.2 pax-utils 0.2.2

file 5.11 pax-utils-native 0.2.2

file-native 5.11 pciutils 3.1.9

findutils 4.4.2 pcmanfm 0.9.10

findutils-native 4.4.2 pcmciautils 18

fixesproto 5 perf 3.4

fixesproto-native 5 perl 5.14.2

fixesproto-nativesdk 5 perl-native 5.14.2

flac 1.2.1 phpmyadmin 3.5.2.2

flex 2.5.35 pigz 2.2.4

flex-native 2.5.35 pigz-native 2.2.4

font-alias 1.0.3 pinentry 0.8.1

font-util 1.3.0 pixman 0.25.2

font-util-native 1.3.0 pkgconfig 0.25

fontcacheproto 0.1.3 pkgconfig-native 0.25




68

fontcacheproto-native 0.1.3 pkgconfig-nativesdk 0.25

fontconfig 2.8.0 pm-utils 1.4.1

fontconfig-native 2.8.0 pmtools 20071116

fontsproto 2.1.1 pointercal 0

fontsproto-native 2.1.1 poky-feed-config-opkg 1

foomatic-filters 4.0.7 polkit 0.104

footprint 5 polkit-gnome 0.102

formfactor 0 popt 1.16

fotowall 0.9 popt-native 1.16

freeglut 2.8.0 portmap 6

freetype 2.4.9 postgresql 9.1.4

freetype-native 2.4.9 powertop 1.13

fstests 0.1+git1+218b99d82b56011e3f1b909e6baf22ce25af6334

ppp 2.4.5

gail 1.20.2 ppp-dialin 0.1

gaku 0.1+git1+a0be2fe4b5f12b8b07f4e3bd624b3729657f0ac5

prelink 1.0+git1+7b47f2f8a15ed13b7905bc120bb2586f3e164f7d

galago-daemon 0.5.1 printproto 1.0.5

gamin 0.1.10 procps 3.2.8

gawk 4.0.0 pseudo 1.4.1+git1+398a264490713c912b4ce465251a8a82a7905f45

gcc-cross-canadian-arm 4.6.3+svnr184847

pseudo-native 1.4.1+git1+398a264490713c912b4ce465251a8a82a7905f45

gcc-cross-initial 4.6.3+svnr184847

pseudo-nativesdk 1.4.1+git1+398a264490713c912b4ce465251a8a82a7905f45

gcc-cross-intermediate 4.6.3+svnr184847

psmisc 22.16




69

gcc-crosssdk 4.6.3+svnr184847

psplash 0.1+git1+e05374aae945bcfc6d962ed0d7b2774b77987e1d

gcc-crosssdk-initial 4.6.3+svnr184847

psqlodbc 09.01.0200

gcc-crosssdk-intermediate 4.6.3+svnr184847

pth 2.0.7

gcc-runtime-nativesdk 4.6.3+svnr184847

ptpd 2.2.0

gconf 3.2.3 pulseaudio 2.1

gconf-native 3.2.3 puzzles r9375

gd 2.0.35 python 2.7.2

gdb-cross-canadian-arm 7.4 python-argparse 1.2.1

gdbm 1.8.3 python-argparse-native 1.2.1

gdbm-native 1.8.3 python-dbus 1.0.0

gdbm-nativesdk 1.8.3 python-gst 0.10.22

gdk-pixbuf 2.24.1 python-imaging 1.1.7

gdk-pixbuf-native 2.24.1 python-native 2.7.2

genext2fs 1.4.1 python-nativesdk 2.7.2

genext2fs-native 1.4.1 python-paste 1.7.5

gettext 0.18.1.1 python-pycairo 1.10.0

gettext-minimal-native 0.18.1.1 python-pycurl 7.19.0

gettext-native 0.18.1.1 python-pycurl-native 7.19.0

gettext-nativesdk 0.18.1.1 python-pygobject 2.27.91

ghostscript 9.05 python-pygobject-native 2.27.91

ghostscript-native 9.05 python-pygtk 2.24.0

git 1.7.7 python-pyrex 0.9.9

git-native 1.7.7 python-pyrex-native 0.9.9

glew 1.7.0 python-scons 2.1.0

glib-2.0 2.32.3 python-scons-native 2.1.0

glib-2.0-native 2.32.3 python-setuptools 0.6c11

glib-2.0-nativesdk 2.32.3 python-setuptools-native 0.6c11




70

glib-networking 2.28.7 python-smartpm 1.4.1

glproto 1.4.15 python-smartpm-native 1.4.1

glproto-nativesdk 1.4.15 qemu 1.3.0

gmp 5.0.4 qemu-helper-native 1

gmp-native 5.0.4 qemu-helper-nativesdk 1

gmp-nativesdk 5.0.4 qemu-native 0.15.1

gnome-common 2.28.0 qemu-nativesdk 0.15.1

gnome-common-native 2.28.0 qemugl-nativesdk 0.0+git1+d888bbc723c00d197d34a39b5b7448660ec1b1c0

gnome-desktop 2.32.1 qoriq-debug git

gnome-doc-utils 0.20.6 qt-demo-init 0.1

gnome-doc-utils-native 0.20.6 qt-mobility-embedded 1.2.0

gnome-icon-theme 2.31.0 qt-mobility-x11 1.2.0

gnome-keyring 2.32.1 qt-x11-free 3.3.7

gnome-mime-data 2.18.0 qt-x11-free-native 3.3.5

gnu-config 1.0+git1+a47f842264fc19837f8a00eb1d2d254a4c527334

qt4-embedded 4.8.0

gnu-config 20111111 qt4-graphics-system 1

gnu-config-native 1.0+git1+a47f842264fc19837f8a00eb1d2d254a4c527334

qt4-native 4.8.0

gnu-config-native 20111111 qt4-tools-nativesdk 4.8.0

gnu-config-nativesdk 20111111 qt4-x11-free 4.8.0

gnupg 2.0.18 qt4e-demo-image 1

gnutls 2.12.17 quicky 0.4

gnutls-native 2.12.17 quilt 0.51

gperf 3.0.4 quilt-native 0.51

gperf-native 3.0.4 quota 4

gpgme 1.3.1 randrproto 1.3.2




71

gradm 2.9.1 randrproto-native 1.3.2

grep 2.9 randrproto-nativesdk 1.3.2

groff 1.20.1 rdate 1.5

groff-native 1.20.1 rdist 6.1.5

grub 1.99 readline 6.2

grub-efi-x86-64-native 1.99 readline-native 6.2

gssdp 0.10.0 readline-nativesdk 6.2

gst-ffmpeg 0.10.13 recordproto 1.14.1

gst-fluendo-mpegdemux 0.10.69 refpolicy-mls 2.20120725

gst-meta-base 0.1 refpolicy-rbac 2.20120725

gst-plugin-bluetooth 4.101 refpolicy-standard 2.20120725

gst-plugins-bad 0.10.23 renderproto 0.11.1

gst-plugins-base 0.10.36 renderproto-native 0.11.1

gst-plugins-good 0.10.31 renderproto-nativesdk 0.11.1

gstreamer 0.10.36 resolvconf 1.64

gthumb 2.12.4 resourceproto 1.2.0

gtk+ 2.24.8 rgb 1.0.4

gtk-doc 1 rng-tools 3

gtk-doc-native 1 rpcbind 0.2.0

gtk-engines 2.20.2 rpm 5.4.9

gtk-sato-engine 0.3.3+git1+e4a29fbb7648f12fb3aefd8ea0120c3f54ba392a

rpm-native 5.4.9

gtk-theme-torturer 0.0.0+git1+99962ae39bb5aadb31929b25c58e1a053f9c9545

rpmresolve 1

gtkhtml2 2.11.0+svnr1161 rpmresolve-native 1

guile 2.0.3 rrdtool 1.4.7

guile-native 2.0.3 rsync 3.0.9

guilt-native 0.33 rt-tests 0.84




72

gupnp 0.16.1 ruby 1.9.3-p194

gupnp-av 0.8.0 ruby-native 1.9.3-p194

gupnp-tools 0.8.1 run-postinsts 1

gypsy 0.8 rxvt-unicode 9.15

gzip 1.4 samba 3.6.5

gzip-native 1.4 samhain 3.0.4

hdparm 9.39 sat-solver 0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32

hello 1 sato-icon-theme 0.4.1

help2man-native 1.38.2 sato-screenshot 0.1+git1+c792e4edc758bab21e0b01814979eacf0b1af945

hiawatha 8.6 schedtool 1.3

hicolor-icon-theme 0.12 screen 4.0.3

hostap-conf 1 scrnsaverproto 1.2.1

hostap-utils 0.4.7 scsidev 2.37

hostapd 1 sdparm 1.07

hwdata 0.234 sed 4.2.1

hwlatdetect 0.84 sed-native 4.2.1

i2c-tools 3.1.0 seedit 2.2.0.1

iasl 20100528 setserial 2.17

icecc-create-env-native 0.1 settings-daemon 0.0+git1+0f174f463dfed500b65533e249cd22942e439c77

icon-naming-utils-native 0.8.7 sg3-utils 1.33

icu 3.6 sgml-common 0.6.3

icu-native 3.6 sgml-common-native 0.6.3

ifenslave 1.1.0 sgmlspl-native 1.03ii

imagemagick 6.7.5 shadow 4.1.4.3

imagemagick-native 6.7.5 shadow-native 4.1.4.3

imake 1.0.5 shadow-securetty 4.1.4.3




73

imake-native 1.0.5 shadow-sysroot 4.1.4.3

inetutils 1.9.1 shared-mime-info 0.91

initramfs-boot 1 shared-mime-info-native 0.91

initramfs-framework 1 slang 2.2.4

initramfs-live-boot 1 smartmontools 5.42

initramfs-live-install 1 socat 1.7.2.0

initscripts 1 speex 1.2rc1

inotify-tools 3.14 sqlite3 3.7.10

inputproto 2.2 sqlite3-native 3.7.10

inputproto-native 2.2 sqlite3-nativesdk 3.7.10

inputproto-nativesdk 2.2 squashfs-tools 4.2

insserv 1.14.0 squashfs-tools-native 4.2

insserv-native 1.14.0 ssiapi 1.0.1

intltool 0.50.0 startup-notification 0.12

intltool-native 0.50.0 stat 3.3

iozone3 414 stat-native 3.3

iproute2 3.5.1 strace 4.7

ipsec-tools 0.8.0 strace-native 4.7

iptables 1.4.12.2 subversion 1.7.2

iputils s20101006 subversion-native 1.7.2

irda-utils 0.9.18 sudo 1.8.4p4

irqbalance 1.0.4 swabber-native 0.0+git1+a0792390c5d6d5a5bade7ab155c80eef3f30fa52

iw 3.6 sysfsutils 2.1.0

jpeg 8c sysklogd 1.5

jpeg-native 8c syslinux 4.05

js 1.7.0+1.8.0rc1 syslinux-native 4.05

json-glib 0.14.2 syslog-ng 3.3.5




74

kbd 1.15.2 sysprof 1.1.8+git1+4692f85f625f4fd969cef4ab5dc47cc4655c87f9

kbd-native 1.15.2 sysstat 10.0.3

kbproto 1.0.5 systemtap 1.7+git1+83bd2699d8cff2f2d6b9eaf5ea254e4cb6b33e81

kbproto-native 1.0.5 systemtap-native 1.7+git1+83bd2699d8cff2f2d6b9eaf5ea254e4cb6b33e81

kbproto-nativesdk 1.0.5 systemtap-nativesdk 1.7+git1+83bd2699d8cff2f2d6b9eaf5ea254e4cb6b33e81

kern-tools-native 0.1+git1+e2ccbf4c8626278e5884ff461b0b425d4fd3986f

systemtap-uprobes 1.7+git1+83bd2699d8cff2f2d6b9eaf5ea254e4cb6b33e81

kernelshark 1.2 sysvinit 2.88dsf

kexec-tools 2.0.3 sysvinit-inittab 2.88dsf

keymaps 1 taglib 1.6.3

keynote 2.3 tar 1.26

keyutils 1.5.5 tar-replacement-native 1.26

krb5 1.10.1 tasks 0.19

kvm-kmod 3.4 tboot 1.7.1

latencytop 0.5 tcf-agent 0.4.0+git1+4ef94ecb927a8912c3d79ce137182247786cff8f

lcms 1.17 tcl 8.5.11

lcms-native 1.17 tcl-native 8.5.11

ldconfig-native 2.12.1 tcp-wrappers 7.6

leafpad 0.8.18.1 tcpdump 4.1.1

less 444 telepathy-glib 0.17.5

liba52 0.7.4 telepathy-idle 0.1.11

libacpi 0.2 telepathy-mission-control 5.11.0

libaio 0.3.109 telepathy-python 0.15.19




75

libarchive 2.8.5 texi2html 5

libarchive-nativesdk 2.8.5 texinfo 4.13a

libart-lgpl 2.3.21 texinfo-native 4.13a

libassuan 2.0.3 tftp-hpa 5.2

libatomics-ops 7.2 tiff 4.0.1

libauthen-sasl-perl 2.15 time 1.7

libauthen-sasl-perl-native 2.15 tinylogin 1.4

libcanberra 0.29 tnftp 20100108

libcap 2.22 tokyocabinet 1.4.48

libcap-native 2.22 toolchain-wrappers-cross 1

libcgroup 0.37.1 toolchain-wrappers-cross-canadian-arm

1

libcheck 0.9.8 trace-cmd 1.2

libclass-isa-perl 0.36 transfig-native 3.2.5d

libclass-isa-perl-native 0.36 trapproto 3.4.3

libconvert-asn1-perl 0.22 tremor 20120314

libconvert-asn1-perl-native 0.22 trousers 0.3.10

libcroco 0.6.3 tslib 1

libdaemon 0.14 ttf-bitstream-vera 1.1

libdata-hexdump-perl 0.02 turbostat 3.4

libdata-hexdump-perl-native 0.02 tzcode-native 2011i

libdigest-hmac-perl 1.03 tzdata 2012f

libdigest-hmac-perl-native 1.03 u-boot v2011.06+git3+b1af6f532e0d348b153d5c148369229d24af361a

libdigest-sha1-perl 2.13 u-boot-fw-utils 2011.06

libdigest-sha1-perl-native 2.13 u-boot-mkimage 2011.06

libdmx 1.1.2 u-boot-mkimage-native 2011.06

libdrm 2.4.31 u-boot-mkimage-nativesdk 2011.06

libdumpvalue-perl 1.16 ubootchart 0.0+r12

libdumpvalue-perl-native 1.16 udev 164




76

libenv-perl 1.03 udev-extraconf 0

libenv-perl-native 1.03 unfs-server-native 2.1+2.2beta47

liberation-fonts 1.06 unfs-server-nativesdk 2.1+2.2beta47

libevent 2.0.16 unifdef-native 2.6.18+git

libexif 0.6.20 unixodbc 2.3.1

libfakekey 0.0+git1+e8c2e412ea4a417afc1f30e32cb7bdc508b1dccc

unzip 6

libffi 3.0.10 unzip-native 6

libffi-native 3.0.10 update-modules 1

libffi-nativesdk 3.0.10 update-rc.d 0.7

libfile-checktree-perl 4.41 update-rc.d-native 0.7

libfile-checktree-perl-native 4.41 usbinit 1

libfm 0.1.17 usbutils 0.91

libfontenc 1.1.1 userspace-rcu 0.7.2

libfontenc-native 1.1.1 util-linux 2.21.1

libgalago 0.5.2 util-linux-native 2.21.1

libgcc 4.6.3+svnr184847

util-macros 1.17

libgcc-nativesdk 4.6.3+svnr184847

util-macros-native 1.17

libgcrypt 1.5.0 util-macros-nativesdk 1.17

libgcrypt-native 1.5.0 v86d 0.1.10

libgdata 0.7.1 valgrind 3.7.0

libglade 2.6.4 videoproto 2.3.1

libgnome-keyring 2.32.0 vim 7.3.429

libgpg-error 1.1 vim-tiny 7.3.429

libgpg-error-native 1.1 vsftpd 3.0.0

libgsmd 0.1+svnr5394 vte 0.28.2

libgssglue 0.4 watchdog 5.11

libhugetlbfs 2.14 wdbagent-ptrace 3.3.75




77

libi18n-collate-perl 1.02 web 0.0+git1+e9a1c9433b9500feb7e3b9bb135debcea3a3e651

libi18n-collate-perl-native 1.02 web-webkit 0.1+git1+0f7019acd9db5383c732d0524c7c3a5eaec9be2b

libical 0.48 webkit-gtk 1.7.2+svnr101488

libice 1.0.8 wget 1.13.4

libice-native 1.0.8 which 2.2

libid3tag 0.15.1b wireless-tools 29

libidn 1.24 wpa-supplicant 0.7.3

libio-socket-ssl-perl 1.74 wr-coverageagent 1.1

libio-socket-ssl-perl-native 1.74 wr-opagent 1

libipc-signal-perl 1 wr-sdktools 5

libjson 0.9 wr-sdktools-native 5

libksba 1.2.0 wr-sdktools-nativesdk 5

liblockfile 1.09 wrlinux-feed-config-opkg 1

libmatchbox 1.9 wrlinux-image-glibc-core 1

libmatchbox 1.9+git1+d9dd0ac810de4f0b93cd813ce14aee34c722c2cf

wrlinux-image-glibc-small 1

libmhash 0.9.9.9 wrlinux-image-glibc-std 1

libmime-types-perl 1.35 wrlinux-image-glibc-std-5.0 1

libmpc 0.8.2 wrlinux-image-glibc-std-sato 1

libmpc-native 0.8.2 wrlinux-image-initramfs 1

libmpc-nativesdk 0.8.2 wrproxy 1.3

libmusicbrainz 3.0.3 wrs-kvm-helper 1

libnet 1.1.6 wrsv-ltt 4.0.11

libnet-libidn-perl 0.12 x-load 1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915

libnet-libidn-perl-native 0.12 x11-common 0.1




78

libnet-ssleay-perl 1.48 x11perf 1.5.4

libnet-ssleay-perl-native 1.48 x11vnc 0.9.13

libnet-telnet-perl 3.03 xauth 1.0.6

libnewt 0.52.14 xcb-proto 1.7

libnfsidmap 0.24 xcb-proto-native 1.7

libnl 3.2.8 xcb-proto-nativesdk 1.7

libnss-mdns 0.1 xcb-util 0.3.8

libogg 1.3.0 xcmiscproto 1.2.1

liboil 0.3.17 xcmiscproto-native 1.2.1

libowl 0.1+git1+6ebc8ac8f8575278dd40a535cadefa26374e44b1

xcmiscproto-nativesdk 1.2.1

libowl-av 0.1+git1+1379fd230a32509e94971961183f1031f469737a

xcursor-transparent-theme 0.1.1

libpam 1.1.5 xdebug 2.2.1

libpcap 1.2.1 xdg-utils 1.0.2

libpciaccess 0.12.902 xdpyinfo 1.3.0

libpcre 8.21 xerces-c 3.1.1

libpcre-native 8.21 xextproto 7.2.0

libpng 1.2.49 xextproto-native 7.2.0

libpng-native 1.2.49 xextproto-nativesdk 7.2.0

libpod-plainer-perl 1.03 xf86-input-evdev 2.6.0

libpod-plainer-perl-native 1.03 xf86-input-keyboard 1.6.1

libproc-waitstat-perl 1 xf86-input-mouse 1.7.1

libproxy 0.4.7 xf86-input-synaptics 1.5.0

libpthread-stubs 0.3 xf86-input-vmmouse 12.7.0

libpthread-stubs-native 0.3 xf86-video-fbdev 0.4.2

libpthread-stubs-nativesdk 0.3 xf86-video-intel 2.18.0

librsvg 2.32.1 xf86-video-vesa 2.3.0




79

libsamplerate0 0.1.8 xf86-video-vmware 11.0.3

libsdl 1.2.15 xf86bigfontproto 1.2.0

libsdl-nativesdk 1.2.15 xf86bigfontproto-native 1.2.0

libsm 1.2.1 xf86bigfontproto-nativesdk 1.2.0

libsm-native 1.2.1 xf86dgaproto 2.1

libsndfile1 1.0.25 xf86driproto 2.1.1

libsocketcan 0.0.8 xf86miscproto 0.9.3

libsoup 2.2.105 xf86rushproto 1.1.2

libsoup-2.4 2.36.1 xf86vidmodeproto 2.3.1

libssh2 1.4.2 xfsdump 3.1.0

libtasn1 2.11 xfsprogs 3.1.8

libtasn1-native 2.11 xhost 1.0.4

libtelepathy 0.3.3 xineramaproto 1.2.1

libtext-iconv-perl 1.7 xinetd 2.3.15

libtheora 1.1.1 xinit 1.3.2

libtimedate-perl 1.2 xinput 1.5.3

libtimedate-perl-native 1.2 xkbcomp 1.2.3

libtirpc 0.2.2 xkbcomp-native 1.2.3

libtool 2.4.2 xkeyboard-config 2.1

libtool-cross 2.4.2 xmlsec1 1.2.18

libtool-native 2.4.2 xmodmap 1.0.5

libtool-nativesdk 2.4.2 xorg-cf-files 1.0.4

libunique 1.1.6 xorg-cf-files-native 1.0.4

libunistring 0.9.3 xorg-minimal-fonts 1

libunistring-native 0.9.3 xprop 1.2.1

libunistring-nativesdk 0.9.3 xproto 7.0.22

libunwind 1.0.1 xproto-native 7.0.22

liburcu 0.6.7 xproto-nativesdk 7.0.22

liburi-perl 1.59 xrandr 1.3.5

libusb-compat 0.1.3 xrestop 0.4




80

libusb1 1.0.8 xserver-kdrive 1.7.99.2

libuser 0.57.1 xserver-nodm-init 1

libvirt 0.9.12 xserver-xf86-config 0.1

libvorbis 1.3.3 xserver-xorg 1.11.2

libwrsqtehelper 1 xserver-xorg-lite 1.11.2

libwrsqtxhelper 1 xset 1.2.2

libx11 1.4.4 xtrans 1.2.6

libx11-diet 1.4.4 xtrans-native 1.2.6

libx11-native 1.4.4 xtrans-nativesdk 1.2.6

libx11-nativesdk 1.4.4 xtscal 0.6.3

libx11-trim 1.4.4 xvideo-tests 0.1+git1+f8f320d0254c09ce483fc1d8ee99ecf5bc940965

libxau 1.0.7 xvinfo 1.1.1

libxau-native 1.0.7 xwininfo 1.1.2

libxau-nativesdk 1.0.7 xz 5.1.1alpha

libxcalibrate 0.0+git1+209d83af61ed38a002c8096377deac292b3e396c

xz-native 5.1.1alpha

libxcb 1.8.1 yaffs2-utils git1+7862c133d9d887fc9a939aefd69ed3403c287d54

libxcb-native 1.8.1 yajl 2.0.1

libxcb-nativesdk 1.8.1 zaurusd 0.1+git1+82b30c7865f007fff81372c3cdc71b2ff6843ccc

libxcomposite 0.4.3 zeroconf 0.9

libxcomposite-native 0.4.3 zip 3

libxcursor 1.1.13 zip-native 3

libxcursor-native 1.1.13 zlib 1.2.7

libxdamage 1.1.3 zlib-native 1.2.7

libxdamage-native 1.1.3 zlib-nativesdk 1.2.7




81

libxdmcp 1.1.1 zypper 1.5.3-git1+2c5bb6ceb99ecd950ef993e43d77bf0569ea0582

libxdmcp-native 1.1.1




82

83

BFixed Defect List

B.1 Introduction 83

B.2 Defects Fixed in Wind River Linux 5 83

B.1 Introduction

Table B-1 lists release 4.x defects fixed in the 5 release:

B.2 Defects Fixed in Wind River Linux 5

NOTE: Online Support always provides the latest list of defects and additional information such as workarounds. This list is provided here for your convenience but you should check Online Support for current details.

Table B-1 Defect Fixes Included with Wind River Linux 5

ClearQuest ID Summary

WIND00046653 System Viewer -- nested interrupts: Events are shown in an interrupt context instead of a task; warnings in log load report.

WIND00374343 File missing from UMA - when building using wr-uma-bb layer the wrong version is built

WIND00013729 On Linux Host, when the name of the local host is localhost.localdomain the target Registry does not get attached. Any other name given to the host machine make this fail.

WIND00365631 Application stdout blocked for QEMU user mode connections


84

WIND00374340 The default symbol file selected for Workbench Performance profiler *System.map-WR5* is set in the wrong field, the vmlinux file field

WIND00377844 Interrupting Wind River Linux Platform Project creation in Workbench is corrupting product installation

WIND00203836 Some toolchain build options out of sync.

WIND00230624 Feature Testing: warning "group dbus does not exist" appeared in installing RPMS

WIND00243141 Unable to connect Workbench to linux virtual board over MIPC on wrsbc8548

WIND00243345 [Bug Review]pkgconfig was missing when installing qt4-embedded

WIND00245754 Feature Testing: we need to document the working scope of userspace-ltt feature

WIND00247937 Feature Testing: Some userpace packages are NOT named properly

WIND00250424 On Fedora 13 x86_64, the postinst_lx_ckpackages.sh script claims packages (i686) as missing although their x86_64 counterparts are installed

WIND00250495 Feature Testing: [LSB] : Missing gdbm link of GDBM_File.so from pre-built x86_64 perl target package

WIND00253831 Qt demonstration documentation is not appearing on target

Table B-1 Defect Fixes Included with Wind River Linux 5 (cont’d)

ClearQuest ID Summary

B Fixed Defect ListB.2 Defects Fixed in Wind River Linux 5

85


86

87


88

CUSTOMER SERVICES

Wind River is committed to meeting the needs of its customers. As part of that commitment, Wind River provides a variety of services, including training courses and contact with customer support engineers, along with a Web site containing the latest advisories, FAQ lists, known problem lists, and other information resources.

Customer Support

For customers holding a maintenance contract, Wind River offers direct contact with support engineers experienced in Wind River products. The Customer Support program is described in the Standard Support User’s Guide available at:


The guide describes the services available, including assistance with installation problems, product software, documentation, and service errors.

You can reach Customer Support by e-mail or telephone:

For detailed contact information, including contact information specific to your products, see the Support Web site shown above.

Wind River Online Support

Wind River Customer Services also provides Wind River Online Support, an online service available under the Support Web site. This is a basic service to all Wind River customers and includes advisories, online manuals, and a list of training courses and schedules. For maintenance contract holders, Online Support also provides access to additional services, including known problems lists, patches, answers to frequently asked questions, and demo code.

Location Phone E-mail

North and South America, Asia/Pacific (outside Japan)

800-872-4977(toll-free)

[email protected]

Europe, Africa, Middle East +(00) 800-4977-4977(toll-free)

[email protected]

Japan 81-3-5778-6001 [email protected]

89

mailto:[email protected]


