Error starting remote application

QNX USERS QNX6 - OS
1

Hi all,
I am using QNX Momentics on a Linux machine (Ubuntu 8.10), and the x86-linux-gcc as a cross-compiler.
I successfully cross-compile my software(driver+application) to remote QNX6.3.2 target machine(installed on a Lippert Cool Front Runner PC104 board) from the Linux machine. Then I have no problem in running the QNX driver remotely, but when I try to run the application (which is a client of the QNX driver), it fails with the error below. Has anyone got any ideas on why would the driver run remotely, but not the application?

Error starting remote application.
com.qnx.tools.utils.target.QConnException: Target launcher@localhost:8000: Error Can’t access shared library
at com.qnx.tools.utils.target.TargetBinary.parseResponse(TargetBinary.java:130)
at com.qnx.tools.utils.target.TargetServiceLaunch.launch(TargetServiceLaunch.java:136)
at com.qnx.tools.utils.target.TargetProcess.startProcess(TargetProcess.java:46)
at com.qnx.tools.utils.target.TargetProcess.(TargetProcess.java:15)
at com.qnx.tools.ide.qde.internal.ui.launch.QDELaunchUtils.remoteLaunch(QDELaunchUtils.java:236)
at com.qnx.tools.ide.qde.internal.ui.launch.QDELaunchConfigurationDelegate.startApplicationOnTarget(
QDELaunchConfigurationDelegate.java:579)
at com.qnx.tools.ide.qde.internal.ui.launch.QDELaunchConfigurationDelegate$1.doRun(QDELaunchConfigurationDelegate.java:
879)
at com.qnx.tools.ide.qde.internal.ui.launch.QDELaunchConfigurationDelegate$QDELaunchJob.run(
QDELaunchConfigurationDelegate.java:176)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58 )

2

Error Can’t access shared library

This means you have a linked library in your application, which is not present at your target system itself.

But from the launcher@localhost:8000 i wonder if your target is set to localhost, which would then not be your remote QNX but your Linux itself.

3

Thank you very much for being interested micro. Yes, you’re right, the err msg “Can’t access shared library” is the key point here. But since the application is linked to the static shared library and then executed, I cannot figure out why would it not be able to find it at the target.
By the way, I am sure my target is set to the remote Lippert card within the LAN because I use the same QConn configuration to download code for both the driver, which succeeds, and the linked application, which fails.

4

Problem solved. I noticed that I forgot to change the target environment variable in .bashrc to qnx. Therefore, whole application source code was being compiled for Linux, not qnx, and the linked library was of course unreachable. Sorry for bothering, it was a careless mistake of me.