Binary generated by gcc on BSDI are portable or not ?

[rajabb]

Hi,

I want to know that if i compile a c++ code using g++ on one BSDi box and put it on any other BSDi box which is not having gcc , will it work ?

Also when i tried with a binary generated on FreeBSD (as o/p of g++ only) and when i execute, it give me following error -
$./a.out
bash: ./a.out: No such file or directory

and when i run ldd for it -
$ ldd ./a.out
ldd: can't execute ./a.out (No such file or directory)

but when i run nm -
$ nm ./a.out
00000000 f Test.cpp
0804969c A _DYNAMIC
08049754 A _GLOBAL_OFFSET_TABLE_
.
.
blah blah

can any one help me out that what can be reason for it

thanks,
Raja

[redhead]

The reason the a.out isn't working is because it's linked to some sort of library, which is present at compile time but not at run time, you'r nm command will tell you what a.out is trying to get in contact with during it's run.
The way you'd make anything usable on any BSDi box, is to ensure the libraries it needs will be present on the target box, thus using dependensies.

[teknomage1]

Or compile the program statically, I think the gcc flag for that is --static. That way the binary will be self cintained and have no external dependencies.