New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backslashes do not work in paths #16
Comments
This is a Ruby Issue, not RubyInstaller. Please identify that issues with the Development Kit (like missing a header or tool from GCC) and incorrect packaging of a Ruby version or anything related to the packages and the installer fits into RubyInstaller. We try not to deviate from Ruby vanilla distribution, and if this issue is present in Ruby itself, should be discussed there, not here. Thank you. |
But this is a DevKit bug. Using the MSVC6 version of Ruby, this problem does not occur:
|
Is not the devkit, is something from RbConfig and mkmf |
Rubyinstaller doesn't write the devkit software, we only repackage it for simplicity. These path seperators are standard for mingw/msys. http://www.mingw.org/wiki/IncludePathHOWTO If you consider it a bug, you could submit it to that project. |
So how do RbConfig and mkmf handle this properly with the MSVC6 version? The way I read it, those are passing the paths through, and the shell where gcc is being executed does not handle backslashes. |
I'll file the bug with mingw, but I am not hopefully about this approach. Strangely enough, executing gcc directly with backslashes works fine. It's when it is run through Make that it fails:
|
Make is msys make, not mingw one. MinGW one works fine, as you discovered, however, after lot of investigation and testing, none of the gems or even Ruby itself compiled with MinGW make. Because of that, the reason was to stick to msys-make. That do not solve your problem, but the reasoning behind that was a bigger than just a personal taste. |
Oh, pardon my ignorance. I thought mingw and msys make were one and the same. |
So, where do I file bugs about MSYS Make? |
As I suspected, MSYS Make considers this not a bug: |
So, the MSYS team declares very strongly that MSYS Make should not be used from the Windows command line, because it makes no attempt to be compatible with Windows command line arguments, escaping or paths. What were the issues with MinGW make exactly? |
Ruby didn't like it since we used *nix'ism configure & friends. We could try using MinGW make, it is a simple replacement in the building recipes. Do you want to try it? |
Yeah, let's give it a spin and see what the errors are. |
Using backslashes, as Windows paths do, in the arguments to an extconf.rb causes compilation failures. Substituting forward slashes works, but is quite time consuming, and not exactly native. Example:
However:
The text was updated successfully, but these errors were encountered: