Re: RFD: cygwin + *native* MinGW compiler

Charles Wilson wrote: > Pursuant to a discussion on the libtool list, I'm trying to get a feel > for how many cygwin users rely on the cygwin environment to drive the > *native* MinGW gcc compiler. That is, incantations like this: [snip] > I hope this is considered on-topic here, because I'm in

Re: multiple cygwin1.dll message

Christopher Faylor wrote: > On Sat, May 26, 2007 at 02:14:47AM -0400, John wrote: >> John wrote: >>> 602k 2005/06/26 C:\WINDOWS\system32\cygwin1.dll - os=4.0 img=1.0 sys=4.0 >>> "cygwin1.dll" v0.0 ts=2005/5/25 19:38 >> I just noticed this line in the output. However, a Windows

Re: Burning ISO's to CD with Cygwin

Grok Mogger wrote: > Brian Dessent wrote: >> Grok Mogger wrote: >>> I recently wanted to burn an ISO to a CD on my Windows machine. >>> So where did I turn first? Cygwin! But much to my dismay, I >>> don't seem to have cdrecord or wodim. I couldn't seem to find >>> the packages anywh

Re: Eliminating -mno-cygwin from gcc.

Frank Fesevur wrote: > At 5-2-2007 17:58, Charles Wilson wrote: >> Sounds to me like we need to consider extending the setup.ini format >> (and, by extension, the setup.hint format) to include an optional field: >> popup: This package is a significant change from the previous release. >> Please c

Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1

Christopher Faylor wrote: > We're already cluttering the root one less than linux since modern linuxes > use /dev, /proc, and /sys. > Hmm. /sys/drive/c has a nice feel to it, although this is YA a case where > the existence of a filesystem under this directory is not linux-like. What about /mn