[ruby-core:110867] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder

[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)]

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/

[ruby-core:110869] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder

[alanwu (Alan Wu)]

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/

[ruby-core:110871] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder

[MSP-Greg (Greg L)]

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/

[ruby-core:111108] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder

[nobu (Nobuyoshi Nakada)]

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/

[ruby-core:111130] [Ruby master Bug#19143] Windows - bundled extension gems compile, but don't copy *.so files to lib folder

[MSP-Greg (Greg L)]

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/