Contents

1	Supported Platforms........................................................................................................................................		1
2	AIX Platforms....................................................................................................................................................		3
	2.1	Changing Thread Priority .....................................................................................................................	3
	2.2	Multicast Support ...................................................................................................................................	3
	2.3	Supported Transports ............................................................................................................................	3
	2.4	Monotonic Clock Support .....................................................................................................................	4
	2.5	Support for Controlling CPU Core Affinity for RTI Threads...........................................................	4
3	INTEGRITY Platforms ....................................................................................................................................		7
	3.1	Patch Required for INTEGRITY 10.02 Platform.................................................................................	8
	3.2	Support for Request-Reply Communication Pattern ........................................................................	8
	3.3	Diagnostics on INTEGRITY Systems...................................................................................................	8
	3.4	Socket-Enabled and POSIX-Enabled Threads are Required ............................................................	9
	3.5	Running over IP Backplane on a Dy4 Champ-AVII Board...............................................................	9
	3.6	Multi-NIC Support on INTEGRITY 5.0...............................................................................................	9
	3.7	Multicast Support ...................................................................................................................................	9
	3.8	Supported Transports ............................................................................................................................	9
	3.9	Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems............................................	11
	3.10	Monotonic Clock Support ...................................................................................................................	11
	3.11	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	11
	3.12	Issues with INTEGRITY Systems.......................................................................................................	11
4 Linux and Fedora Platforms .........................................................................................................................			13
	4.1	Native POSIX Thread Library (NPTL) Requirements.....................................................................	13
	4.2	Multicast Support .................................................................................................................................	14
	4.3	Supported Transports ..........................................................................................................................	14
	4.4	Monotonic Clock Support ...................................................................................................................	14
	4.5	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	14
	4.6	Libraries Required for Using RTI Secure WAN Transport APIs....................................................	14
	4.7	Libraries Required for Using RTI TCP Transport APIs...................................................................	15
5	LynxOS Platforms...........................................................................................................................................		23
	5.1	Multicast Support .................................................................................................................................	23
	5.2	Supported Transports ..........................................................................................................................	23
	5.3	Monotonic Clock Support ...................................................................................................................	24
	5.4	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	24
6	Mac OS Platforms...........................................................................................................................................		27
	6.1	Multicast Support .................................................................................................................................	27
	6.2	Supported Transports ..........................................................................................................................	27
	6.3	Monotonic Clock Support ...................................................................................................................	27
	6.4	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	27

iii

7 QNX Platforms................................................................................................................................................		31
7.1	Required Change for Building with C++ Libraries for QNX Platforms—New in 5.0.0.............	31
7.2	Multicast Support .................................................................................................................................	31
7.3	Supported Transports ..........................................................................................................................	31
7.4	Monotonic Clock Support ...................................................................................................................	32
7.5	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	32
7.6	Restarting Applications on QNX Systems ........................................................................................	32

8 Solaris Platforms ............................................................................................................................................		35
8.1	Support for Request-Reply Communication Pattern ......................................................................	35
8.2	Multicast Support .................................................................................................................................	35
8.3	Supported Transports ..........................................................................................................................	35
8.4	Monotonic Clock Support ...................................................................................................................	36
8.5	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	37
8.6	Libraries Required for using RTI Secure WAN Transport APIs ....................................................	37

9 VxWorks Platforms ........................................................................................................................................		41
9.1	Support for Request-Reply Communication Pattern ......................................................................	41
9.2	Increasing the Stack Size......................................................................................................................	41
9.3	Libraries for RTP on VxWorks 6 .........................................................................................................	41
9.4	Requirement for Restarting Applications .........................................................................................	42
9.5	Multicast Support .................................................................................................................................	42
9.6	Supported Transports ..........................................................................................................................	42
9.7	Monotonic Clock Support ...................................................................................................................	42
9.8	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	42

10	Windows Platforms........................................................................................................................................		57
	10.1	Use Dynamic MFC Library, Not Static ..............................................................................................	60
	10.2	Visual Studio 2005 Required when Using RTI ‘Debug’ Libraries for Java or .NET APIs ..........	60
	10.3	.NET API Requires Thread Affinity...................................................................................................	60
	10.4	Multicast Support .................................................................................................................................	60
	10.5	Supported Transports ..........................................................................................................................	61
	10.6	Monotonic Clock Support ...................................................................................................................	61
	10.7	Support for Controlling CPU Core Affinity for RTI Threads.........................................................	61
	10.8	PPP Link Support for Windows XP Systems....................................................................................	61
	10.9	Libraries Required for Using RTI Secure WAN Transport APIs....................................................	61
	10.10	Libraries Required for Using RTI TCP Transport APIs...................................................................	62
11	Custom Supported Platforms.......................................................................................................................		70

iv

Platform Notes

This document provides platform-specific instructions on how to compile, link, and run RTI® Connext™ (formerly RTI Data Distribution Service) applications.

1 Supported Platforms

Table 1.1 lists the platforms available with Connext 5.0.

See also: Custom Supported Platforms (Section 11).

Table 1.1 Platforms Available with Release 5.0

		Operating System	Reference
	AIX®	AIX 5.3	Table 2.1 on page 4
	INTEGRITY®	INTEGRITY 5.0.11 and 10.0.2	Table 3.1 on page 7
	Linux® (Cell BE™)	Fedora™ 12 (2.6.32 kernel)	Table 4.1 on page 15
		CentOS 5.4, 5.5, 6.0
		Fedora 12 (2.6.32 kernel)
		Fedora 12 (2.6.32 kernel) with gcc 4.5.1
	Linux (Intel®)	Red Hat® Enterprise Linux 5.0-5.2, 5.4, 5.5, 6.0, 6.1	Table 4.2 on page 15
		Red Hat Enterprise Linux 5.2 with Real-Time Extensions
		SUSE® Linux Enterprise Server 10.1 (2.6 kernel)
		Ubuntu® Server 10.04 (2.6 kernel)
		Wind River® Linux 4 (2.6 kernel)
		Freescale P2020RDB (2.6.32 kernel)
	Linux (PowerPC®)	SELinux (2.6.32 kernel)	Table 4.3 on page 16
		Wind River Linux 3
		Yellow Dog™ Linux 4.0
	LynxOS®a	LynxOS 4.0, 4.2, 5.0	Table 5.1 on page 24

1

Table 1.1 Platforms Available with Release 5.0

		Operating System	Reference
	Mac OS®	Mac OS X 10.6	Table 6.1 on page 28
	QNX®	QNX Neutrino® 6.4.1, 6.5	Table 7.1 on page 32
	Solaris™	Solaris 2.9, 2.10	Table 8.1 on page 37
		VxWorks 5.5, 6.3 - 6.9
	VxWorks®	VxWorks 653 2.3	Table 9.1 on page 43
		VxWorks MILS 2.1.1
		Windows 7 (32-bit and 64-bit Editions)
		Windows 2003 (32-bit and 64-bit Editions)
	Windows®	Windows Server 2008 R2 (64-bit Edition)	Table 10.1 on page 57
		Windows Vista® (32-bit and 64-bit Editions)
		Windows XP Professional (32-bit and 64-bit Editions) with
		Service Pack 2

a.The Java API is not supported on LynxOS platforms in 5.0.0. If your application requires support for Java on LynxOS, please contact your RTI account manager.

For each platform, this document provides information on:

❏Supported operating systems and compilers

❏Required Connext and system libraries

❏Required compiler and linker flags

❏Required environment variables for running the application (if any)

❏Details on how the Connext libraries were built

❏Multicast support

❏Supported transports

❏Monotonic clock support

❏CPU core affinity control support

2

AIX Platforms

2 AIX Platforms

Table 2.1 on page 4 lists the architectures supported on the IBM® AIX operating system.

Table 2.2 on page 5 lists the compiler flags and the libraries you will need to link into your application.

Table 2.3 on page 6 provides details on the environment variables required to be set at run time for an AIX architecture.

Table 2.4 on page 6 provides details on how the libraries were built. This table is provided strictly for informational purposes; you do not need to use these parameters to compile your application. You may find this information useful if you are involved in any in-depth debugging.

2.1Changing Thread Priority

Due to the AIX threading-model implementation, there are situations that require you to run your Connext application with root privileges:

❏For all APIs: Your application must have root privileges to use the thread option, DDS_THREAD_SETTINGS_REALTIME_PRIORITY, for the event and receiver pool thread QoS (DDS_DomainParticipantQos.event.thread, DDS_DomainParticipantQos.receiver- _pool.thread).

❏For the Java API only: Your application must have root privileges to change the event and receiver pool thread priorities (DDS_DomainParticipantQos.event.thread, DDS_DomainParticipantQos.receiver_pool.thread).

2.2Multicast Support

Multicast is supported on all AIX platforms and is configured out of the box. That is, the default value for the initial peers list (NDDS_DISCOVERY_PEERS) includes a multicast address. See the online documentation for more information.

2.3Supported Transports

Shared memory: Supported and enabled by default.

UDPv4: Supported and enabled by default.

UDPv6: Not supported.

TCP/IPv4: Not supported.

2.3.1Notes for Using Shared Memory

By default, the maximum number of shared memory segments you can use with AIX is quite small and limits the capability of Connext applications to work properly over shared memory. To increase the maximum number of shared memory segments an application can use, set the following environment variable before invoking your Connext application:

EXTSHM=ON

This environment variable is not required if your application does not use the shared memory transport.

3

To see a list of shared memory resources in use, please use the 'ipcs' command. To clean up shared memory and shared semaphore resources, please use the 'ipcrm' command.

The shared memory keys used by Connext are in the range of 0x400000. For example:

ipcs -m | grep 0x004

The shared semaphore keys used by Connext are in the range of 0x800000; the shared mutex keys are in the range of 0xb00000. For example:

ipcs -s | grep 0x008 ipcs -s | grep 0x00b

Please refer to the shared-memory transport online documentation for details on the shared memory and semaphore keys used by Connext.

2.4Monotonic Clock Support

The monotonic clock (described in Section 8.6 in the RTI Core Libraries and Utilities User’s Manual) is not supported on AIX platforms.

2.5Support for Controlling CPU Core Affinity for RTI Threads

Support for controlling CPU core affinity (described in Section 19.5 in the RTI Core Libraries and Utilities User’s Manual) is not available for AIX platforms.

Table 2.1 Supported AIX Target Platforms

	Operating	CPU	Compiler	RTI Architecture
	System			Abbreviation
		POWER5 (32-bit mode)	IBM XLC for AIX v9.0	p5AIX5.3xlc9.0
	AIX 5.3		IBM Java 1.6	p5AIX5.3xlc9.0jdk
		POWER5 (64-bit mode)	IBM XLC for AIX v9.0	64p5AIX5.3xlc9.0
			IBM Java 1.6	64p5AIX5.3xlc9.0jdk

4

					AIX Platforms
Table 2.2 Building Instructions for AIX Architectures
	API	Library	Required RTI Librariesa	Required System	Required
		Format		Librariesb	Compiler Flags
			libnddscppz.a
			libnddscz.a
		Static Release	libnddscorez.a
			For Connext Messaging, also include:
			librticonnextmsgcppz.a	-ldl -lnsl -lm
			libnddscppzd.a	-pthread
			libnddsczd.a
		Static Debug	libnddscorezd.a
			For Connext Messaging, also include:		-DRTI_AIX
	C++		librticonnextmsgcppzd.a		-DRTI_UNIX
			libnddscpp.so		-q[32|64] c
		Dynamic	libnddsc.so		-qlongdouble
			libnddscore.so
		Release
			For Connext Messaging, also include:
			librticonnextmsgcpp.so	-ldl -lnsl -lm
			libnddscppd.so	-pthread -brtl
		Dynamic	libnddscd.so
			libnddscored.so
		Debug
			For Connext Messaging, also include:
			librticonnextmsgcppd.so
			libnddscz.a
		Static Release	libnddscorez.a
			For Connext Messaging, also include:
			librticonnextmsgcz.a	-ldl -lnsl -lm
			libnddsczd.a	-pthread
		Static Debug	libnddscorezd.a		-DRTI_AIX
			For Connext Messaging, also include:
					-DRTI_UNIX
			librticonnextmsgczd.a
	C				-q[32|64] c
			libnddsc.so
					-qlongdouble
		Dynamic	libnddscore.so
					-qthreaded d
		Release	For Connext Messaging, also include:
			librticonnextmsgc.so	-ldl -lnsl -lm
			libnddscd.so	-pthread -brtl
		Dynamic	libnddscored.so
		Debug	For Connext Messaging, also include:
			librticonnextmsgcd.so
			nddsjava.jar
		Release	For Connext Messaging, also include:
	Java		rticonnextmsg.jar	N/A	N/A
			nddsjavad.jar
		Debug	For Connext Messaging, also include:
			rticonnextmsgd.jar

a.The Connext C/C++ libraries are located in $(NDDSHOME)/lib/<architecture>/. (where $(NDDSHOME) is where Connext is installed, such as /local/rti/ndds.5.0.x)

b.Transports (other than the default IP transport) such as StarFabric may require linking in additional libraries. For further details, see the online documentation or contact support@rti.com.

c.Use '-q32' if you build 32-bit code or '-q64' for 64-bit code.

5

d. The '-qthreaded' option is automatically set if you use one of the compilers that ends with ‘_r’, such as cc_r, xlc_r, xlC_r. See the IBM XLC reference manual for more information.

Table 2.3 Running Instructions for AIX Architectures

		Library
	RTI Architecture	Format	Required Environment Variables
		(Release &
		Debug)
	p5AIX5.3xlc9.0jdk	N/A	LD_LIBRARY_PATH=$(NDDSHOME)/lib/<arch>: $(LD_LIBRARY_PATH)a
			EXTSHM=ONb
	64p5AIX5.3xlc9.0jdk
	All other supported	Static	EXTSHM=ONb
			LD_LIBRARY_PATH=$(NDDSHOME)/lib/<arch>: $(LD_LIBRARY_PATH)
	architectures	Dynamic
			EXTSHM=ONb

a.${NDDSHOME} represents the root directory of your Connext installation. ${LD_LIBRARY_PATH} represents the value of the LD_LIBRARY_PATH variable prior to changing it to support Connext. When using nddsjava.jar, the Java vir- tual machine (JVM) will attempt to load release versions of the native libraries (nddsjava.so, nddscore.so, nddsc.so). When using nddsjavad.jar, the JVM will attempt to load debug versions of the native libraries (nddsjava.so, nddscore.so, nddsc.so).

b.See Notes for Using Shared Memory (Section 2.3.1).

Table 2.4 Library-Creation Details for AIX Architectures

	Library
RTI Architecture	Format	Compiler Flags Used by RTI a
	(Static &
	Dynamic)
		-q32 -qlongdouble -qalias=noansi -qpic=large -qthreaded
	Release	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
p5AIX5.3xlc9.0		-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+ -DNDEBUG
		-q32 -qlongdouble -qalias=noansi -qpic=large -qthreaded
	Debug	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
		-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+ -g
		-q64 -qwarn64 -qlongdouble -qalias=noansi -qpic=large -qthreaded
	Release	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
64p5AIX5.3xlc9.0		-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+ -DNDEBUG
		-q64 -qwarn64 -qlongdouble -qalias=noansi -qpic=large -qthreaded
	Debug	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
		-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+ -g
All supported AIX	Release	-target 1.4 -source 1.4
architectures for Java	Debug	-target 1.4 -source 1.4 -g

a. Connext was built using the 'xlC_r' compiler. See IBM's XLC reference manual for a description of the different com- pilers. For a list of the additional settings (defined by default) for the 'xlC_r' compiler, see the file, /etc/vac.cfg.53.

6

INTEGRITY Platforms

3	INTEGRITY Platforms
	Table 3.1 lists the architectures supported on the INTEGRITY® operating system.
Table 3.1 Supported INTEGRITY Target Platformsa
	Operating System	CPU	Compiler	IP Stack	RTI Architecture
					Abbreviation
	INTEGRITY 5.0.11	PPC	multi 4.2.4	GHnet2 IP stackb	ppc85xxInty5.0.11.xes-p2020
		85XX
	INTEGRITY 10.0.2 c	x86	multi 5.0.6	CHNet IPv4 stack	pentiumInty10.0.2.pcx86

a.For use with Windows and Solaris hosts, as supported by Green Hills Software.

b.Kernel must be built using -lip4 or -lip46.

c.Requires patch_6901.iff from Green Hills Software.

Table 3.2 lists the compiler flags and the libraries you will need to link into your application.

Table 3.2 Building Instructions for INTEGRITY Architectures

	API	Library	Required RTI Librariesa	Required	Required
		Format		System Librariesb	Compiler Flags
			libnddscppz.a
			libnddscz.a
		Static Release	libnddscorez.a
			For Connext Messaging, also include:
			librticonnextmsgcppz.a
	C++		libnddscppzd.a
			libnddsczd.a
			libnddscorezd.a
		Static Debug	(libnddscppzd.dba)c
			(libnddsczd.dba)c
			(libnddscorezd.dba)c	libsocket.a	RTI_INTY
			For Connext Messaging, also include:
				libnet.a
					--exceptions
			librticonnextmsgcppzd.a	libposix.a
			libnddscz.a
		Static Release	libnddscorez.a
			For Connext Messaging, also include:
			librticonnextmsgcz.a
	C		libnddsczd.a
			libnddscorezd.a
		Static Debug	(libnddsczd.dba)c
			(libnddscorezd.dba)c
			For Connext Messaging, also include:
			librticonnextmsgczd.a

a.The Connext C/C++ libraries are located in $(NDDSHOME)/lib/<architecture>/. (where $(NDDSHOME) is where Connext is installed, such as /local/rti/ndds.5.0.x)

b.Transports (other than the default IP transport) such as StarFabric may require linking in additional libraries. For further details, see the online documentation or contact support@rti.com.

c.The *.dba files contain the debugging information. You can link without these, as long as they are located in the same directory as the matching *d.a file (so that the MULTI® IDE can find the debug information).

7

Table 3.3 provides details on the environment variables required to be set at run time for an INTEGRITY architecture.

Table 3.3 Running Instructions for INTEGRITY Architectures

RTI Architecture	Required Environment Variables
All INTEGRITY architectures	None

Table 3.4 provides details on how the libraries were built. This table is provided strictly for informational purposes; you do not need to use these parameters to compile your application. You may find this information useful if you are involved in any in-depth debugging.

Table 3.4 Library-Creation Details for INTEGRITY Architectures

	RTI Architecture	Library	Compiler Flags Used by RTI
		Format
		Static	-bspname=pcx86 -prefixed_msgs --unknown_pragma_silent -G
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Release
			-DTARGET=\"pentiumInty10.0.2.pcx86\" -DNDEBUG -c
	pentiumInty10.0.2.pcx86
		Static	-bspname=pcx86 -prefixed_msgs --unknown_pragma_silent -G
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Debug
			-DTARGET=\"pentiumInty10.0.2.pcx86\" -c
		Static	-bspname=xes-p2020 -prefixed_msgs --unknown_pragma_silent
			-G -DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Release
			-DTARGET=\"ppc85xxInty5.0.11.xes-p2020\" -DNDEBUG -c
	ppc85xxInty5.0.11.xes-p2020
		Static	-bspname=xes-p2020 -prefixed_msgs --unknown_pragma_silent
			-G -DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Debug
			-DTARGET=\"ppc85xxInty5.0.11.xes-p2020\" -c

3.1Patch Required for INTEGRITY 10.02 Platform

To run a Connext application on an INTEGRITY 10.0.2 system, you must install patch_6901.iff from Green Hills Software. For more information, please contact your Green Hills Software representative.

3.2Support for Request-Reply Communication Pattern

RTI Connext Messaging includes support for the Request-Reply Communication Pattern for the platforms described in Table 3.1 and all programming languages, except as noted below.

When using C++, the following platform does not support the Request-Reply Communication Pattern:

❏ppc85xxInty5.0.11.xes-p2020

3.3Diagnostics on INTEGRITY Systems

Connext libraries for the INTEGRITY platforms use consolestring(), which prints debugging information to the serial console when available. Using the serial console as opposed to the target I/O window (host I/O) is generally recommended. Host I/O will affect the real-time performance of the target. For more information on consolestring(), please refer to the

INTEGRITY Development Guide.

8

INTEGRITY Platforms

3.4Socket-Enabled and POSIX-Enabled Threads are Required

Connext on INTEGRITY platforms internally relies on the POSIX API for many of its system calls. As a result, any thread calling Connext must be POSIX-enabled. By default, the 'Initial' thread of an address space is POSIX-enabled, provided the address space has been linked with libposix.a. Additional user threads that call Connext must be spawned from the Initial thread using pthread_create. Only then is the created thread also POSIX-enabled. Note that tasks created at build time using the Integrate utility are not POSIX-enabled.

Furthermore, threads calling Connext must be socket-enabled. This can be achieved by calling InitLibSocket() before making any Connext calls and calling ShutdownLibSocket before the thread terminates. Note that an Initial thread is, by default, socket-enabled when the address space is linked with libsocket.a. Please refer to the INTEGRITY Development Guide for more information.

3.5Running over IP Backplane on a Dy4 Champ-AVII Board

Connext can run on all four CPUs, provided the following hold true:

❏Connext applications on CPUs B, C and D only exchange data with applications on a different CPU or off-board.

❏The IP backplane and associated routing has been properly configured. Connext has been tested with the following libraries built into the INTEGRITY kernel: debug, res, load, socket, itcpip, lbp, queue, ifbp, idb, bsl.

3.6Multi-NIC Support on INTEGRITY 5.0

Due to limitations with the API of the InterPeak stack for INTEGRITY 5.0, Connext only supports a single NIC when the InterPeak stack is used. This NIC must be called “eth0”. By default on an INTEGRITY system, this will correspond to the first network card, which can be changed by reconfiguring the kernel. This limitation does not affect the InterNiche stack.

3.7Multicast Support

Multicast is supported on all INTEGRITY 5.0 and 10.0 platforms.

3.8Supported Transports

Shared memory: Supported, enabled by default. To clean up shared memory resources, reboot the kernel.

UDPv4: Supported, enabled by default.

UDPv6: Not supported.

TCP/IPv4: Not supported.

3.8.1Smaller Shared-Memory Receive-Resource Queue Size

INTEGRITY's shared-memory pluggable transport uses the shared-memory POSIX API. This API is part of the standard INTEGRITY distribution and is shipped as a library. The current version (5.0.4) of this library uses a hard-coded value for the total amount of memory that can be shared with an address space. This limits the overall buffer space that can be used by the DomainParticipants within the same address space to communicate over shared memory with other DomainParticipants.

9

To allow more DomainParticipants to run within the same address space, we reduced the default size of the queue for each receive resource of the shared memory transport. The queue size is reduced to 8 messages (the default for other platforms is 32). This change only applies to INTEGRITY architectures and this default value can be overwritten through the shared memory transport QoS.

3.8.2Using Shared Memory on INTEGRITY Systems

Connext uses the single address-space POSIX library to implement the shared-memory transport on INTEGRITY 10.0 operating systems.

To use shared-memory, you must configure your system to include the POSIX shared-memory library. The posix_shm_manager must be running in an "AddressSpace" solely dedicated to it. After building any Connext application that uses shared memory, you must use the intex utility (provided with the INTEGRITY development environment) to pack the application with multiple address-spaces: one (or more) to contain the Connext application(s), and another one to contain the posix_shm_manager.

Connext will run on a target without the posix_shm_manager, but the POSIX functions will fail and return ENOSYS, and the participants will fail to communicate through shared memory.

To include the POSIX Shared-Memory Manager in its own Address Space:

The project files generated by rtiddsgen for MULTI will create the shared-memory manager for you. Please follow these steps:

1.Specify the path to your INTEGRITY distribution in the _default.gpj top-level project file by adding the following line (modify it according to the path to your INTEGRITY distribution):

-os_dir=/local/applications/integrity/integrity-10.0.2

2.Build the project.

3.Before running your Connext application on a target, download the posix_shm_manager file (generated by the build) onto the target.

The POSIX Shared Memory Manager will start automatically after the download and your applications will be able to use shared memory.

Notes:

❏Only one posix_shm_manager is needed on a particular target. INTEGRITY offers the option of building this posix_shm_manager inside the kernel. Please refer to the INTEGRITY documentation.

❏If you are already using shared memory through the POSIX library, there may be a possible conflict.

❏INTEGRITY 5 has two different types of POSIX library: a single-address space one (or 'light') and another one (complete POSIX implementation). Connext uses the first one, but will work if you are using the complete POSIX implementation.

3.8.3Shared Memory Limitations on INTEGRITY Systems

If several applications are running on the same INTEGRITY node and are using shared memory, once an application is stopped, it cannot be restarted. When the application is stopped (gracefully or ungracefully), any new application on the same domain index within the same domain will fail to start until the shared memory manager is also restarted.

10

INTEGRITY Platforms

Additionally, if the application is stopped ungracefully, the remaining applications will print several error messages such as the following until Connext purges the stopped application from its database:

Resource Manager send error = 0x9

This error message is logged from INTEGRITY’s POSIX shared memory manager, not from Connext. The error message is benign and will not prevent the remaining applications from communicating with each other or with application on other nodes.

The workaround is to either restart the stopped application with a different participant index or shut down all the other applications and the shared memory manager, then restart everything.

3.9Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems

While the RTI libraries for INTEGRITY can be used with any BSP, providing the PowerPC processor falls under the same category (for example, the ppc7400... RTI libraries can be used on any target with a PPC74xx processor), rtiddsping and rtiddsspy are provided as executables, and therefore are BSP-dependent. You will not be able to run them successfully on your target if it is not compatible with the BSP listed in the architecture name (such as mvme5100-7400). Please refer to your hardware documentation for peripheral compatibility across BSPs.

3.10Monotonic Clock Support

The monotonic clock (described in Section 8.6 in the RTI Core Libraries and Utilities User’s Manual) is not supported.

3.11Support for Controlling CPU Core Affinity for RTI Threads

Support for controlling CPU core affinity (described in Section 19.5 in the RTI Core Libraries and Utilities User’s Manual) is not available for INTEGRITY platforms.

3.12Issues with INTEGRITY Systems

3.12.1Delay When Writing to Unreachable Peers

On INTEGRITY systems, if a publishing application’s initial peers list includes a nonexistent (or simply unreachable) host, calls to write() may block for approximately 1 second.

This long block is caused by the stack trying to resolve the invalid/unreachable host. Most IP stacks do not block the sending thread because of this reason, and you may include invalid/ unreachable hosts in your initial-peers list. If you find that your stack does block the sending thread, please consult your IP stack vendor on how to change its behavior. [RTI Issue ID CORE- 1637, Bug # 10768]

3.12.2Linking with ‘libivfs.a’ without a File System

If you link your application with libivfs.a and are using a system that does not have a file system, you may notice the application blocks for 2 seconds at start-up.

11

3.12.3Compiler Warnings Regarding Unrecognized #pragma Directives

Building Connext projects for INTEGRITY causes the compiler to produce several warnings about #pragma directives not recognized in some Connext header files. For example:

Building default.bld "C:/ndds/ndds.4.4x/include/ndds/dds_c/dds_c_infrastructure.h", line 926: warning: unrecognized #pragma

#pragma warning(push)

^

"C:/ndds/ndds.4.4x/include/ndds/dds_c/dds_c_infrastructure.h", line 927: warning: unrecognized #pragma

#pragma warning(disable:4190)

^

"C:/ndds/ndds.4.4x/include/ndds/dds_c/dds_c_infrastructure.h", line 945: warning: unrecognized #pragma

#pragma warning(pop)

^

These warnings do not compromise the final application produced and can be safely ignored.

3.12.4Warning when Loading Connext Applications on INTEGRITY Systems

When a Connext application compiled with the rtiddsgen-generated project files is loaded on an INTEGRITY 5.0.x target, the following warning appears:

"Warning: Program is linked with libc.so POSIX signals and cancellation will not work."

The Connext libraries do not use the additional features provided by the full POSIX implementation, therefore the warning can safely be ignored. This warning is due to the fact that the rtiddsgen-generated project files use the Single AddressSpace POSIX library by default, not the full POSIX implementation on INTEGRITY (POSIX System). The Connext libraries only require Single AddressSpace POSIX to function correctly, but will still work if you are using the POSIX System. The message indicates that items such as inter-process signaling or process- shared semaphores will not be available (more information can be found in the INTEGRITY Libraries and Utilities User's Guide, chapter "Introduction to POSIX on INTEGRITY").

12

Linux and Fedora Platforms

4 Linux and Fedora Platforms

First, see the basic instructions for compiling on Linux platforms provided in Section 9.3 in the

RTI Core Libraries and Utilities User’s Manual. The following tables provide supplemental information.

Table 4.1 on page 15 through Table 4.3 on page 16 list the supported Linux and Fedora architectures.

Table 4.4 on page 17 lists the compiler flags and libraries you will need to link into your application. See also: Monotonic Clock Support (Section 4.4).

Table 4.5 on page 18 provides details on the environment variables required to be set at run time for a Linux architecture. When running on 64-bit Java architectures (x64Linux2.6...jdk), use the - d64 flag in the command-line.

Table 4.6 on page 18 provides details on how the Linux libraries were built. This table is provided strictly for informational purposes; you do not need to use these parameters to compile your application. You may find this information useful if you are involved in any in- depth debugging.

Table 4.7 on page 21 and Table 4.8 on page 22 list additional libraries required when using the optional RTI Secure WAN Transport and RTI TCP Transport, respectively.

4.1Native POSIX Thread Library (NPTL) Requirements

This section applies only to these architectures:

❏ Yellow Dog Linux 4.0: ppc7400Linux2.6gcc3.3.3

To use the above architectures, you must have the development version of Native POSIX Thread Library (NPTL) installed on your host system, and the NPTL libraries on your target system.

❏When you build the application, you must have the development NPTL library installed in / usr/lib/nptl. This library is not installed by default.

❏To see if your system has NPTL installed, look for this directory: /usr/lib/nptl. It should contain these files: libpthread.so and libpthread.a.

If NPTL is not installed, you will need to install a package that includes it, such as nptl- devel. This package is not typically part of a default installation. You can find it either in your original Linux installation media (CD/DVD) or, if you have upgraded your system, through the distribution's update site.

❏When you run the application, it will automatically use the default NPTL library in /lib/ nptl. You do not need the development library installed on the target system.

Note: Make sure the environment variable LD_ASSUME_KERNEL is either not defined at all, or is set to 2.4.20 or higher. The middleware will not run if it is set to less than 2.4.20.1

1. The dynamic loader (ld), is configured by default to load the NPTL library, as long as LD_ASSUME_KERNEL is NOT defined.

13

4.2Multicast Support

Multicast is supported on all Linux and Fedora platforms and is configured out of the box. That is, the default value for the initial peers list (NDDS_DISCOVERY_PEERS) includes a multicast address. See the online documentation for more information.

4.3Supported Transports

Shared memory: Supported and enabled by default. To clean up shared memory resources, reboot the kernel.

UDPv4: Supported and enabled by default.

UDPv6: Supported for all platforms listed in Table 4.1 on page 15 through Table 4.3 on page 16 except SELinux 2.6.32 kernel (ppc4xxFPLinux2.6gcc4.5.1).

The UDPv6 transport is not enabled by default, and the peers list must be modified to support IPv6.

Note: Traffic Class support is only provided on architectures with gcc 4.1.0 or later that support the UDPv6 transport.

TCP/IPv4: Supported on CentOS 5.4 and 5.5, Red Hat Enterprise Linux 4.0 and higher (except Red Hat Enterprise Linux 5.2 with Real-Time Extensions), and Ubuntu Server 10.04. (This is not a built-in transport.)

4.3.1Shared Memory Support

To see a list of shared memory resources in use, please use the 'ipcs' command. To clean up shared memory and shared semaphore resources, please use the 'ipcrm' command.

The shared memory keys used by Connext are in the range of 0x400000. For example:

ipcs -m | grep 0x004

The shared semaphore keys used by Connext are in the range of 0x800000; the shared mutex keys are in the range of 0xb00000. For example:

ipcs -s | grep 0x008 ipcs -s | grep 0x00b

Please refer to the shared-memory transport online documentation for details on the shared memory and semaphore keys used by Connext.

4.4Monotonic Clock Support

The monotonic clock (described in Section 8.6 in the RTI Core Libraries and Utilities User’s Manual) is supported on all Linux, SUSE, and Fedora 2.6 kernel platforms.

4.5Support for Controlling CPU Core Affinity for RTI Threads

Support for controlling CPU core affinity (described in Section 19.5 in the RTI Core Libraries and Utilities User’s Manual) is available on all supported Linux, SUSE, and Fedora platforms.

Note: The API for controlling CPU core affinity may change in future releases.

4.6Libraries Required for Using RTI Secure WAN Transport APIs

This section is only relevant if you have installed RTI Secure WAN Transport. This feature is not part of the RTI Core Libraries and Utilities. If you choose to use it, it must be downloaded and

14

Linux and Fedora Platforms

installed separately. It is only available on specific architectures. See the RTI Secure WAN Transport Release Notes and RTI Secure WAN Transport Release Notes Installation Guide for details.

To use the WAN or Secure Transport APIs, link against the additional libraries from Table 4.7 on page 21. (Select the files appropriate for your chosen library format.)

4.7Libraries Required for Using RTI TCP Transport APIs

To use the TCP Transport APIs, link against the additional libraries from Table 4.8 on page 22. If you are using RTI TLS Support, see Table 4.9 on page 22. (Select the files appropriate for your chosen library format.)

Table 4.1 Linux Platforms on Cell BE CPUs

	Operating System	CPU	Compiler	RTI Architecture
				Abbreviation
	Fedora 12 (2.6.32 kernel)	Cell BE	gcc 4.5.1a, glib 2.9	cell64Linux2.6gcc4.5.1

a. Requires a custom version of gcc 4.5.1.

Table 4.2 Linux Platforms on Intel CPUs

	Operating System	CPU	Compiler			RTI Architecture
						Abbreviation
			gcc 4.1.2			i86Linux2.6gcc4.1.2
		x86
			Sun	Java	Platform	i86Linux2.6gcc4.1.2jdk
	CentOS 5.4, 5.5 (2.6 kernel)		Standard Edition JDK 1.6
			gcc 4.1.2			x64Linux2.6gcc4.1.2
		x64
			Sun	Java	Platform	x64Linux2.6gcc4.1.2jdk
			Standard Edition JDK 1.6
			gcc 4.4.5			i86Linux2.6gcc4.4.5
		x86
			Sun	Java	Platform	i86Linux2.6gcc4.4.5jdk
	CentOS 6.0		Standard Edition JDK 1.6
			gcc 4.4.5			x64Linux2.6gcc4.4.5
		x64
			Sun	Java	Platform	x64Linux2.6gcc4.4.5jdk
			Standard Edition JDK 1.6
	Fedora 12 (2.6.32 kernel)	x64	gcc 4.4.4			x64Linux2.6gcc4.4.4
	Fedora 12 (2.6.32 kernel) with gcc	x64	gcc 4.5.1a			x64Linux2.6gcc4.5.1
	4.5.1
			gcc 4.1.1			i86Linux2.6gcc4.1.1
		x86
			Sun Java Platform Stan-			i86Linux2.6gcc4.1.1jdk
	Red Hat Enterprise Linux 5.0 (2.6		dard Edition JDK 1.6
	kernel)		gcc 4.1.1			x64Linux2.6gcc4.1.1
		x64
			Sun Java Platform Stan-			x64Linux2.6gcc4.1.1jdk
			dard Edition JDK 1.6
			gcc 4.1.2			i86Linux2.6gcc4.1.2
		x86
	Red Hat Enterprise Linux 5.1, 5.2,		Sun	Java	Platform	i86Linux2.6gcc4.1.2jdk
			Standard Edition JDK 1.6
	5.4, 5.5 (2.6 kernel)
			gcc 4.1.2			x64Linux2.6gcc4.1.2
		x64
			Sun	Java	Platform	x64Linux2.6gcc4.1.2jdk
			Standard Edition JDK 1.6

15

Table 4.2 Linux Platforms on Intel CPUs

	Operating System	CPU	Compiler			RTI Architecture
						Abbreviation
	Red Hat Enterprise Linux 5.2 with		gcc 4.1.2			i86Linux2.6gcc4.1.2
		x86
			Sun	Java	Platform
	Real-Time Extensions (2.6 kernel)					i86Linux2.6gcc4.1.2jdk
			Standard Edition JDK 1.6
			gcc 4.4.5			i86Linux2.6gcc4.4.5
		x86
	Red Hat Enterprise Linux 6.0, 6.1 (2.6		Sun	Java	Platform	i86Linux2.6gcc4.4.5jdk
			Standard Edition JDK 1.6
	kernel)
			gcc 4.4.5			x64Linux2.6gcc4.4.5
		x64
			Sun	Java	Platform	x64Linux2.6gcc4.4.5jdk
			Standard Edition JDK 1.6
			gcc 4.1.0			i86Suse10.1gcc4.1.0
		x86	Sun Java Platform Stan-
			dard Edition JDK 1.5 and			i86Suse10.1gcc4.1.0jdk
	SUSE Linux Enterprise Server 10.1		1.6
	(2.6 kernel)		gcc 4.1.0			x64Suse10.1gcc4.1.0
		x64	Sun Java Platform Stan-
			dard Edition JDK 1.5 and			x64Suse10.1gcc4.1.0jdk
			1.6
			gcc 4.4.3			i86Linux2.6gcc4.4.3
		x86
			Sun Java Platform Stan-			i86Linux2.6gcc4.4.3jdk
			dard Edition JDK 1.6
	Ubuntu Server 10.04 (LTS)
			gcc 4.4.3			x64Linux2.6gcc4.4.3
		x64
			Sun Java Platform Stan-			x64Linux2.6gcc4.4.3jdk
			dard Edition JDK 1.6
	Wind River Linux 4	x64	gcc 4.4.1			x64WRLinux2.6gcc4.4.1
	(2.6 kernel)

a. Requires a custom version of gcc 4.5.1.

Table 4.3 Linux Platforms on PowerPC CPUs

	Operating System	CPU	Compiler		RTI Architecture
					Abbreviation
	Freescale P2020RDB	PPC 85xx	Freescale	gcc.4.3.74	ppc85xxLinux2.6gcc4.3.2
	(2.6.32 kernel)		based on gcc.4.3.2
	SELinux (2.6.32 kernel)	PPC 4xxFP	gcc 4.5.1a, glibc 2.9		ppc4xxFPLinux2.6gcc4.5.1
	Wind River Linux 3	PPC 85xx	gcc 4.3.2		ppc85xxWRLinux2.6gcc4.3.2
	Yellow Dog® Linux 4.0	PPC 74xx (such	gcc 3.3.3		ppc7400Linux2.6gcc3.3.3
	(2.6 kernel)	as 7410)

a. Requires a custom version of gcc 4.5.1.

16

Linux and Fedora Platforms

Table 4.4 Building Instructions for Linux and Fedora Architectures

		Library	Required	Required	Required
	API		RTI Libraries or
		Format		System Libraries	Compiler Flags
			Jar Filesa
			libnddscppz.a
		Static	libnddscz.a
			libnddscorez.a
		Release
			For Connext Messaging, also include:
			librticonnextmsgcz.a
				For all *Linux2.6gcc3*
			libnddscppzd.a
		Static	libnddsczd.a	architectures:
			libnddscorezd.a	-ldl -lnsl -lm
		Debug			64-bit architectures:
			For Connext Messaging, also include:	-L/usr/lib/nptl
					-DRTI_UNIX -m64
			librticonnextmsgcppzd.a	-lpthread -lrt
	C++
			libnddscpp.so		32-bit architectures:
			libnddsc.so	All other Linux
		Dynamic			-DRTI_UNIX -m32
			libnddscore.so	architectures:
		Release
			For Connext Messaging, also include:	-ldl -lnsl -lm
			librticonnextmsgcpp.so	-lpthread -lrt
			libnddscppd.so
		Dynamic	libnddscd.so
			libnddscored.so
		Debug
			For Connext Messaging, also include:
			librticonnextmsgcppd.so
			libnddscz.a
		Static	libnddscorez.a
		Release	For Connext Messaging, also include:
			librticonnextmsgcz.a	For all *Linux2.6gcc3*
			libnddsczd.a	architectures:
		Static	libnddscorezd.a	-ldl -lnsl -lm	64-bit architectures:
		Debug	For Connext Messaging, also include:	-L/usr/lib/nptl
					-DRTI_UNIX -m64
			librticonnextmsgczd.a	-lpthread -lrt
	C
			libnddsc.so		32-bit architectures:
		Dynamic	libnddscore.so	All other Linux
					-DRTI_UNIX -m32
		Release	For Connext Messaging, also include:	architectures:
			librticonnextmsgc.so	-ldl -lnsl -lm
				-lpthread -lrt
			libnddscd.so
		Dynamic	libnddscored.so
		Debug	For Connext Messaging, also include:
			librticonnextmsgcd.so
			nddsjava.jar
		Release	For Connext Messaging, also include:
	Java		rticonnextmsg.jar	N/A	None required
			nddsjavad.jar
		Debug	For Connext Messaging, also include:
			rticonnextmsgd.jar

a. RTI C/C++ libraries are in $(NDDSHOME)/lib/<architecture>/. RTI Java files are in $(NDDSHOME)/class/ (where $(NDDSHOME) is where Connext is installed, such as /local/rti/ndds.5.0.x).

17

Table 4.5 Running Instructions for Linux and Fedora Architectures

	RTI Architecture	Library Format	Environment Variables
	All supported Linux/		LD_LIBRARY_PATH= ${NDDSHOME}/lib/<architecture>:
		N/A	${LD_LIBRARY_PATH}a
	SUSE/Fedora		Note: For all 64-bit Java architectures (...64Linux...jdk), use
	architectures for Java
			-d64 in the command line.
	All other supported	Static (Release &	None required
		Debug)
	Linux/SUSE/Fedora
		Dynamic (Release	LD_LIBRARY_PATH= ${NDDSHOME}/lib/<architecture>:
	architectures
		& Debug)	${LD_LIBRARY_PATH}a

a. ${NDDSHOME} represents the root directory of your Connext installation. ${LD_LIBRARY_PATH} represents the value of the LD_LIBRARY_PATH variable prior to changing it to support Connext. When using nddsjava.jar, the Java virtual machine (JVM) will attempt to load release versions of the native libraries. When using nddsjavad.jar, the JVM will attempt to load debug versions of the native libraries.

Table 4.6 Library-Creation Details for Linux and Fedora Architectures

		Library
	RTI Architecture	Format	Compiler Flags Used by RTI
		(Static &
		Dynamic)
			-O3 -fPIC -mminimal-toc -mcpu=cell -mtune=cell -DLINUX -Wall
		Release	-Wno-unknown-pragmas -DRTS_UNIX -DPtrIntType=long
			-DCSREAL_IS_FLOAT -DCPU=cell
	cell64Linux2.6gcc4.5.1		-DTARGET=\"cell64Linux2.6gcc4.5.1\" -DNDEBUG -c -Wp,-MD
			-O3 -fPIC -mminimal-toc -mcpu=cell -mtune=cell -DLINUX -g -Wall
		Debug	-Wno-unknown-pragmas -DRTS_UNIX -DPtrIntType=long
			-DCSREAL_IS_FLOAT -DCPU=cell
			-DTARGET=\"cell64Linux2.6gcc4.5.1\" -c -Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Linux2.6gcc4.1.1\" -fmessage-length=0
	i86Linux2.6gcc4.1.1		-DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Linux2.6gcc4.1.1\" -fmessage-length=0 -c -Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Linux2.6gcc4.1.2\" -fmessage-length=0
	i86Linux2.6gcc4.1.2		-DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Linux2.6gcc4.1.2\" -fmessage-length=0 -c -Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Linux2.6gcc4.4.3\" -fmessage-length=0
	i86Linux2.6gcc4.4.3		-DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Linux2.6gcc4.4.3\" -fmessage-length=0 -c -Wp,-MD

18

			Linux and Fedora Platforms
Table 4.6 Library-Creation Details for Linux and Fedora Architectures
		Library
	RTI Architecture	Format	Compiler Flags Used by RTI
		(Static &
		Dynamic)
			gcc -m32 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=I80586 -DTARGET=\\"i86Linux2.6gcc4.4.5\\" -DNDEBUG
	i86Linux2.6gcc4.4.5		-Wp,-MD
			gcc -m32 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas
		Debug	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=I80586 -DTARGET=\\"i86Linux2.6gcc4.4.5\\" -Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Suse10.1gcc4.1.0\" -fmessage-length=0
	i86Suse10.1gcc4.1.0		-DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=I80586
			-DTARGET=\"i86Suse10.1gcc4.1.0\" -fmessage-length=0 -c
			-Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=PPC7400
	ppc7400Linux2.6gcc3.3.3 a		-DTARGET=\"ppc7400Linux2.6gcc3.3.3\" -DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=PPC7400
			-DTARGET=\"ppc7400Linux2.6gcc3.3.3\" -c -Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=4xxFP
	ppc4xxFPLinux2.6gcc4.3.3		-DTARGET=\"ppc4xxFPLinux2.6gcc4.3.3\" -DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=4xxFP
			-DTARGET=\"ppc4xxFPLinux2.6gcc4.3.3\" -DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -O -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=4xxFP
	ppc4xxFPLinux2.6gcc4.5.1		-DTARGET=\"ppc4xxFPLinux2.6gcc4.5.1\" -DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=4xxFP
			-DTARGET=\"ppc4xxFPLinux2.6gcc4.5.1\" -DNDEBUG -c -Wp,-MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Release	-DPtrIntyType=long -DCREAL_IS_FLOAT -DCPU=e500
	ppc85xxLinux2.6gcc4.3.2		-DTARGET=\"ppc85xxLinux2.6gcc4.3.2\" -DNDEBUG -c -Wp, -MD
			-fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntyType=long -DCREAL_IS_FLOAT -DCPU=e500
			-DTARGET=\"ppc85xxLinux2.6gcc4.3.2\" -c -Wp, -MD
			-mcpu=powerpc -msoft-float -fPIC -DLINUX -O -Wall
		Release	-Wno-unknown-pragmas -DRTS_UNIX -DPtrIntType=long
			-DCSREAL_IS_FLOAT -DCPU=PPC32
	ppc85xxWRLinux2.6gcc4.3.2		-DTARGET=\"ppc85xxWRLinux2.6gcc4.3.2\" -DNDEBUG -Wp,-MD
			powerpc-wrs-linux-gnu-gcc -mcpu=powerpc -msoft-float -fPIC
		Debug	-DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=PPC32
			-DTARGET=\"ppc85xxWRLinux2.6gcc4.3.2\" -Wp,-MD

19

Table 4.6 Library-Creation Details for Linux and Fedora Architectures

		Library
	RTI Architecture	Format	Compiler Flags Used by RTI
		(Static &
		Dynamic)
			-m64 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=AMD64 -DTARGET=\"x64Linux2.6gcc4.1.1\"
	x64Linux2.6gcc4.1.1a		-DNDEBUG -c -Wp,-MD
			-m64 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=AMD64
			-DTARGET=\"x64Linux2.6gcc4.1.1\" -fmessage-length=0 -c
			-Wp,-MD
			-m64 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=AMD64 -DTARGET=\"x64Linux2.6gcc4.1.2\"
	x64Linux2.6gcc4.1.2 a		-DNDEBUG -c -Wp,-MD
			-m64 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=AMD64
			-DTARGET=\"x64Linux2.6gcc4.1.2\" -fmessage-length=0 -c
			-Wp,-MD
			-m64 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
	x64Linux2.6gcc4.3.4		-DCPU=AMD64 -DTARGET=\"x64Linux2.6gcc\" -c -Wp,-MD
			-m64 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=AMD64
			-DTARGET=\"x64Linux2.6gcc4.3.4\" -c -Wp,-MD
			-m64 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=AMD64 -DTARGET=\"x64Linux2.6gcc4.4.4\"
	x64Linux2.6gcc4.4.4 a		-DNDEBUG -c -Wp,-MD
			-m64 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=AMD64
			-DTARGET=\"x64Linux2.6gcc4.4.4\" -c -Wp,-MD
			-m64 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=AMD64 -DTARGET=\"x64Linux2.6gcc4.4.3\"
	x64Linux2.6gcc4.4.3		-DNDEBUG -c -Wp,-MD
			-m64 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas -DRTS_UNIX
		Debug	-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=AMD64
			-DTARGET=\"x64Linux2.6gcc4.4.3\" -fmessage-length=0 -c
			-Wp,-MD
			gcc -m64 -fPIC -DLINUX -O -Wall -Wno-unknown-pragmas
		Release	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=AMD64 -DTARGET=\\"x64Linux2.6gcc4.4.5\\"
	x64Linux2.6gcc4.4.5		-DNDEBUG -Wp,-MD
			gcc -m64 -fPIC -DLINUX -g -Wall -Wno-unknown-pragmas
		Debug	-DRTS_UNIX -DPtrIntType=long -DCSREAL_IS_FLOAT
			-DCPU=AMD64 -DTARGET=\\"x64Linux2.6gcc4.4.5\\" -Wp,-MD