Bug #2278
closed(windows) RbConfig sitearchdir differs from $: path
Description
=begin
Hi,
It seems in ruby 1.9.2dev, on windows, 'sitearch' may differ between
RbConfig vs. ruby_initial_load_paths[].
In RbConfig, 'sitearch' is i386-msvcr71:
arch => i386-mswin32_71
sitearch => i386-msvcr71
ruby_version => 1.9.1
rubylibdir => M:/dev/ruby-build/v1_9_2/lib/ruby/1.9.1
archdir => M:/dev/ruby-build/v1_9_2/lib/ruby/1.9.1/i386-mswin32_71
sitelibdir => M:/dev/ruby-build/v1_9_2/lib/ruby/site_ruby/1.9.1
sitearchdir => M:/dev/ruby-build/v1_9_2/lib/ruby/site_ruby/1.9.1/i386-msvcr71
But in $: it is i386-mswin32_71:
M:/dev/ruby-build/v1_9_2/lib/ruby/site_ruby/1.9.1
M:/dev/ruby-build/v1_9_2/lib/ruby/site_ruby/1.9.1/i386-mswin32_71
M:/dev/ruby-build/v1_9_2/lib/ruby/site_ruby
M:/dev/ruby-build/v1_9_2/lib/ruby/1.9.1
M:/dev/ruby-build/v1_9_2/lib/ruby/1.9.1/i386-mswin32_71
This is causing native extensions using extconf.rb to install into i386-msvcr71,
but ruby can't find them since it's looking in i386-mswin32_71.
(I am using Visual Studio .NET 2003 to build ruby.)
Regards,
Bill
=end
Updated by nobu (Nobuyoshi Nakada) about 15 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
=begin
This issue was solved with changeset r25492.
B, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
=end
Updated by spatulasnout (B Kelly) about 15 years ago
=begin
From: "Nobuyoshi Nakada" redmine@ruby-lang.org
Issue #2278 has been updated by Nobuyoshi Nakada.
Status changed from Open to Closed
% Done changed from 0 to 100This issue was solved with changeset r25492.
B, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
Thank you !
You are awesome! :D
=end