* [ruby-core:110867] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder
@ 2022-11-23 14:43 MSP-Greg (Greg L)
2022-11-24 2:27 ` [ruby-core:110869] " alanwu (Alan Wu)
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: MSP-Greg (Greg L) @ 2022-11-23 14:43 UTC (permalink / raw)
To: ruby-core
Issue #19143 has been reported by MSP-Greg (Greg L).
----------------------------------------
Bug #19143: Windows - bundled extension gems compile, but don't copy *.so files to lib folder
https://bugs.ruby-lang.org/issues/19143
* Author: MSP-Greg (Greg L)
* Status: Open
* 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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:110869] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder
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 ` alanwu (Alan Wu)
2022-11-24 3:49 ` [ruby-core:110871] " MSP-Greg (Greg L)
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: alanwu (Alan Wu) @ 2022-11-24 2:27 UTC (permalink / raw)
To: ruby-core
Issue #19143 has been updated by alanwu (Alan Wu).
Does that mean the native extensions of those gems don't work when one tries to load after installation?
----------------------------------------
Bug #19143: Windows - bundled extension gems compile, but don't copy *.so files to lib folder
https://bugs.ruby-lang.org/issues/19143#change-100228
* Author: MSP-Greg (Greg L)
* Status: Open
* 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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:110871] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder
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 ` MSP-Greg (Greg L)
2022-12-01 6:27 ` [ruby-core:111108] " nobu (Nobuyoshi Nakada)
2022-12-01 15:00 ` [ruby-core:111130] " MSP-Greg (Greg L)
3 siblings, 0 replies; 5+ messages in thread
From: MSP-Greg (Greg L) @ 2022-11-24 3:49 UTC (permalink / raw)
To: ruby-core
Issue #19143 has been updated by MSP-Greg (Greg L).
@alanwu
Thanks. A bit of 'multi-tasking brain freeze' going on this morning.
Or, yes they do work **without** a copy in the lib folder.
Please close...
----------------------------------------
Bug #19143: Windows - bundled extension gems compile, but don't copy *.so files to lib folder
https://bugs.ruby-lang.org/issues/19143#change-100229
* Author: MSP-Greg (Greg L)
* Status: Open
* 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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:111108] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder
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 ` nobu (Nobuyoshi Nakada)
2022-12-01 15:00 ` [ruby-core:111130] " MSP-Greg (Greg L)
3 siblings, 0 replies; 5+ messages in thread
From: nobu (Nobuyoshi Nakada) @ 2022-12-01 6:27 UTC (permalink / raw)
To: ruby-core
Issue #19143 has been updated by nobu (Nobuyoshi Nakada).
It is intended.
`*.so` files are architecture-dependent, which are "tainted" in other words, while `lib` directories are architecture-independent, "untainted".
"Tainted" files should not infect "untainted" directories.
----------------------------------------
Bug #19143: Windows - bundled extension gems compile, but don't copy *.so files to lib folder
https://bugs.ruby-lang.org/issues/19143#change-100378
* 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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:111130] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder
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)
` (2 preceding siblings ...)
2022-12-01 6:27 ` [ruby-core:111108] " nobu (Nobuyoshi Nakada)
@ 2022-12-01 15:00 ` MSP-Greg (Greg L)
3 siblings, 0 replies; 5+ messages in thread
From: MSP-Greg (Greg L) @ 2022-12-01 15:00 UTC (permalink / raw)
To: ruby-core
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/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-12-01 15:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` [ruby-core:111130] " MSP-Greg (Greg L)
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).