[#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

[ ruby-Bugs-9736 ] New kill_thread function in eval.c conflict with a BeOS system function

From: <noreply@...>
Date: 2007-04-01 14:20:59 UTC
List: ruby-core #10830
Bugs item #9736, was opened at 01/04/2007 16:20
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=9736&group_id=426

Category: Core
Group: 1.8.6
Status: Open
Resolution: None
Priority: 3
Submitted By: Olivier Coursiere (oco)
Assigned to: Nobody (None)
Summary: New kill_thread function in eval.c conflict with a BeOS system function

Initial Comment:
Here is the make output when compiling ruby 1.8.6 under BeOS :

gcc -g -O2  -DRUBY_EXPORT  -I. -I.  -c eval.c
/boot/home/Downloads/ruby-1.8.6/eval.c:11247: conflicting types for `kill_thread'
/boot/develop/headers/be/kernel/OS.h:266: previous declaration of `kill_thread'
make: *** [eval.o] Error 1

As kill_thread is only used in eval.c, i rename "kill_thread" to "kill_thread2" : now it compiles.

I hope someone will come with a better fix that could be included in the official source tree.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=9736&group_id=426

In This Thread

Prev Next