
May I ask you what distro you have then?
I'm moving to Debian Sarge this weekend. If everything goes as planned, that is.
Moderator: OpenTTD Developers
That doesn't fix my problem. You properly compiled to a i386. I'm trying to port it to mac, and as we all know, they aren't based on x86 cpus.MadEgg wrote:Look at my previous post in this thread, it containts a tgz file with Linux binaries in it.
Are you really using Linux? Generally the Linux include files define a value to show the #ifdefs that you're using it. If it doesn't work, look for these #ifdefs and hardcode to linux. Also remove the lines that include win32.cBjarni wrote:When I compile, I get this
Compiling win32.c (76 errors)
win32.c:6: header file 'windows.h' not found
win32.c:7: header file 'mmsystem.h' not found
win32.c:9: header file 'winnt.h' not found
How did you manage to avoid the windows only files?
I was actually replying to Eirik with that post.Bjarni wrote:That doesn't fix my problem. You properly compiled to a i386. I'm trying to port it to mac, and as we all know, they aren't based on x86 cpus.MadEgg wrote:Look at my previous post in this thread, it containts a tgz file with Linux binaries in it.
What should I do with win32.c, when I'm not using windows
Code: Select all
make
Code: Select all
#include <sys/statfs.h>
Code: Select all
#include <sys/stat.h>
If you don't like it because you can't do that, then why not just change settings so that you can? You talk like you're a Linux pro... Log in as root and change the permissions so that whatever your normal log-on is can access those directories/files... Pretty simple to do...Saskia wrote:Because GCC is a bit complicated and sensitive for different versions of it's main package, the compiler modules, the library, and so on. And then it's very difficult to find the source of your problems, because the compiler messages get microsoftified: they don't point to the right problem - the wrong library for example!GoneWacko wrote: Anyways, why would it be dangerous to reinstall GCC. If it would be dangerous, then why would it be in YaST ?Anyway, the kernel is in YaST too, or isn't it?
I don't have SuSE, I hate it, it's like Windows ... it don't even lets you set the rights of your files, or edit something in /etc!
This is going quite offtopic but that's about one of the worst things you can do. The reason normal users can't do that is so that you(or any virus-like program) can't mess the whole system up, in the worst case only your own home-directory...petteyg359 wrote: If you don't like it because you can't do that, then why not just change settings so that you can? You talk like you're a Linux pro... Log in as root and change the permissions so that whatever your normal log-on is can access those directories/files... Pretty simple to do...
You could open unix.c and replace every occurence of statvfs with statfs.(so also change the #include <sys/statvfs.h> to #include <sys/statfs.h>.Bjarni wrote:I started all over and downloaded the new code, but I still have problems![]()
When I write make, it compiles and give this error:
gcc -g -Wall -Wno-multichar `sdl-config --cflags` -DUNIX -DWITH_SDL -c unix.c
unix.c:10:25: sys/statvfs.h: No such file or directory
unix.c: In function `FiosGetDescText':
unix.c:143: error: storage size of `s' isn't known
unix.c:145: warning: implicit declaration of function `statvfs'
unix.c:143: warning: unused variable `s'
Help. Please. Really want this to work
Code: Select all
find /usr/include -iname 'statfs.h'
Code: Select all
locate statfs.h
Users browsing this forum: Amazon [Bot] and 21 guests