[#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-Patches-9762 ] Hefty patch for mkmf.rb

From: Daniel Berger <djberg96@...>
Date: 2007-04-05 01:31:21 UTC
List: ruby-core #10870
Nobuyoshi Nakada wrote:
> Hi,
> 
> At Tue, 3 Apr 2007 23:14:17 +0900,
> Daniel Berger wrote in [ruby-core:10850]:
>>>> I wasn't completely sure if pkg_config was meant for public
>>>> use or not. If so, I leave it for someone else to document
>>>> more thoroughly.
>>> Yes, and macro_defined?, checking_for, scalar_ptr_type?,
>>> scalar_type? and Logging are too.
>> Are you sure about all of these?
> 
> It depends on how you define "internal use" here.
> These methods are for particular use, in extconf.rb.

By "internal" I just mean private, i.e. we aren't meant to use them 
directly in our extconf.rb files.

>> The macro_defined? method does not look like it's meant to be used 
>> directly. It's wrapped by the have_macro method which wraps the 
>> macro_defined? method and emits a "checking for" message to boot.
> 
> Formerly, there was macro_defined? only, but have_macro didn't
> exist.

Then I would say we only want have_macro published.

>> The checking_for method does not appear to have any use beyond emitting 
>> a message for the various have_x and find_x methods. I cannot envision 
>> using it directly. Do you?
> 
> Any library specific tests can use it to emit and log a
> message.  In other hand, if an extension author wants not to
> emit it, it isn't enforced.

Seems an odd thing to do, but ok.

>> I wasn't sure about scalar_type?, scalar_ptr_type? or what_type?. The 
>> what_type? method is the only one of the three with a 'checking_for' 
>> hook, which leads me to believe it's the only one of the three we should 
>> publish. However, I'm somewhat confused as to its usage. It doesn't seem 
>> to modify the generated Makefile in any case. Any insight you can offer 
>> here would be appreciated.
> 
> They were made for ext/etc, to check compatible types of pid_t
> and gid_t, but those checks are moved into configure.in now.

Should they be removed then?

>> As for the Logging module, I've never used directly, nor have I ever 
>> seen anyone who did. But, I'll leave it to you to document as you see 
>> fit. :)
> 
> When the author wants to log some extra information.

Alright.

Thanks,

Dan


In This Thread

Prev Next