Date of this edition: March 08, 2007
Target OS: QNX® Neutrino® 6.3.0 SP1
Host OS: Microsoft Windows Vista, XP SP1 or SP2, 2000 SP4, or NT 4 SP6a; Sun Solaris 8, 9, or 10; QNX® Neutrino® 6.3.0 SP1; Linux Red Hat 8 or 9, Red Hat Enterprise WS 3 or 4, Red Hat Fedora Core 3 or 4, Debian 3.1, or SUSE 10
![]() |
For information about the issues that this patch addresses, see the release notes. |
This note includes:
$ qconfig QNX Installations Installation Name: QNX Momentics 6.3.0 Version: 6.3.0 Base Directory: /usr/qnx630/ QNX_HOST: /usr/qnx630/host/qnx6/x86/ QNX_TARGET: /usr/qnx630/target/qnx6/
The base directory in this example is /usr/qnx630/, but it could be different on your machine, depending on your host and where you installed QNX Momentics.
copy drive:\patch-630SP1-0488-qconn-401.tar base_dir
cd base_dir
tar -xvf patch-630SP1-0488-qconn-401.tar
Open a command shell and use the following commands (replacing base_dir with the path from step 2, and archive_path with the full path to the downloaded archive):
cd base_dir
tar -x -v -f archive_path/patch-630SP1-0488-qconn-401.tar
![]() |
If you use WinZIP, choose , switch to the Miscellaneous tab in this dialog, and de-select the TAR file smart CR/LF conversion option. If this option is selected, and you extract the archive, then your shiplist file will contain ^M characters. |
The patch is installed in the base_dir/patches/630SP1-0488/ directory. This directory includes the following:
Next, you must determine how to incorporate the patch into your host system. The patch is stored in a directory (or folder) that's separate from your development system. This structure allows you some flexibility in how to apply the patch.
There are three methods for using a patch:
In the first method, you can use the files in the patch by simply modifying buildfiles to include the full path to the files in the patch subdirectory. This method lets you test the patch before committing to it, without affecting your development host. If you choose to stop using the patch, you only need to change the buildfiles to the original location.
You can use a similar approach that involves creating an "override" tree. You can notify the system builder and mkifs utilities to look for binaries in a particular subdirectory before looking in the standard location ($QNX_TARGET).
To create an override tree from the command line:
The third method replaces the files on your development host with the patched files.
![]() |
Since this is a destructive procedure, we recommend that you create a backup of the affected files. |
To create a backup on any of our hosts:
cd base_dir
pax -w < patches/630SP1-0488/shiplist > patches/630SP2-0337-backup.tar
You can use whatever name you prefer for the backup archive. The pax utility might display some error messages when it attempts to back up nonexistent files for host operating systems other than the one you're using. You can safely ignore these messages.
To apply the patch on a Windows system from the command prompt (remember to change back to cmd.exe from ksh):
cd base_dir\patches\630SP1-0488
cp -Rp target base_dir\.
To apply the patch on a Neutrino, Linux, or Solaris system:
cd base_dir/patches/630SP1-0488
cp -Rp target base_dir/.
cd target/qnx6/x86 cp -fRp . /
After installing this patch, you need to update the version of qconn on your target machine. How you do this depends on your target system; you might have to build a new image, or you might simply have to copy the new version to your target. For example:
If you have any questions, comments, or problems with a QNX product, please contact Technical Support. For more information, see the How to Get Help chapter of the Welcome to QNX Momentics guide or visit our website, www.qnx.com.