[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>

I would like to request developers meeting around April 17 or 18 in this month.

14 messages 2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014 — Urabe Shyouhei <shyouhei@...> 2014/04/03

It's good if we have a meeting then.

[#61826] Re: Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...> 2014/04/03

Regarding openssl issues, I’ve discussed possible meeting time with Martin last month and he seemed positive.

[#61833] Re: Plan Developers Meeting Japan April 2014 — Martin Bo煬et <martin.bosslet@...> 2014/04/03

Hi,

[ruby-core:62002] [ruby-trunk - Bug #9737] [Open] Non-ASCII characters in the path to ruby executable break require paths

From: billk@...
Date: 2014-04-13 03:01:57 UTC
List: ruby-core #62002
Issue #9737 has been reported by B Kelly.

----------------------------------------
Bug #9737: Non-ASCII characters in the path to ruby executable break require paths
https://bugs.ruby-lang.org/issues/9737

* Author: B Kelly
* Status: Open
* Priority: Normal
* Assignee: cruby-windows
* Category: platform/windows
* Target version: 
* ruby -v: ruby 2.2.0dev (2014-04-12 trunk 45576) [i386-mswin32_100]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
Hi,

On Windows, if non-ASCII characters exist the path on which the ruby
interpreter is invoked, the character encoding is not handled properly
when the require paths in $: are created, making ruby unable to require
libraries in its standard lib paths.

In the first two examples, the working directory of the shell is not
a factor; what matters is the path by which the ruby interpreter is
invoked.

~~~
Here we invoke ruby using a path containing non-ASCII characters:

$ M:\dev\ruby-build\zz-k旦nnen2\bin\ruby.exe -v --disable-gems -e "p $:.first.encoding, $:.first; require 'uri'"
ruby 2.2.0dev (2014-04-12 trunk 45576) [i386-mswin32_100]
#<Encoding:ASCII-8BIT>
"M:/dev/ruby-build/zz-k\xF6nnen2/lib/ruby/site_ruby/2.2.0"
-e:1:in `require': cannot load such file -- uri (LoadError)
        from -e:1:in `<main>'

Here we invoke ruby in the same location, but instead using the
NTFS "short" name on the path so that it is ASCII only:

$ M:\dev\ruby-build\ZZ-KNN~2\bin\ruby.exe -v --disable-gems -e "p $:.first.encoding, $:.first; require 'uri'"
ruby 2.2.0dev (2014-04-12 trunk 45576) [i386-mswin32_100]
#<Encoding:IBM437>
"M:/dev/ruby-build/ZZ-KNN~2/lib/ruby/site_ruby/2.2.0"

In the second two examples, we change the working dir instead of
specifying the interpreter path directly.  The results are the same:

# working dir: M:\dev\ruby-build\zz-k旦nnen2\bin
$ .\ruby.exe -v --disable-gems -e "p $:.first.encoding, $:.first; require 'uri'"
ruby 2.2.0dev (2014-04-12 trunk 45576) [i386-mswin32_100]
#<Encoding:ASCII-8BIT>
"M:/dev/ruby-build/zz-k\xF6nnen2/lib/ruby/site_ruby/2.2.0"
-e:1:in `require': cannot load such file -- uri (LoadError)
        from -e:1:in `<main>'

# working dir: M:\dev\ruby-build\ZZ-KNN~2\bin
$ .\ruby.exe -v --disable-gems -e "p $:.first.encoding, $:.first; require 'uri'"
ruby 2.2.0dev (2014-04-12 trunk 45576) [i386-mswin32_100]
#<Encoding:IBM437>
"M:/dev/ruby-build/ZZ-KNN~2/lib/ruby/site_ruby/2.2.0"
~~~


I'm guessing this will be related to the GetModuleFileName() call in:

win32/stub.c:    lenexe = (size_t)GetModuleFileName(NULL, exename, sizeof exename);

which would presumably need to become the Unicode GetModuleFileNameW()
version instead?


Regards,

Bill





-- 
https://bugs.ruby-lang.org/

In This Thread

Prev Next