From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: JonY <10walls@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows
Date: Fri, 17 Feb 2017 11:51:00 -0000 [thread overview]
Message-ID: <bb762fc2-ef7f-fabf-db50-c9234895b26f@foss.arm.com> (raw)
In-Reply-To: <97780aa1-62c2-9471-a9f7-fce968f94fe3@gmail.com>
Here you are:
2017-01-24 Thomas Preud'homme <thomas.preudhomme@arm.com>
* configure.ac (--enable-mingw-wildcard): Add new configurable feature.
* configure: Regenerate.
* config.in: Regenerate.
* config/i386/driver-mingw32.c: new file.
* config/i386/x-mingw32: Add rule to build driver-mingw32.o.
* config.host: Link driver-mingw32.o on MinGW host.
* doc/install.texi: Document new --enable-mingw-wildcard configure
option.
Must have forgotten to paste it.
On 17/02/17 10:52, JonY wrote:
> On 02/14/2017 10:42 AM, JonY wrote:
>> On 02/14/2017 09:32 AM, Thomas Preudhomme wrote:
>>>>
>>>> Looks good, be sure to emphasize this option affects mingw hosted GCC
>>>> only, not the compiler output.
>>>
>>> I think that should be pretty clear in the latest version of the patch,
>>> doc/install.texi contains:
>>>
>>> "Note that this option only affects wildcard expansion for GCC itself.
>>> It does
>>> not affect wildcard expansion of executables built by the resulting GCC."
>>>
>>> If you think a part of that sentence is still confusing please let me
>>> know and I'll improve it.
>>>
>>> Best regards,
>>>
>>> Thomas
>>>
>>
>> Yes, that should be good, no more objections.
>>
>>
>
> Before I forget, please also provide a changelog, thanks.
>
>
next prev parent reply other threads:[~2017-02-17 11:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:49 Thomas Preudhomme
2017-01-19 2:05 ` JonY
2017-01-20 9:06 ` Thomas Preudhomme
2017-01-26 13:19 ` Thomas Preudhomme
2017-02-07 8:48 ` JonY
2017-02-14 9:46 ` Thomas Preudhomme
2017-02-14 10:58 ` JonY
2017-02-17 11:01 ` JonY
2017-02-17 11:51 ` Thomas Preudhomme [this message]
2017-02-17 23:05 ` JonY
2017-02-22 16:07 ` Thomas Preudhomme
[not found] ` <CAF1jjLtsw10najrRwzJ7MJSSKxqmX0Wy4gKyf=dhmcAebS+JOA@mail.gmail.com>
2017-03-02 16:58 ` Thomas Preudhomme
2017-03-04 14:25 ` [wwwdocs] gcc-8/porting_to.html (was: [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows) Gerald Pfeifer
2017-03-09 10:51 ` [wwwdocs] gcc-8/porting_to.html Thomas Preudhomme
2017-03-09 10:59 ` Jakub Jelinek
2017-03-09 11:22 ` Thomas Preudhomme
2017-03-09 13:16 ` JonY
2017-03-12 14:08 ` Gerald Pfeifer
2017-03-12 23:51 ` JonY
2017-03-22 17:39 ` Thomas Preudhomme
2017-03-22 22:51 ` JonY
2017-03-23 6:47 ` Gerald Pfeifer
2017-03-23 10:47 ` Thomas Preudhomme
2017-05-04 11:10 ` JonY
2017-05-04 14:37 ` Thomas Preudhomme
2017-05-04 14:43 ` Thomas Preudhomme
2017-05-04 15:17 ` [arm-embedded] [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme
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=bb762fc2-ef7f-fabf-db50-c9234895b26f@foss.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).