|
From: Mark W. <ma...@kl...> - 2023-04-27 16:29:39
|
Hi Carl,
On Mon, Apr 24, 2023 at 02:29:13PM -0700, Carl Love wrote:
> Mark:
>
> Thanks for the pointer on IRC chat to the RC2 tarball. I must have
> missed the email.
>
> I noticed the following message on a Power 10 system.
>
> ./autogen.sh
> running: aclocal
> running: autoheader
> running: automake -a
> Unescaped left brace in regex is passed through in regex; marked by <--
> HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /home/carll/bin/automake
> line 3936.
> running: autoconf
>
> The autoconf version is:
>
> autoconf --version
> autoconf (GNU Autoconf) 2.69
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+/Autoconf: GNU GPL version 3 or later
>
> Note the autoconf seemed to work ok. I was still able to configure and
> build Valgrind and run the testsuite.
It is actually automake that produces the warning. But it is indeed
harmless. It is produced by a newer perl (>= 5.21.1) used with an
older automake (< 1.15.1).
> The test failures on Power 10 that I saw on one of the Power 10 systems
> was fixed, as expected.
>
> I see the following on both Power 10 systems.
>
> == 714 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures,
> 0 stdoutB failures, 2 post failures ==
> memcheck/tests/bug340392 (stderr)
> memcheck/tests/linux/rfcomm (stderr)
> massif/tests/new-cpp (post)
> massif/tests/overloaded-new (post)
So pretty close to zero fail.
bug340392 is mentioned as failing for ppc64 in in
https://bugs.kde.org/show_bug.cgi?id=352364 I wonder if we can mark it
known-fail/ignore with a reference to that bug?
I cannot easily test rfcomm my self since I don't seem to have
bluetooth enabled on my powerpc setup.
new-cpp/overload-new (post) checks are very dependent on the version
of libstdc++ installed. I don't know how to make these tests less
fragile.
Cheers,
Mark
|