From: Anton Ivanov <Anton.Ivanov@...>
Date: 2007-04-21T03:02:26+09:00
Subject: Re: ruby 1.9 crash on cygwin

Thanks for the suggestion.  Unfortunately I wasn't able to figure out
how to not link tk (statically or otherwise).  I tried to run configure
like this:

./configure CFLAGS=-g --program-suffix=19 --without-static-linked-ext

But tcl/tk is still included in the build:
[...]
EXTLIBS=-ladvapi32 -lkernel32 -lreadline -lncurses -ltermcap
-lgdbm_compat -lgdbm -ldl -liconv -lutil -luser32 -luuid -loleaut32
-lole32 -lz -ltk -ltcl
[...]

The interpreter still crashes, and the backtrace still manifests Tk init
code.

So how can I suppress it?

Thanks

Anton

-----Original Message-----
From: Nobuyoshi Nakada [mailto:nobu@ruby-lang.org] 
At Fri, 20 Apr 2007 06:43:05 +0900,
Anton Ivanov wrote in [ruby-core:10981]:
> I compiled ruby 1.9 from trunk on cygwin.  Initially, the only option
I
> gave to configure was -program-suffix=19.  I got a crash when I ran
the
> interpreter and fed it one line of code ('puts "yo"').  I since tried
to
> recompile without ext/tk and with -disable-pthreads, but I still get
> crashes in the same place.  Here's the backtrace:

Apparently, you linked ext/tk statically.  VM support of ext/tk
is still incomplete and will need more time.