https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109913
--- Comment #6 from rep.dot.nop at gmail dot com
---
On 21 May 2023 01:27:29 CEST, "pinskia at gcc dot gnu.org"
wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109913
>
>--- Comment #5 from Andrew Pinski ---
&g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109913
--- Comment #4 from rep.dot.nop at gmail dot com
---
On 20 May 2023 00:39:45 CEST, "pinskia at gcc dot gnu.org"
wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109913
>
>Andrew Pinski changed:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107691
--- Comment #4 from rep.dot.nop at gmail dot com
---
The problem was encountered with configure --enable-valgrind-annotations with
valgrind not installed.
Assignee: unassigned at gcc dot gnu.org
Reporter: rep.dot.nop at gmail dot com
Target Milestone: ---
New debian install, /bin/sh points to dash
/scratch/src/gcc-13.orig/libcpp/configure: line 7847: test: =: unary operator
expected
line 7847 reads
if (test $have_valgrind_h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47122
--- Comment #4 from rep.dot.nop at gmail dot com
---
On January 18, 2016 3:57:22 PM GMT+01:00, "bernds at gcc dot gnu.org"
<gcc-bugzi...@gcc.gnu.org> wrote:
>Can this be closed?
Sorry, yes, i think so.
