From: "Berger, Daniel" Date: 2007-04-13T00:24:25+09:00 Subject: Re: Turning off verbose output for mkmf > -----Original Message----- > From: Nobuyoshi Nakada [mailto:nobu@ruby-lang.org] > Sent: Wednesday, April 11, 2007 6:06 PM > To: ruby-core@ruby-lang.org > Subject: Re: Turning off verbose output for mkmf > > > Hi, > > At Thu, 12 Apr 2007 04:41:36 +0900, > Daniel Berger wrote in [ruby-core:10909]: > > require 'mkmf' > def message(*s) end > > have_func('gethostname') > > > > If it's not possible then I'd like to suggest a way to disable this, > > perhaps via a global like $mkmf_verbose. My motivation for > this is that > > I'd like to use some of these functions in my test suite. > I'd rather not > > set $VERBOSE to nil, since that will disable warnings I > might otherwise > > want to see. > > Sounds like quite particular purpose. For some of my C extensions, not all platforms support all functions. For example, in the proc-wait3 package, not all platforms support the waitid() function. In my test suite, then, I have to do something like this: if RUBY_PLATFORM =~ /linux|sunos/i def test_waitid ... end end The problem with this approach is that it requires that I know, in advance, which platforms support the waitid() function and which don't. What I would rather do is this: if have_func('waitid') def test_waitid ... end end I can do this now but it gives me the verbose output, which I don't want. That's all. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.