Re: Cygwin compiler and linker options

- Original Message - From: "Warren Young" <[EMAIL PROTECTED]> Subject: Re: Cygwin compiler and linker options It's not impossible to have them both in the PATH, but I've come across enough strange behavior that I don't do that anymore. I posted abo

Re: Cygwin compiler and linker options

I thought I should point out that "gcc -v -help" says: % gcc -v --help 2>&1 | grep no-cygwin -mno-cygwin Use the Mingw32 interface cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation:

Re: Cygwin compiler and linker options

John Emmas skrev: Guys, Whilst I only signed up to this mailing list a couple of days ago, I can naturally understand your frustration if this topic ( -mno-cygwin) is dropping up over & over again and (apparently) being widely misunderstood. What I don't accept is that you have any right to cast

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 04:00:06PM -0400, Ralph Hempel wrote: > arren Young wrote: >>Ralph Hempel wrote: >>>what I think I hear you saying is that when -mno-cygwin is fully >>>deprecated I'll need to build a cross compiler for native Windows >>>executables >>Or, you could install MinGW. Cygwin and

Re: Cygwin compiler and linker options

Warren Young wrote: Ralph Hempel wrote: I know I can install MinGW, but keeping track of their releases and having to download custom versions of this and that to get all the parts to play nicely together is such a huge PITA. Building cross-compilers is easier?

Re: Cygwin compiler and linker options

Ralph Hempel wrote: I know I can install MinGW, but keeping track of their releases and having to download custom versions of this and that to get all the parts to play nicely together is such a huge PITA. Building cross-compilers is easier? -- Unsubscribe info: http://cygwin.com/ml/#uns

Re: Cygwin compiler and linker options

Warren Young wrote: Ralph Hempel wrote: what I think I hear you saying is that when -mno-cygwin is fully deprecated I'll need to build a cross compiler for native Windows executables Or, you could install MinGW. Cygwin and MinGW will coexist, side by side, without conflict, if you arrange

Re: Cygwin compiler and linker options

Ralph Hempel wrote: what I think I hear you saying is that when -mno-cygwin is fully deprecated I'll need to build a cross compiler for native Windows executables Or, you could install MinGW. Cygwin and MinGW will coexist, side by side, without conflict, if you arrange it so only one is in

Re: Cygwin compiler and linker options

Ralph Hempel wrote: Christopher Faylor wrote: . As one of "those people" I wonder if it will still be possible to generate executables that do not depend on cygwin DLLs using cygwin's gcc? No, we're changing the laws of the universe to make this a physical impossibility. At your first attempt

Re: Cygwin compiler and linker options

Christopher Faylor wrote: . As one of "those people" I wonder if it will still be possible to generate executables that do not depend on cygwin DLLs using cygwin's gcc? No, we're changing the laws of the universe to make this a physical impossibility. At your first attempt to generate a mingw

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 11:32:24AM -0400, Ralph Hempel wrote: > Christopher Faylor wrote: > >> Phil is 100% correct here. It's heartening to see someone so thoroughly >> getting it after having to so frequently deal with the misconceptions >> about -mno-cygwin. Confusion about -mwindows is new th

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 12:45:43PM -0400, Larry Hall (Cygwin) wrote: > On 08/22/2008, John Emmas wrote: >> Whilst I only signed up to this mailing list a couple of days ago, I can >> naturally understand your frustration if this topic ( -mno-cygwin) is >> dropping up over & over again and (apparent

Re: Cygwin compiler and linker options

On 08/22/2008, John Emmas wrote: Whilst I only signed up to this mailing list a couple of days ago, I can naturally understand your frustration if this topic ( -mno-cygwin) is dropping up over & over again and (apparently) being widely misunderstood. What I don't accept is that you have any right

Re: Cygwin compiler and linker options

sumption and I came to that conclusion because the writer's explanation was wholly inadequate (which isn't actually MY fault). In fact, that's precisely WHY I was asking if there was a more authoritative resource. John - Original Message - From: "Christopher Faylor" &

Re: Cygwin compiler and linker options

Christopher Faylor wrote: Phil is 100% correct here. It's heartening to see someone so thoroughly getting it after having to so frequently deal with the misconceptions about -mno-cygwin. Confusion about -mwindows is new though. I'm counting the days until -mno-cygwin disappears. It is a blig

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 03:52:35PM +0100, Phil Betts wrote: >John Emmas wrote on Friday, August 22, 2008 1:54 PM:: > >> Just doing some searches on the internet, there seems to be an awful >> lot of misinformation / misunderstanding about what the various >> Cygwin-gcc compiler and linker flags do.

Re: Cygwin compiler and linker options

Phil Betts wrote: It would be nice if the cygwin-specific options were documented in the gcc info file, but they don't appear to be. Don't expect -mno-cygwin to appear there soon either, because my understanding is that the -mno-cygwin option will be removed soon because of the surprising num

RE: Cygwin compiler and linker options

John Emmas wrote on Friday, August 22, 2008 1:54 PM:: > Just doing some searches on the internet, there seems to be an awful > lot of misinformation / misunderstanding about what the various > Cygwin-gcc compiler and linker flags do. > > For example, I saw one article that said that that flag -mn