title: Windows rails installation failing, currently on websocket mask compilation -- `make: *** [Makefile:246: websocket_mask.o]`
body: <p>I have tried a bunch of different ways to get Rails to install and haven't been able to find one that works. I have refrained from going the WSL way because my OS drive is nearly at capacity, but I plan to try that if I can't find a solution here.</p>
  <p>With my current setup, I am failing on the compilation of <code>websocket_mask.c</code>.</p>
  <p>Current process I took was one directed by John Elder to use <code>RailsInstaller</code> to get a bunch of the dependencies, then upgrade Ruby and Devkit from <a href="https://rubyinstaller.org/" rel="nofollow noreferrer">https://rubyinstaller.org/</a>, then <code>gem install rails</code> to upgrade to the latest version of Rails.</p>
  <p>When I ran <code>gem install rails</code>, I encountered an error I'd seen before in <code>make: gcc: No such file or directory </code>.</p>
  <pre><code>current directory: C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/websocket-driver-0.7.5/ext/websocket-driver
  make DESTDIR\=
  generating websocket_mask-x64-mingw-ucrt.def
  compiling websocket_mask.c
  make: gcc: No such file or directory
  make: *** [Makefile:246: websocket_mask.o] Error 127
  
  make failed, exit code 2
  </code></pre>
  <p>I followed <a href="https://dev.to/gamegods3/how-to-install-gcc-in-windows-10-the-easier-way-422j" rel="nofollow noreferrer">this</a> guide on installing <code>gcc</code> on windows. I ran <code>gem install rails</code> again and now have</p>
  <pre><code>current directory: C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/websocket-driver-0.7.5/ext/websocket-driver
  make DESTDIR\=
  generating websocket_mask-x64-mingw-ucrt.def
  compiling websocket_mask.c
  websocket_mask.c:1:0: sorry, unimplemented: 64-bit mode not compiled in
   #include &lt;ruby.h&gt;
  
  make: *** [Makefile:246: websocket_mask.o] Error 1
  
  make failed, exit code 2
  </code></pre>
  <p>I could have sworn in a past attempt that I got past this point and was able to install Rails and proceed to errors in <code>rails new</code>, but I think it's possible this error had appeared above some other success messages and I proceeded. <code>rails -v</code> produces the most current version even with an error in installation.</p>
  <p>I think it's all tied to this error in installing rails, but I remember in the past that <code>rails new</code> threw errors related to <code>msgpack</code> at one point and <code>sprockets-rails</code> at another.</p>