From: "MSP-Greg (Greg L)" <noreply@ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Subject: [ruby-core:111130] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder
Date: Thu, 01 Dec 2022 15:00:49 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-100408.20221201150048.11129@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19143.20221123144306.11129@ruby-lang.org
Issue #19143 has been updated by MSP-Greg (Greg L).
@nobu
Yes, I agree, it might be very helpful when one has more than one platform installed and uses `--user-install`. As in `Gem.install_extension_in_lib`, also [Gem::Ext::ExtConfBuilder](https://github.com/ruby/ruby/blob/master/lib/rubygems/ext/ext_conf_builder.rb#L46). I overwrite my Windows Ruby master installs daily, so I always use `--user-install`.
Maybe issues with existing extension gems that load with `require_relative`, and also pre-compiled gems?
----------------------------------------
Bug #19143: Windows - bundled extension gems compile, but don't copy *.so files to lib folder
https://bugs.ruby-lang.org/issues/19143#change-100408
* Author: MSP-Greg (Greg L)
* Status: Closed
* Priority: Normal
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
Just finished updating ruby-loco's mswin build to use a system similar to the ucrt & mingw builds.
Confirmed something I noticed previously, and also occurs with the RubyInstaller2 head build.
On Windows, bundled extension gems (debug, rbs) compile their extension in the `ext` folder, but do not copy them to the `lib` folder. So, the *.so file is created, but not copied.
I think this was working correctly on Ruby 3.1?
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
prev parent reply other threads:[~2022-12-01 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 14:43 [ruby-core:110867] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder MSP-Greg (Greg L)
2022-11-24 2:27 ` [ruby-core:110869] " alanwu (Alan Wu)
2022-11-24 3:49 ` [ruby-core:110871] " MSP-Greg (Greg L)
2022-12-01 6:27 ` [ruby-core:111108] " nobu (Nobuyoshi Nakada)
2022-12-01 15:00 ` MSP-Greg (Greg L) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-100408.20221201150048.11129@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).