Committed with the suggested changes (see attachment for reference).
Thanks.
Best regards,
Thomas
On 23/03/17 06:47, Gerald Pfeifer wrote:
Hi Thomas,
On Wed, 22 Mar 2017, Thomas Preudhomme wrote:
Is this ok for wwwdocs once [1] is committed in GCC 8 cycle?
+ GCC on Microsoft Windows c
Great, thanks. I'll go and commit the corresponding wwwdocs change.
Best regards,
Thomas
On 04/05/17 12:03, JonY wrote:
On 03/23/2017 10:47 AM, Thomas Preudhomme wrote:
Ack. Please find updated patch as per suggestions.
Best regards,
Thomas
I've applied the changes to GCC 8 trunk as r247
On 03/23/2017 10:47 AM, Thomas Preudhomme wrote:
> Ack. Please find updated patch as per suggestions.
>
> Best regards,
>
> Thomas
>
I've applied the changes to GCC 8 trunk as r247588.
signature.asc
Description: OpenPGP digital signature
Ack. Please find updated patch as per suggestions.
Best regards,
Thomas
On 23/03/17 06:47, Gerald Pfeifer wrote:
Hi Thomas,
On Wed, 22 Mar 2017, Thomas Preudhomme wrote:
Is this ok for wwwdocs once [1] is committed in GCC 8 cycle?
+ GCC on Microsoft Windows can now be configured via
+
Hi Thomas,
On Wed, 22 Mar 2017, Thomas Preudhomme wrote:
Is this ok for wwwdocs once [1] is committed in GCC 8 cycle?
+ GCC on Microsoft Windows can now be configured via
+ --enable-mingw-wildcard or
+ --disable-mingw-wildcard to force a specific behavior for
+ GCC itself
On 03/22/2017 05:39 PM, Thomas Preudhomme wrote:
> Hi JonY,
>
> Sorry for the delay. Please find updated patch as per Gerald and you
> suggestion.
>
> Is this ok for wwwdocs once [1] is committed in GCC 8 cycle?
>
> [1] https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01153.html
>
> Best regards,
Hi JonY,
Sorry for the delay. Please find updated patch as per Gerald and you suggestion.
Is this ok for wwwdocs once [1] is committed in GCC 8 cycle?
[1] https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01153.html
Best regards,
Thomas
On 12/03/17 23:51, JonY wrote:
On 03/12/2017 02:07 PM, Ger
On 03/12/2017 02:07 PM, Gerald Pfeifer wrote:
> On Thu, 9 Mar 2017, Thomas Preudhomme wrote:
>> JonY: what about the attached patch to document the change of behavior
>> of GCC on Windows depending on the configure option used?
>
> +MinGW issues
> +
> +GCC on Microsoft Windows can now be configure
On Thu, 9 Mar 2017, Thomas Preudhomme wrote:
JonY: what about the attached patch to document the change of behavior
of GCC on Windows depending on the configure option used?
+MinGW issues
+
+GCC on Microsoft Windows can now be configured via
+--enable-mingw-wildcard or --disable-mingw-wildcard
On 03/09/2017 11:22 AM, Thomas Preudhomme wrote:
> Hi Jakub,
>
> I forgot to mention "ok for stage1?", my bad. JonY said he was queuing
> the corresponding changes in GCC for stage1 so I was just trying to have
> a complete story. I do not expect to commit this before the actual code
> change is c
Hi Jakub,
I forgot to mention "ok for stage1?", my bad. JonY said he was queuing the
corresponding changes in GCC for stage1 so I was just trying to have a complete
story. I do not expect to commit this before the actual code change is committed.
Best regards,
Thomas
On 09/03/17 10:58, Jaku
On Thu, Mar 09, 2017 at 10:51:27AM +, Thomas Preudhomme wrote:
> Thanks Gerald,
>
> JonY: what about the attached patch to document the change of behavior of
> GCC on Windows depending on the configure option used?
GCC 7 has not branched yet, so the change can't be committed anywhere.
It seem
Thanks Gerald,
JonY: what about the attached patch to document the change of behavior of GCC on
Windows depending on the configure option used?
Best regards,
Thomas
On 04/03/17 14:25, Gerald Pfeifer wrote:
On Thu, 2 Mar 2017, Thomas Preudhomme wrote:
This should be mentioned in the "portin
13 matches
Mail list logo