Shouldn't one build run in different machines?

[portilhe]

I haven't had the time to look at this since yesterday, but to answer your question quickly, the application does nothing at all. The error message is
"bash: ./MisterMand: no se puede ejecutar el fichero binario" (which is spanish for "cannot execut binary file").
-Manu

[squidge]

You have made sure that the executable bit is set?

[portilhe]

Yes, I did do that (chmod 700 ...)

[schnitzel]

please show the output from the following commands:

file ./MisterMand
uname -a

file ./MisterMand
uname -a

To copy to clipboard, switch view to plain text mode 

btw: you can't run a 64bit executable on a 32bit machine - (unless your pc has certain virtualization capabilities, then you could run the 64bit executable in a 64bit linux guest virtual machine).
You could build a 32bit executable on a 64bit machine by using the -march gcc compile option.

[portilhe]

The code is

$ file ./MisterMand
./MisterMand: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

$ file ./MisterMand
./MisterMand: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

To copy to clipboard, switch view to plain text mode 

$ uname -a
Linux nico-laptop 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:21 UTC 2011 i686 GNU/Linux

$ uname -a
Linux nico-laptop 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:21 UTC 2011 i686 GNU/Linux

To copy to clipboard, switch view to plain text mode 

I guess that means I really need to link statically, right?

[wysota]

No, it means you need to build the program for 32 bit architecture. You are currently pouring petrol into a diesel engine and pouring petrol from another gas station will not change a thing. You need a diesel (aka 32bit binary).

[schnitzel]

The code is

$ file ./MisterMand
./MisterMand: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

$ file ./MisterMand
./MisterMand: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

To copy to clipboard, switch view to plain text mode 

$ uname -a
Linux nico-laptop 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:21 UTC 2011 i686 GNU/Linux

$ uname -a
Linux nico-laptop 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:21 UTC 2011 i686 GNU/Linux

To copy to clipboard, switch view to plain text mode 

I guess that means I really need to link statically, right?

not neccesarily - you *can* bundle all libs and executable together into an installer (this is a good read for you: http://doc.qt.nokia.com/4.7/deployment.html)
but... your target architecture needs to be compatible with the produced executable. This doesn't seem to be the case in your example: 32bit target trying to run 64bit executable
This will not work regardless of whether you build the app dynamic or static.

arrgggh [wysota beat me to it]

[portilhe]

Thanks everyone! I shall now embark on a journey to learn how to do that (compile for 32bit on a 64bit machine).
Cheers,
-Manu

[schnitzel]

or (if you have oodles of diskspace and a decent amount of RAM) you could install a 32bit linux guest os in a virtual machine on your 64bit linux host (check out oracle's virtualbox)

[wysota]

Or a chrooted build environment.

Google for "linux compiling for 32 bits on 64 bit machine"