smaug.exe wont run after successful compile

i get this message:
this is stock 1.7 version of FUSS

$ ../src/smaug
../src/smaug: ../src/smaug: cannot execute binary file

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




my stock 1.6 version of FUSS runs fine after compile.

$ file smaug.exe
smaug.exe: PE executable for MS Windows (console) Intel 80386 32-bit






why is the file information so dramatically different? Are those versions and 64bit/32bit information decided by makefile? How would I go about fixing this?

Are the permissions correct?

What is your system info (computer) that is trying to run it?

For some reason your compiler is generating 64-bit code; it probably thinks (correctly one hopes??) that you are on a 64-bit system. But you probably don't want to do that in general on a Windows machine, because you probably don't have the proper 64-bit system libraries and all that set up.

This is gcc under Cygwin, right? What version of gcc, and is your Cygwin installation up to date?

yes - it is cygwin under windows environment. i dont know why it is compiling it as 64 bit code. it works though even though i have a 32 bit processor.

I guess I figured out the problem because zeno was wondering about the permissions of the files. While I was comparing the permissions, I realized that in my directory where smaug.exe is there is also another "binary" file called just plain old smaug with no extension. when i was trying to start up smaug.exe i was just using ../src/smaug which was then making a call to the one with no extension because it is an exact match.

i was then able to run smaug after typing ../src/smaug.exe

I simply changed the smuag "whatever" binary file to smaug.backup in case i needed it(so far I havent:). Now I can just ../src/smaug without any problems.

1.6 or 1.8 do not have the extra smaug "binary" file in the stock release but 1.7 does. go figure. It's 3mb big. Are they padding the download size? jk:)