https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112014-01-02T08:55:08ZRuby Issue Tracking SystemRuby master - Bug #9339: Can't Compile Ruby 2.1 without baseruby (Win7, MSYS/MinGW)https://bugs.ruby-lang.org/issues/9339?journal_id=440122014-01-02T08:55:08Zluislavena (Luis Lavena)luislavena@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Hello,</p>
<p>Even that you're using MSYS bash and make to trigger the compilation process, please use Windows-style paths for the installation directory.</p>
<p>configure --prefix=C:/some/folder</p>
<p>Depending on the way the source code was extracted, timestamps might trigger the need to rebuild the files that a base Ruby is required for compilation.</p>
<p>I recommend you install an existing binary of Ruby to be used when building.</p>
<p>Last but not least, RubyInstaller already packages lot of these steps to automate and build Ruby 2.0 and 2.1, please take a look to the recipes:</p>
<p><a href="https://github.com/oneclick/rubyinstaller/" class="external">https://github.com/oneclick/rubyinstaller/</a></p> Ruby master - Bug #9339: Can't Compile Ruby 2.1 without baseruby (Win7, MSYS/MinGW)https://bugs.ruby-lang.org/issues/9339?journal_id=440132014-01-02T11:18:20Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><p>If you want to extract from a tarball, you need 'p' option.</p>
<p>I recommend not to include drive letter and even use of environment dependent path.<br>
As windows binaries are always relocatable, I configure with --prefix=/. and use DESTDIR at the installation, instead.</p> Ruby master - Bug #9339: Can't Compile Ruby 2.1 without baseruby (Win7, MSYS/MinGW)https://bugs.ruby-lang.org/issues/9339?journal_id=797662019-07-20T03:51:53Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>Backport</strong> deleted (<del><i>1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN</i></del>)</li></ul>