[#10853] Why limit class def to a constant or colon node? — Charles Oliver Nutter <charles.nutter@...>

Is there a historical reason why I can't do something like these:

12 messages 2007/04/03

[#10933] Cannot build with extra library path if previous version already installed — <noreply@...>

Bugs item #10140, was opened at 2007-04-16 17:32

10 messages 2007/04/16
[#10934] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — nobu@... 2007/04/16

Hi,

[#10960] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — "Michal Suchanek" <hramrach@...> 2007/04/18

On 4/16/07, nobu@ruby-lang.org <nobu@ruby-lang.org> wrote:

[#10967] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — Nobuyoshi Nakada <nobu@...> 2007/04/19

Hi,

[#10970] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — "Michal Suchanek" <hramrach@...> 2007/04/19

On 4/19/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:> Hi,>> At Wed, 18 Apr 2007 20:21:44 +0900,> Michal Suchanek wrote in [ruby-core:10960]:> > Yes. And this should also apply to extensions. The mkmf tests are now> > fine but the extension is linked with -L/sw/lib before -L../..>> Indeed.>>> Index: configure.in> ===================================================================> --- configure.in (revision 12191)> +++ configure.in (working copy)> @@ -1385,5 +1385,4 @@ if test "$enable_rpath" = yes; then> fi>> -LDFLAGS="-L. $LDFLAGS"> AC_SUBST(ARCHFILE)>This would break the previous fix so I did not even try to apply this ^

[#11003] miniruby loads extensions from already installed ruby — <noreply@...>

Bugs item #10303, was opened at 2007-04-23 10:44

10 messages 2007/04/23

[#11025] gsub with backslash characters in replacement string — "Adam Bozanich" <adam.boz@...>

Hello, spotted this one the other day:

10 messages 2007/04/26

Re: ruby 1.9 crash on cygwin

From: "Anton Ivanov" <Anton.Ivanov@...>
Date: 2007-04-20 18:02:26 UTC
List: ruby-core #10991
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.




In This Thread