Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I'm trying to assist someone across the ocean who's having trouble running a 32 bit application on a 64 bit machine. I'm assuming that the app was compiled with 64 bit flags (openSuSE's build), although there are no flags or code for 64 bit usage in the app (it was written many years ago, when 32 bits was bleeding edge).
For example, there are some fstat() calls, involving the stat struct. Presumably that's all compiled as 64 bit, but then things like file mtime timestamps are copied from 64 bit (?) fields to 32 bit variables. Could this be causing strange problems? I can't debug it myself, as I'm only on a 32 bit machine, and this other guy has minimal development skills. If I can figure out where to start making this app 64 bit friendly, I could send the modified code over to him to rebuild and test. Anyone care to donate a 64 bit machine? :-)
Assuming that some sort of 32/64 bit conflict is the root of the problem, what things should I be looking at? time_t timestamps, ftell()/fseek() file offsets, what else? Are flags for 64 bits standardized (I see several different ones in the GNU C library)? Is there a good on-line source of information for how to proceed? Thanks much for any help!

![]() |
Freespire error code 224
|
PS/2 problem DeLi Linux
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |