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: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,SPF_PASS,T_DKIM_INVALID, T_RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id B257B20D0A for ; Thu, 1 Jun 2017 19:08:39 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 39EBD120764; Fri, 2 Jun 2017 04:08:37 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id E36EC120731 for ; Fri, 2 Jun 2017 04:08:34 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=4d+Gb0z1KjGzbkOr4vPaESR3Nwg=; b=ooQGhgfCCz/TR6ILdK IOZfgn/Rg6vn8t7pechYp/Fgo4+JOkYk8n1RYJIKc9GRc17HjcTaMBKAL9iV4umQ CE/PuAz8exMoLWTOs8nsAVRV3HTg6RRwJePgayVERFKfqo00gN8CV5uHWYiB60QV 4TGTq8qUK0/+VNmaljdTMqfic= Received: by filter0896p1mdw1.sendgrid.net with SMTP id filter0896p1mdw1-12700-5930662C-2D 2017-06-01 19:08:28.481762954 +0000 UTC Received: from herokuapp.com (ec2-54-160-142-233.compute-1.amazonaws.com [54.160.142.233]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id eft3WDnSS_65rFS0yZ4XVQ Thu, 01 Jun 2017 19:08:28.401 +0000 (UTC) Date: Thu, 01 Jun 2017 19:08:28 +0000 From: eregontp@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 56543 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 13570 X-Redmine-Issue-Author: Eregon X-Redmine-Issue-Assignee: X-Redmine-Sender: Eregon X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS6hO2rWMgvWtyf2zjv/gYCY45p12Lv7Mrvj5f szL/KAFogIk3VZ9HPIxfrSvCDqJFjQ29wMCm1bQ7PInXNbdDiI0l6qR0SoUKCxpAfCPdG8/QWhdBqM Rz/uJygy6CCksBhERXkZBefrieXfzP8R97hhe8jdOBrNEKGAJtT9VS3AxA== X-ML-Name: ruby-core X-Mail-Count: 81513 Subject: [ruby-core:81513] [Ruby trunk Feature#13570] Using mkmf for ruby/spec C API specs X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #13570 has been updated by Eregon (Benoit Daloze). MSP-Greg (Greg L) wrote: > I checked on MinGW, and there is not an issue with `File.rename` with `src` and `dest` being on different drives. Where I got that from, I don't know... It's the semantics of the rename(2) syscall on Linux, which throws EXDEV if oldpath and newpath are not on the same mounted filesystem. And indeed, on Linux: > File.write "foo","abc" > File.rename "foo", "/tmp/bla" Errno::EXDEV: Invalid cross-device link @ rb_file_s_rename - (foo, /tmp/bla) So we would need some special handling to move files across filesystems on non-Windows, or use FileUtils.mv > > MSpec's #cp should use "rb"/"wb" modes obviously. > Would it work with that? > > Yes and haven't tried. Seems odd to copy a file when a rename will do... Indeed, moving sounds nicer in principle. The reason I like the copy is to help debugging, the .so is still in tmpdir used for compilation along other files. But it's a small thing, looking for the moved file is fine as well. ---------------------------------------- Feature #13570: Using mkmf for ruby/spec C API specs https://bugs.ruby-lang.org/issues/13570#change-65220 * Author: Eregon (Benoit Daloze) * Status: Assigned * Priority: Normal * Assignee: cruby-windows * Target version: ---------------------------------------- Hello all, I am thinking to use mkmf to compile the C API specs. https://github.com/ruby/ruby/blob/trunk/spec/rubyspec/optional/capi/spec_helper.rb is getting pretty complex and hard to maintain. I have a few questions: * Does mkmf works well on Windows? * What is a good way to compile a single .c file with mkmf to a given library file in another directory? I tried this but I am not sure it's correct: ~~~ ruby def compile_extension(name) objdir = object_path ext = "#{name}_spec" lib = "#{objdir}/#{ext}.#{RbConfig::CONFIG['DLEXT']}" require 'mkmf' # TODO: probably best to use a subprocess to avoid polluting the namespace Dir.chdir(objdir) do $srcs = ["#{extension_path}/#{ext}.c"] $objs = ["#{extension_path}/#{ext}.o"] # should probably be in objdir but that does not seem to work create_makefile(ext) system "make" end lib end ~~~ Alternatively, we can copy the needed files to a temporary directory, build there and copy the shared library back. It's a bit more work but not a big deal either. ---Files-------------------------------- spec_helper.rb (2.22 KB) -- https://bugs.ruby-lang.org/