Re: gcc -mno-cygwin

On 2023-01-08 01:06, Brian Inglis wrote: On Sat, 7 Jan 2023 14:50:02 -0500, Lee wrote: The "-mno-cygwin" gcc option went away years ago.  Correct? It still shows up in the output of 'man gcc': $ man gcc | grep mno-cygwin    x86 Windows Options -mconsole  -mcygwin  -mno-cygwin  -mdll -m

Re: gcc -mno-cygwin

On Sat, 7 Jan 2023 14:50:02 -0500, Lee wrote: The "-mno-cygwin" gcc option went away years ago. Correct? It still shows up in the output of 'man gcc': $ man gcc | grep mno-cygwin x86 Windows Options -mconsole -mcygwin -mno-cygwin -mdll -mnop-fun-dllimport -mthread -municode -mw

Re: gcc -mno-cygwin still wants to link with cygwin libs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 8 Jun 2006, Brian Dessent wrote: The search order is documented: . I think the only thing it says about search order that is relevant here is that

Re: gcc -mno-cygwin still wants to link with cygwin libs

Peter Amstutz wrote: > However, the real problem is that when ld searches the linker path, it > seems to do so in several phases, and is the way this search works is > troublesome. I should note that it does find files that end it ".lib", > but only AFTER it has searched the ENTIRE path for files

Re: gcc -mno-cygwin (incorrectly) looks for libraries in /usr/lib

On Tue, Oct 11, 2005 at 02:02:27PM +0200, Burgers A.R. wrote: >When executing a configure script with gcc -mno-cygwin, the script may >incorrectly determine a mingw library is present. Yep. It's a long-standing bug. binutils has advanced to the point where ld can now be told to ignore /usr/lib s

Re: gcc -mno-cygwin foo.c & gcc foo.c generate different behavior

"Alex Vinokur" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Windows 2000 > CYGWIN_NT-5.0 1.5.10-3 (0.116/4/2) > gcc (GCC) 3.3.1 (cygming special) > > > > > -- foo.c -- > > #include > > struct foo > { > char* bar_; > }; > > int

Re: gcc -mno-cygwin foo.c & gcc foo.c generate different behavior

At 12:06 PM 6/22/2004, you wrote: > >Windows 2000 >CYGWIN_NT-5.0 1.5.10-3 (0.116/4/2) >gcc (GCC) 3.3.1 (cygming special) > > > > >-- foo.c -- > >#include > >struct foo >{ > char* bar_; >}; > >int main() >{ >char* ch = "ABC"; >struct foo* f; > > f->

RE: gcc -mno-cygwin finds the wrong include files

Greetings, Has anyone else been able to confirm this as a bug? if so, any attempts to fix it? Regards, Bryan -Original Message- From: Dave Korn [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 13, 2004 1:08 PM To: [EMAIL PROTECTED] Subject: RE: gcc -mno-cygwin finds the wrong include

Re: gcc -mno-cygwin finds the wrong include files

... Hi self! I've been having a play around and I believe this problem is connected to #include_next not respecting the -mno-cygwin. My knowledge of gcc is however nowhere near enough for me to be sure. I just wanted to say this to perhaps save someone else some small amount of time. Chris -

RE: gcc -mno-cygwin finds the wrong include files

> -Original Message- > From: cygwin-owner On Behalf Of Chris Jefferson > Sent: 15 April 2004 19:32 > $ echo "#include " | gcc -mno-cygwin -E - > # 1 "/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/include/stddef.h" 1 3 4 > So I'm picking up i686-pc-cygwin > > But... > > $ gcc -mno-cygwin -print

Re: gcc -mno-cygwin finds the wrong include files

Volker Quetschke wrote: Hi, could someone please confirm that this is a bug, and not a problem that exists only on this computer. Thanks Volker Volker Quetschke wrote: Hi, when I use the following command gcc finds the wrong include file. $ echo "#include " | gcc -mno-cygwin -E - # 1 ""

Re: gcc -mno-cygwin finds the wrong include files

Hi Volker, Dave, I see the same problem as Volker. Interesting issue that Eric doesn't see it. > snip > ignoring nonexistent directory "/usr/local/include/mingw" > ignoring duplicate directory "/usr/include/mingw" > ignoring duplicate directory > "/usr/i686-pc-mingw32/lib/../..

RE: gcc -mno-cygwin finds the wrong include files

> -Original Message- > From: cygwin-owner On Behalf Of Eric Hanchrow > Sent: 13 April 2004 18:43 > > Hi, > > when I use the following command gcc finds the wrong include > > file. > > $ echo "#include " | gcc -mno-cygwin -E - > Hi, could someone please confirm that thi

Re: gcc -mno-cygwin finds the wrong include files

Hi, could someone please confirm that this is a bug, and not a problem that exists only on this computer. I just tried it, and got reasonable-looking output: # 1 "" # 1 "" # 1 "" # 1 "" # 1 "/lib/gcc-lib/i686-pc-mingw32/3.3.1/include/stddef.h" 1 3 4 # 158 "/lib/gcc-lib/i686-pc-mingw32/3.

Re: gcc -mno-cygwin finds the wrong include files

Hi, could someone please confirm that this is a bug, and not a problem that exists only on this computer. Thanks Volker Volker Quetschke wrote: Hi, when I use the following command gcc finds the wrong include file. $ echo "#include " | gcc -mno-cygwin -E - # 1 "" # 1 "" # 1 "" # 1 "" # 1

Re: gcc -mno-cygwin fails

On Thu, Sep 25, 2003 at 05:09:40PM +0200, Gerrit P. Haase wrote: >Gregory schrieb: > > >> Following up with recent problems noted about g77 -mno-cygwin, >> the same problem occurs for gcc. > >> I am using the newest packages: gcc-3.3.1-2, gcc-mingw-20030911-2 > >> $ gcc foo.c >> $ gcc -mno-cygwin

Re: gcc -mno-cygwin fails

Igor Pechtchanski wrote: I have gcc-mingw-20030911-2, which "setup" lists as the most recent. >> $ pwd /usr/lib/gcc-lib/i686-pc-mingw32 $ ls 3.2 $ Doesn't look like you have gcc-mingw-20030911-2 installed. Hmmm, interesting comment. So I use "setup" to "reinstall" gcc-mingw-20030911-2, now I get

Re: gcc -mno-cygwin fails

Greg, On Thu, 25 Sep 2003, Greg Sharp wrote: > Igor Pechtchanski wrote: > > On Thu, 25 Sep 2003, Gregory C. Sharp wrote: > >>Following up with recent problems noted about g77 -mno-cygwin, > >>the same problem occurs for gcc. > >> > >>I am using the newest packages: gcc-3.3.1-2, gcc-mingw-2003091

Re: gcc -mno-cygwin fails

Igor Pechtchanski wrote: On Thu, 25 Sep 2003, Gregory C. Sharp wrote: Following up with recent problems noted about g77 -mno-cygwin, the same problem occurs for gcc. I am using the newest packages: gcc-3.3.1-2, gcc-mingw-20030911-2 $ gcc foo.c $ gcc -mno-cygwin foo.c gcc: installation problem, ca

Re: gcc -mno-cygwin fails

On Thu, 25 Sep 2003, Gregory C. Sharp wrote: > Following up with recent problems noted about g77 -mno-cygwin, > the same problem occurs for gcc. > > I am using the newest packages: gcc-3.3.1-2, gcc-mingw-20030911-2 > > $ gcc foo.c > $ gcc -mno-cygwin foo.c > gcc: installation problem, cannot exec

Re: gcc -mno-cygwin fails

Gregory schrieb: > Following up with recent problems noted about g77 -mno-cygwin, > the same problem occurs for gcc. > I am using the newest packages: gcc-3.3.1-2, gcc-mingw-20030911-2 > $ gcc foo.c > $ gcc -mno-cygwin foo.c > gcc: installation problem, cannot exec `cc1': No such file or dire

RE: gcc -mno-cygwin preprocessing: cygwin headers included.

From: Teun Burgers --- > > consider a file hello.c with the following two lines: > > #include > #include > > The attached cygwin.txt is the output of gcc -E hello.c > The attached no-cygwin.txt is the output of gcc -mno-cygwin -E hello.c > > The cygwin one includes /usr/include/st

Re: gcc -mno-cygwin fail -- undefined reference to `_impure_ptr'

On 12 Dec 2001 at 17:24, egor duda wrote: > Hi! > > Wednesday, 12 December, 2001 Jari Aalto+mail.emacs > [EMAIL PROTECTED] wrote: > > JAme> Does anyone know why following code fails? Do I need some > JAme> other libraries or gcc compile options? This is latest JAme> > Cygwin / W2k

RE: gcc -mno-cygwin creates cygwin executables!

David wrote: > I must say I'm baffled by this whole thread (NPI) > Why are you using such a lame program. If you look at a configure script, you will find that autoconf uses these "lame programs" to check for libraries. > Just add > #include > to zz.c and everything should work as intended, n

RE: gcc -mno-cygwin creates cygwin executables!

un Burgers [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 2:51 PM To: [EMAIL PROTECTED] Cc: Robert Collins Subject: Re: gcc -mno-cygwin creates cygwin executables! To sum up this thread: consider the following program: main () { pthread_create(); } gcc -mno-cygwin -o z

Re: gcc -mno-cygwin creates cygwin executables!

- Original Message - From: "Teun Burgers" <[EMAIL PROTECTED]> > 1) How about making libpthread.a a dummy library with just one .o file >with a dummy (empty) function? This does fix this particular >configure problem, but might have side effects since the pthread > symbols >are

RE: gcc -mno-cygwin creates cygwin executables!

On Wednesday, December 12, 2001 1:10 PM, Christopher Faylor [SMTP:[EMAIL PROTECTED]] wrote: > On Wed, Dec 12, 2001 at 09:55:25PM +0100, Teun Burgers wrote: > >egor duda wrote: > > > >> you're fixing specific symptoms instead of the problem itself. this > >> had been discussed already and the gen

Re: gcc -mno-cygwin creates cygwin executables!

On Wed, Dec 12, 2001 at 09:55:25PM +0100, Teun Burgers wrote: >egor duda wrote: > >> you're fixing specific symptoms instead of the problem itself. this >> had been discussed already and the general consensus (at least as i >> understand it) is the following: -mno-cygwin is a _hack_. it's >> suppo

Re: gcc -mno-cygwin creates cygwin executables!

egor duda wrote: > you're fixing specific symptoms instead of the problem itself. this > had been discussed already and the general consensus (at least as i > understand it) is the following: -mno-cygwin is a _hack_. it's > supposed to be used only when absolutely necessary and when you > absolut

Re: gcc -mno-cygwin creates cygwin executables!

Hi! Wednesday, 12 December, 2001 Teun Burgers [EMAIL PROTECTED] wrote: TB> To sum up this thread: TB> consider the following program: TB> main () { TB> pthread_create(); TB> } TB> gcc -mno-cygwin -o zz.exe zz.c -lpthread will compile and build. TB> A cygcheck on zz.exe reveals that lib

Re: gcc -mno-cygwin creates cygwin executables!

To sum up this thread: consider the following program: main () { pthread_create(); } gcc -mno-cygwin -o zz.exe zz.c -lpthread will compile and build. A cygcheck on zz.exe reveals that libcygwin.a is linked in. The problem with this is that a configure script with CC='gcc -mno-cygwin' wi

Re: gcc -mno-cygwin fail -- undefined reference to `_impure_ptr'

Hi! Wednesday, 12 December, 2001 Jari Aalto+mail.emacs [EMAIL PROTECTED] wrote: JAme> Does anyone know why following code fails? Do I need some JAme> other libraries or gcc compile options? This is latest JAme> Cygwin / W2k Pro / srv.p. 2 JAme> --

Re: gcc -mno-cygwin creates cygwin executables!

- Original Message - From: "a.rburgers" <[EMAIL PROTECTED]> > > If you want a mingw pthread library see the pthread-win32 project. > > I don't want to force the user to install pthread-win32. > I want this configure script (for fltk btw) to detect correctly whether > threads > are availabl

RE: gcc -mno-cygwin creates cygwin executables!

Rob Collins wrote: > > 1) Move the pthread functions from libcygwin.a to a separate library > > libpthread.a instead of libpthread.a being a symlink to libcygwin.a. > > That > > would fix this particular configure problem I think. This already > > works this way I found for libpng.a and libjpeg.a

Re: gcc -mno-cygwin creates cygwin executables!

=== - Original Message - From: "Teun Burgers" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 12, 2001 8:02 AM Subject: Re: gcc -mno-cygwin creates cygwin executables! > Christopher Faylor wrote: > > > On Tue, Dec 11, 2001 at 06

Re: gcc -mno-cygwin creates cygwin executables!

Christopher Faylor wrote: > On Tue, Dec 11, 2001 at 06:47:09PM +0100, Teun Burgers wrote: > >1) gcc -mno-cygwin searches for libs in /usr/lib. > > Should it? > It shouldn't, but it does. Changing this requires a complicated change > to 'ld'. I don't think that anyone is contemplating such a

Re: gcc -mno-cygwin creates cygwin executables!

On Tue, Dec 11, 2001 at 06:47:09PM +0100, Teun Burgers wrote: >1) gcc -mno-cygwin searches for libs in /usr/lib. > Should it? It shouldn't, but it does. Changing this requires a complicated change to 'ld'. I don't think that anyone is contemplating such a change. The only alternative is to u