Floating point exception / Compiling a c++ program

[olacelle]

Hi,

I developed a c++ program on a centos(Red-Hat based) computer which I'm trying to run on a Voyage-Linux(Debian-based) computer.

The program compiles and runs fine on my centos. It also runs fine on my iMedia embedded linux computer.

On the Voyage-Linux when I run the program it says

Floating Point Exception

I figured I needed to compile my program on my Voyage-Linux but I have no graphic tools to do so and I'm not quite sure how to do it "by hand".

I was able to do it with a simple hello world program which is only 1 cpp file by doing

gcc helloworld.cpp -o helloworld

, but my project has several cpp and h files and I havn't found a lot of information about accomplishing that kind of task.

Am I heading in the correct direction?
If so how should I do it?
If not what else could be done?

Thanks.

Olivier.

[coopstah13]

How are you building it on your centos computer? The defacto standard is to use makefile's. I'm going to go out on a limb here and guess your voyage linux and centos computers are running different processor architectures, which would explain why the binary wouldn't just run (assuming all the required libs are there too)

[olacelle]

I'm using KDevelop on my Centos to develop, and the "build project" menu option does it all for you. I believe it runs automake, configure and compiles the project.

I'm not sure about the processors but the programs ran fine with my iMedia distro on the same machine I'm using for the Voyage distro.

I'm pretty sure all the libraries are there since I installed the build-essential package.

I know there are Makefiles involved but I don't know how to generate them or do what in what order...

[coopstah13]

i will simplify my question, is the voyage distro 32 or 64 bit? and what is the centos?

[olacelle]

Both 32 bit

[Rubberman]

I assume you simply copied the executable to the new system? If so, then it is likely that your shared libraries are not compatible, unless you built it statically (no shared libraries).

[olacelle]

You are right I just copied the executables.

[Rubberman]

You are right I just copied the executables.

Then you likely have an incompatibillity with the shared libraries used. In order to get an executable to run on systems other than ones very closely compatible with the one you built it on, then you need to tell the linker to do static linking so that shared libraries are not used. In such a case, as long as the kernel versions of the systems are close, then you should be ok. The resulting executable will be larger, but it will run on more target systems.

Normally, people build the software on the target system in order to avoid this situation.

[olacelle]

I don't know how to do static linking but I'll see what I can figure out.

As far as building the software on the target system which I was able to do it but that is a challenge for me too.

Thanks for the info.

[coopstah13]

which I think brings us back to OP's other question, which was how to build the application on this machine. I'm surprised if kdevelop does all those other things for you that there isn't some way to generate a makefile for it or a configure script, etc.