Martin, I've looked into removing the -Wno-error for this warning
for just a subset of targets. It seems doable with some hardcoding
in configure.ac but if you're planning to do the cleanup for all of
them I'm wondering if we should even bother. What do you think?
Martin
On 1/14/22 08:46, Mart
Excerpts from Martin Liška's message of Januar 14, 2022 4:51 pm:
> On 1/14/22 16:46, Martin Liška wrote:
>> Hello.
>>
>> I noticed that when I run:
>> ACLOCAL=~/bin/automake-1.15.1/bin/aclocal
>> AUTOMAKE=~/bin/automake-1.15.1/bin/automake autoconf
>>
>> in gcc subfolder I get the following dif
On 1/14/22 16:46, Martin Liška wrote:
Hello.
I noticed that when I run:
ACLOCAL=~/bin/automake-1.15.1/bin/aclocal
AUTOMAKE=~/bin/automake-1.15.1/bin/automake autoconf
in gcc subfolder I get the following diff:
Have it, started with:
commit 7c6ae994fb587c19ca14aebe18dbc9aca83be609
Author:
Hello.
I noticed that when I run:
ACLOCAL=~/bin/automake-1.15.1/bin/aclocal
AUTOMAKE=~/bin/automake-1.15.1/bin/automake autoconf
in gcc subfolder I get the following diff:
diff --git a/gcc/configure b/gcc/configure
index d19059e13cc..ff570f73ef5 100755
--- a/gcc/configure
+++ b/gcc/configure
