Jacobo,
I am indebted to your keen eye! The second machine is a Core i5 CPU and
was running 64 bit Windows 7 until recently. I would appear that when I
installed Linux MINT I somehow got a 32 bit Linux installed without
noticing. I shall endeavour to correct that and see if things improve.
But from what I'm reading it would seem:
* 32 bit and 64 bit binaries differ
* 32 bit binaries will run on a 32 bit or 64 bit OS (generally)
* 64 bit binaries will not run on a 32 bit OS only on 64 bit OS
* By inference there are 32 bit and 64 bit .deb packages and the
package manager (apt) chooses the appropriate one.
Do forgive my learning curve here. Not meaning to waste anyone's time
getting up to speed on how best to contribute. Have not worked actively
on Unix/Linux systems since about 1993 bar a few sojourns and much has
changed of course (and much hasn't - vi is still it seems popular ;-).
Regards,
Bernd.
On 02-Mar-16 08:41 AM, Jacopo De Simoi wrote:
Hi there
CPU~Quad core Intel Core i7-4790 (-HT-MCP-) speed/max~3600/4000 MHz
Kernel~3.16.0-38-generic x86_64 Up~5 days Mem~9124.3/32052.5MB
HDD~3688.8GB(71.2% used) Procs~275 Client~Shell inxi~2.2.28
CPU~Dual core Intel Core i5-4250U (-HT-MCP-) speed/max~1196/2600 MHz
Kernel~3.19.0-32-generic i686 Up~1 day Mem~1235.8/16107.5MB
HDD~250.1GB(9.0% used) Procs~206 Client~Shell inxi~2.2.28
the x86_64 above says that you are running a 64 bit environment on the first
machine; the i686 below says that you are running a 32 bit environment on the
second machine.
When you compile on the first machine you are compiling a 64 bit runtime, which
cannot run on a 32 bit system.
There are some ways to compile a 32 bit program on a 64 bit system, but you
should also link to all 32 bit libraries and stuff, which makes it a non-
trivial, (yet instructive) endeavor to do on your own.
Cheers
__J
