I have COMPILED the gtk client crossfire-client-1.6.0:
In:
Slack 9.1:
GTK 2.2.4
GCC 3.2.3
./configure --disable-alsa --disable-alsa9
Actually the clients starts and connects to the servers, I can create a new player and do everything BUT MOVE then the client crashes with segmentation fault.
I more info is nedded to track this behaviour request.
Thanx in advance
GTK Client Crashes when move
Moderator: Board moderators
- Cid Highwind
- Luser
- Posts: 33
- Joined: Tue Feb 10, 2004 12:27 am
Try the newer 1.6.1 client tarball or CVS for starters - depending on the server you are using there have been changes to the client that could cause problems (especially older client - newer server and vice versa)
also not sure that GTK2 is good for compiling, I seem to recall something about the GTK client is still relying on older GTK libraries- especially something about key mappings. I could be way off here however and woefully out of touch - we would need more info to figure out the problem really.
Also you can try the crossfire #irc channel or a message to the mailing list for more detailed troubleshooting there is usually linux support hanging around. I haven't had problems compiling since the image code changes just before 1.6.0 but I'm on debian and haven't tried it on slackware.
also not sure that GTK2 is good for compiling, I seem to recall something about the GTK client is still relying on older GTK libraries- especially something about key mappings. I could be way off here however and woefully out of touch - we would need more info to figure out the problem really.
Also you can try the crossfire #irc channel or a message to the mailing list for more detailed troubleshooting there is usually linux support hanging around. I haven't had problems compiling since the image code changes just before 1.6.0 but I'm on debian and haven't tried it on slackware.
Under Windows, I compiled the GTK client using GTK2. There are a few flags to set, but apart that it works perfectly well.Avion wrote:also not sure that GTK2 is good for compiling, I seem to recall something about the GTK client is still relying on older GTK libraries- especially something about key mappings.
I suggest you check Win32-specific settings, in gtk/win32/config.h
The following flags are set for GTK2:
* GTK_ENABLE_BROKEN
* GTK_WINDOW_DIALOG GTK_WINDOW_TOPLEVEL
* #define GC GdkGC (this one may break something under Linux, no clue what it does

* G_DISABLE_CONST_RETURNS
Cid, unless you are using slackware linux 9.1 then your posts in this thread are just confusing the issue. This crossposting has got to stop - it makes it twice as hard to help or carry on a conversation when people are constantly posting extraneous things. I am very happy there is a client for windows and that it is being worked on but this poor fellow is not using it, he's using the linux GTK client and has a problem we would like to solve.
I have always used the older GTK libs to compile the client on my debian LINUX system, I am not sure if the GTK 2 libs will work for LINUX. If you can get the older GTK 1.2 development libraries and compile with those perhaps you might have better luck.
I have always used the older GTK libs to compile the client on my debian LINUX system, I am not sure if the GTK 2 libs will work for LINUX. If you can get the older GTK 1.2 development libraries and compile with those perhaps you might have better luck.
-
- Forum Aficionado
- Posts: 1994
- Joined: Tue Apr 29, 2003 5:55 pm
- Location: Minnesota, USA
- Contact:
NOTE: moved the question and response related to the Win GTK client and black screen/illegal operation to it's own thread.
http://www.metalforge.net/cfmb/viewtopic.php?t=309
http://www.metalforge.net/cfmb/viewtopic.php?t=309