Hidetoshi NAGAI wrote:

> Hi,
> 
> From: Tim Hunter <cyclists / nc.rr.com>
> Subject: Re: segfault in tk/variable.rb
> Date: Thu, 13 Jan 2005 11:46:21 +0900
> Message-ID: <GhlFd.10248$hQ6.2371593 / twister.southeast.rr.com>
>> > Could you tell me the value of TclTkLib::COMPILE_INFO ?
>> 
>> "tcltklib 2004-12-23 :: Ruby1.8.2 (2004-12-25) without pthread :: Tcl8.4.
>> (without stub)/Tk8.4.5(without stub) with tcl_threads"
> 
> Possibly, the trouble depends on inconsistency of pthread support.
> Didn't you see the following messgase when compiling?
> 
>
*****************************************************************************
> **
> ** PTHREAD SUPPORT MODE ERRROR:
> **
> **   Ruby is not compiled with --enable-pthread, but your Tcl/Tk
> **   libararies seems to be compiled with "pthread support". This
> **   combination possibly cause "Hang-up" or "Segmentation Fault"
> **   frequently when Ruby/Tk is working. We NEVER recommend you to
> **   create the library under such combination of pthread support.
> **
> **   Please recompile Ruby with "--enable-pthread" configure option
> **   or recompile Tcl/Tk with "--disable-threads" configure option.
> **
>
*****************************************************************************
> 

Thank you for helping me.

Hmmm...Why is the default for Ruby different from Tcl/Tk's default when I'm
building them at the same time? I did not use --enable-pthread when
building Ruby, so how did Tcl/Tk get --enable-threads?

To be sure, I did a `make clean' and re-ran ./configure without the
--enable-pthread option. When I ran `make' I did not get this message. 

Then I ran ./configure with --enable-pthread. When I ran `make' I _did_ get
the message.

Which is right?