On 11/17/20 1:22 AM, FX wrote:
>> OK. You have commit privs, right?
> Yes, and I did commit after Richard’s OK:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=034db20e2ea8301b5dc251bf10a97ce1cf90655f
>
> … but I forgot to send an email saying I had, sorry.
No worries. Thanks.
jeff
> OK. You have commit privs, right?
Yes, and I did commit after Richard’s OK:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=034db20e2ea8301b5dc251bf10a97ce1cf90655f
… but I forgot to send an email saying I had, sorry.
FX
On 11/2/20 3:40 AM, FX via Gcc-patches wrote:
> Here is an updated patch, that quotes all three makeinfo special characters:
> @ { }
> Tested on a build with source directory /tmp/foo@bar{gee}qux
>
> OK to commit?
OK. You have commit privs, right?
jeff
FX via Gcc-patches writes:
> Here is an updated patch, that quotes all three makeinfo special characters:
> @ { }
> Tested on a build with source directory /tmp/foo@bar{gee}qux
>
> OK to commit?
>
> diff --git a/gcc/Makefile.in b/gcc/Makefile.in
> index 7b94497b6f2..978a08f7b04 100644
> --- a/gcc
Here is an updated patch, that quotes all three makeinfo special characters: @
{ }
Tested on a build with source directory /tmp/foo@bar{gee}qux
OK to commit?
at.diff
Description: Binary data
at.ChangeLog
Description: Binary data
FX via Gcc-patches writes:
> Hi,
>
> Attached is a fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57076
> Currently, we cannot build GCC when the source directory contains a @
> character (which is a problem for Homebrew, where we typically build in
> directories such as /tmp/gcc@10/src:
Hi,
Attached is a fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57076
Currently, we cannot build GCC when the source directory contains a @ character
(which is a problem for Homebrew, where we typically build in directories such
as /tmp/gcc@10/src: https://github.com/Homebrew/brew/pull/90
