On 14-09-22 03:54 AM, Anton Indrawan wrote:
> Hi guys,
>
> I understood that binaries produced by QNX 6.5 toolchain will work on QNX 6.6 targets. I was wondering whether the 
other way around would work. So, I created a hello world application which basically does a printf, compiled with QNX 6.
6's QCC, deployed on a QNX 6.5 target and that worked. However, when I was using std::pow, it threw a memory fault.

Running newer binaries on older versions of the OS might work, but it's 
not guaranteed to work so it's an unsupported use case.

> Note: I statically linked the program against libcpp and libm using the -Bstatic option. Can somebody confirm that 
this is the right way to statically link to the static libcpp library.

Yes, but leaving it without a -Bdynamic, means the -lc that the compiler 
drivers automatically link in will be statically linked as well. If you 
want to create a full static binary, then you should link with -static. 
If you still want dynamically linked program, you need to link against 
libc.so, in which case you should to do, -Bstatic -lcpp -Bdynamic

Regards,

Ryan Mansfield

Why would you want to do that ?

-----Message d'origine-----
De : Anton Indrawan [mailto:community-noreply@qnx.com] 
Envoyé : 22 septembre 2014 03:55
À : general-toolchain
Objet : QNX SDP 6.6 binary compatibility on a QNX SDP 6.5 target

Hi guys,

I understood that binaries produced by QNX 6.5 toolchain will work on QNX 6.6 targets. I was wondering whether the other
 way around would work. So, I created a hello world application which basically does a printf, compiled with QNX 6.6's 
QCC, deployed on a QNX 6.5 target and that worked. However, when I was using std::pow, it threw a memory fault.

Here is the test code:
#include <stdio.h>
#include <math.h>

int main()
{
  double result = std::pow(2.0, 2);
  printf("Result: %lf\n", result);
  return 0;
}

Compile with: QCC -Vgcc_ntoarmv7le -Bstatic -lcpp math.cpp -lm.

Note: I statically linked the program against libcpp and libm using the -Bstatic option. Can somebody confirm that this 
is the right way to statically link to the static libcpp library.

Best regards,
Anton



_______________________________________________

General
http://community.qnx.com/sf/go/post111814
To cancel your subscription to this discussion, please e-mail general-toolchain-unsubscribe@community.qnx.com