While hunting a bug reported on fink-users under "fink vpython2.5 fails to run", I learned that if tcltk is built while xquartz-2.3.0 is installed, it will crash when running anything tk-related.

The cause is the introduction of a new X event and corresponding redefinition of the macro LASTEvent in <X11/X.h> that the Tk guys thought was fixed for eternity (used to be 35 for the last 20 years, is now 36).

This same bug came up also on the x11-users list
<http://lists.apple.com/archives/X11-users/2008/Jul/msg00139.html>

There is a recent discussion on the tcl newsgroup
<http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/3a3fedad45fecc51>
and a bug report
<http://sourceforge.net/tracker/index.php?func=detail&aid=2010422&group_id=12997&atid=112997>

The latter provides a patch, too. Although this is not considered a long-term solution, the patch works. I am attaching a prettier version of this patch below. Dan, if you want I can commit a modified version of tcltk.info, but you will perhaps prefer to incorporate this patch into your PatchFile-MD5-protected patchfile.

--
Martin



--- tk8.4.16.old/generic/tk.h   2007-05-30 19:34:45.000000000 +0200
+++ tk8.4.16/generic/tk.h       2008-07-26 22:09:59.000000000 +0200
@@ -635,6 +635,9 @@
  *
  *---------------------------------------------------------------------------
  */
+#undef LASTEvent
+#define LASTEvent          (MappingNotify + 1)
+
 #define VirtualEvent       (LASTEvent)
 #define ActivateNotify     (LASTEvent + 1)
 #define DeactivateNotify    (LASTEvent + 2)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel

Reply via email to