From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS11260 24.222.16.0/20 X-Spam-Status: No, score=-4.3 required=3.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from webmail.dymaxion.ca (webmail.dymaxion.ca [24.222.19.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id CD58D203E1 for ; Tue, 26 Jul 2016 09:35:30 +0000 (UTC) Received: from DYMAXMAIL.dymaxion.lan (24.222.19.53) by dymaxmail.dymaxion.lan (24.222.19.53) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 26 Jul 2016 06:34:41 -0300 Received: from [IPv6:::1] (24.222.19.4) by DYMAXMAIL.dymaxion.lan (24.222.19.55) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Tue, 26 Jul 2016 06:34:41 -0300 Subject: Re: gem fails to build on Win 7 32 bit, DevKit 3.7.2 (rubyinstaller.org) To: Eric Wong References: <230a2e9e-a0d3-2473-2cba-567eadc32c88@dymaxion.ca> <20160725210439.GA29810@starla> CC: From: Ben Armstrong Message-ID: Date: Tue, 26 Jul 2016 06:35:27 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160725210439.GA29810@starla> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit List-Id: On 25/07/16 06:04 PM, Eric Wong wrote: > Is the pure-Ruby version acceptable for you? > > I wonder if extconf.rb should just bail out with > > if RUBY_PLATFORM =~ /win32/i > raise "C ext not supported on RUBY_PLATFORM=#{RUBY_PLATFORM}" > end That might work for me, except there are several Windows platform strings, and mine is i386-mingw32. In my test, I simply did an unconditional raise and the gem built fine. See: http://stackoverflow.com/questions/170956/how-can-i-find-which-operating-system-my-ruby-program-is-running-on However, after my successful build of the patched gem, when I re-enabled clogger in my rails 3 app in config/application.rb like this, it resulted in an empty log/access.log: config.middleware.use 'Clogger', :format => Clogger::Format::Combined, :logger => File.open("log/access.log", "ab") Odd, as this worked fine for me once upon a time when the application ran on Ruby 1.8.7. (It was only when we made the switch to Ruby 1.8.7 -> 2.2.4 that clogger broke and we temporarily disabled this feature.) > if this can't be fixed... Do you want to go that way anyway? I certainly could provide the Makefile and mkmf.log, except ... > On a side note: I hope to drop the C extension if the pure > Ruby version can offer acceptable performance nowadays. I'd be > much happier if there's zero chance of somebody downloading an > unauditable pre-compiled binary. Sounds reasonable. If this is the way you're heading, I wonder if it's worth the effort to debug the C. Thanks, Ben