Project

General

Profile

Actions

Bug #2278

closed

(windows) RbConfig sitearchdir differs from $: path

Added by spatulasnout (B Kelly) over 14 years ago. Updated almost 13 years ago.

Status:
Closed
Assignee:
-
Target version:
ruby -v:
ruby 1.9.2dev (2009-10-26) [i386-mswin32_71]
Backport:
[ruby-core:26324]

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

Actions

Also available in: Atom PDF

Like0
Like0Like0