From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: ler762@gmail.com
Subject: Re: gcc -mno-cygwin
Date: Tue, 24 Jan 2023 12:35:29 -0700 [thread overview]
Message-ID: <ee9063bd-a37f-b56f-bc25-948061c13f87@Shaw.ca> (raw)
In-Reply-To: <89545deb-1bac-75c8-47de-527d73a1db6e@Shaw.ca>
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
>> -mnop-fun-dllimport -mthread -municode -mwin32
>>
>> Is that a cygwin specific or a generic gcc man page oversight?
>
> They were removed in 2010 except for:
>
> $ info gcc Invoking Option
> /Windows
>
> invoke.texi/Option Summary/x86 Windows Options at:
>
> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/invoke.texi#l1454
>
> 1453 @emph{x86 Windows Options}
> 1454 @gccoptlist{-mconsole -mcygwin -mno-cygwin -mdll @gol
> 1455 -mnop-fun-dllimport -mthread @gol
> 1456 -municode -mwin32 -mwindows -fno-set-stack-executable}
>
> from which the man gcc Windows options are generated with texi2pod and pod2man.
Submitted bug report about and patch to remove these remnants:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610482.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108521
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-01-24 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 19:50 Lee
2023-01-08 8:06 ` Brian Inglis
2023-01-24 19:35 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee9063bd-a37f-b56f-bc25-948061c13f87@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.com \
--cc=ler762@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).