public inbox for
 help / color / mirror / Atom feed
From: "mliska at suse dot cz" <>
Subject: [Bug tools/30072] FAIL:
Date: Fri, 03 Feb 2023 12:36:33 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #2 from Martin Liska <mliska at suse dot cz> ---
> It looks like the other way around (but the test-suite.log is confusing).
> Could you check whether configure detected DEMANGLE support?
>     libstdc++ demangle support         : yes

Yes, I really miss it:

configure:8679: checking for __cxa_demangle in -lstdc++
configure:8702: gcc -o conftest -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
-fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects
-Werror=date-time -g  -flto=auto -ffat-lto-objects conftest.c -lstdc++   >&5
cannot find -lstdc++: No such file or directory
collect2: error: ld returned 1 exit status
configure:8702: $? = 1
configure: failed program was:

Oh, apparently my spec file has not BuildRequires of the gcc-c++ package.
Adding that, all is green.

> If not, then the fix would be:
> diff --git a/tests/ b/tests/
> index 8c63d78d..1780157d 100755
> --- a/tests/
> +++ b/tests/
> @@ -18,6 +18,11 @@
>  . $srcdir/
> +if test -n "$ELFUTILS_DISABLE_DEMANGLE"; then
> +  echo "demangler unsupported"
> +  exit 77
> +fi
> +
>  # See
>  testfiles testfile-inlines

This would fix it as well..

You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-02-03 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  9:01 [Bug tools/30072] New: " mliska at suse dot cz
2023-02-03 10:06 ` [Bug tools/30072] " mark at klomp dot org
2023-02-03 12:36 ` mliska at suse dot cz [this message]
2023-02-03 12:46 ` mark at klomp dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).