Return to Question

Here is the prequal to my problem. After much sweat and swearing I managed to cross-compile and deploy my binary from the notebook onto the RPi2. And here is the problem:

Here is the prequal to my problem. After much sweat and swearing I managed to cross-compile and deploy my binary from the notebook onto the RPi2. And here is the problem:

EDIT 2: As @gogoud suggested:

• Changed to key authentification
• Checked shell on my RPi - it is bash
• Added RequestTTY=force to a newly created ~/.ssh/config

No change at all. Same old story. I did however notice the actual exit code: 2. From TLDP:

2: Misuse of shell builtins (according to Bash documentation) Example: empty_function() {} Comments: Missing keyword or command, or permission problem (and diff return code on a failed binary file comparison).

This doesn't make sense for my binary (I think). I have also checked the permissions on it: drwxr-xr-x. This means that all can execute and read it.

Also I used the g++-arm-linux-gnueabihf that is in my Raspbian to compile a new binary in order to compare both. The output of ldd is literally the same with the small exception that I have different memory addresses (the HEX numbers in brackets) where the libs will be loaded.