Apparently the core fellas use cygwin frequently to build their mingw builds--anyone know of any instructions out there of how to do that? As a side note, downloading oneclick master branch and running rake [for me] still yields: patching file `io.c'' patching file `lib/webrick/httpservlet/filehandler.rb'' Hunk #1 FAILED at 163. Hunk #2 succeeded at 216 with fuzz 2 (offset 17 lines). Hunk #3 FAILED at 290. Hunk #4 FAILED at 344. 3 out of 4 hunks FAILED -- saving rejects to lib/webrick/httpservlet/filehandler.rb.rej patching file `sprintf.c'' patching file `string.c'' rake aborted! Command failed with status (1): ["C:/dev/downloads/rubyinstaller/sandbox/ms...] Thanks! -=r
On Wed, Feb 25, 2009 at 6:38 PM, Roger Pack <rogerdpack at gmail.com> wrote:> Apparently the core fellas use cygwin frequently to build their mingw > builds--anyone know of any instructions out there of how to do that? >-mno-cygwin to the CPFLAGS I believe.> As a side note, downloading oneclick master branch and running rake > [for me] still yields: >Patches are no longer needed with p287. pull requests from your fork are always welcome ;-)> > Thanks! > -=rCheers! :-D -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry
> -mno-cygwin > > to the CPFLAGS I believe.gotcha so add that to CPPFLAGS then compile it using normal ./configure etc. from within cygwin bash.> Patches are no longer needed with p287. pull requests from your fork > are always welcome ;-)All righty my fork has some changes if you''d like them. I also think I figured out that my msys stuff crashing [ex: C:\dev\rubyinstaller>git pull 0 [main] sh.exe" 4632 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump ] was caused either by virus scanners or by TSVNCache or what not. At last I have an almost stable build environment now [1] :) Thanks. -=r [1] http://betterlogic.com/roger/?p=1017 shows a few of the obscure errors that used to occur sporadically.